Article View: comp.os.netware.connectivity
Article #207Re: Which Lan Analyser?
From: Roger Kresge
Date: Thu, 29 Feb 1996 00:00
Date: Thu, 29 Feb 1996 00:00
43 lines
2763 bytes
2763 bytes
dwyerpg@melbpc.org.au (Peter Dwyer) wrote: >We are running about 300 devices on a couple of Token Ring segments (4MB and >16MB). The hosts include NetWare 3.12 Servers, Unix hosts, OS2 Lan Manager >Servers and Win NT servers. >The 4mb ring is fairly over-crowded (a situation which we are moving to >alleviate). Every now and then the 4mb ring beacons and it can take hours to >find the offending device. It can ve caused by a loose connection, some idiot >plugging workstation with a 16mb NIC into the 4mb ring etc etc..... The >downtime is getting rather costly for the company! >The latest beaconing problem caused an entire afternoon of lost time and >management have finally conceded that we need some sort of LAN analysis tool >to try and pinpoint the cause. >I've looked at Lanalyser but it won't attach to a beaconing LAN - fat lot of >good that is! I need something which will run on a "sick" LAN and work with >IPX, TCPIP, NETBEUI, NETBIOS and maybe one or two other protocols. I need it >to be able to highlight the possible cause of the net problems (eg. >whereabouts on the ring the problem occurs). Hmmmm... Last time I checked, Lanalyzer for Windows does insert into a beaconing ring. It does so by forcing itself into the ring as the "active monitor", and therefore is able to help you track down the problem on a "sick" ring. Having said that, one of the most obvious choices available is Network General's Sniffer, but it's a wee bit more expensive than Lanalyzer for Windows. <g> Somewhere over $20K in US dollars, if memory serves me. >Can anyone out there suggest their preferred solution? Of course, capital >expenditure is always an issue so if there's a $200,000 solution, I might like >it but my Boss will just laugh at me. -- =================================================================== Roger Kresge, Master CNE/CNI Internet: rkresge@redrose.net Inacom Information Systems Compuserve: 71023,447 Lancaster, PA ===================================================================
Technical Details
Message-ID:
<4h4804$ut0@lily.redrose.net>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<4gufko$gaa@wombat.melbpc.org.au>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fe659,d41e5bf7a5ddb114 X-Google-Attributes: gidfe659,public X-Google-Thread: fa939,d41e5bf7a5ddb114 X-Google-Attributes: gidfa939,public X-Google-Thread: f8bf7,d41e5bf7a5ddb114 X-Google-Attributes: gidf8bf7,public From: rkresge@redrose.net (Roger Kresge) Subject: Re: Which Lan Analyser? Date: 1996/02/29 Message-ID: <4h4804$ut0@lily.redrose.net> X-Deja-AN: 141592370 references: <4gufko$gaa@wombat.melbpc.org.au> organization: a Digital Internet AlphaServer Site reply-to: rkresge@redrose.net newsgroups: comp.os.netware.connectivity,comp.os.netware.misc,bit.listserv.novell