[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:	DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:	Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:	NETCAD::COLELLADT

Created:	Wed Nov 13 1991
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4455
Total number of notes:	16761

1523.0. "XID Freezes PC (again)" by SWAM1::SACHARSKE_LO () Tue Oct 04 1994 18:44

    A customer is having problems with PCs freezing when a DECbridge90 is
    on the network.
    
    PCs (Gsteway P5 w/ 3Com 3C509 NICs) are running WfW 3.11 and Pathworks
    V5.0A. With the B90's taken out, the network runs fine. A line analyzer
    shows that the freeze is precedded by a XID packet from the bridge.
    
    We logged a call the CSC and there was a B90/XID prblem but only when
    running TCP/IP. The patch is for TCP/IP and appears to be included in
    5.0A, so this seems a dead end.
    
    Anyone else seen this?
    
    Mark/Lou

T.R	Title	User	Personal Name	Date	Lines
1523.1	3C509 NDIS issue or General NDIS issue?	KEIKI::WHITE	MIN(2�,FWIW)	`Wed Oct 05 1994 00:10`	5
	Just to narrow the problem, have you tried an ETHERWORKS-3 NIC card? Bill
1523.2	other bridges?	WOTVAX::64021::Tim_Banks	Network Mercenary	`Wed Oct 05 1994 09:13`	7
	Are there any other bridges on the network, particularly between the PCs and servers? Are you seeing a bridge interaction problem with spanning tree/802.1d? Just a thought....... Tim
1523.3	No-just 3com	SWAM1::SACHARSKE_LO		`Wed Oct 05 1994 13:11`	2
	No. They have 3com and raised the issue of standards etc.. It might be worth while just to see if it has an effect.
1523.4	Probably needs a patch	SWAM1::SACHARSKE_LO		`Wed Oct 05 1994 13:18`	6
	They have captured a XID packet and transmited to the PC and froze it. By virtue of the fact that this is a know problem with TCP/ip and has a patch, I don't think it's spanning tree. Lou
1523.5		KAOFS::M_VALLEE	csc hull canada	`Tue Feb 21 1995 11:22`	8
	The fix for this is to put in the pc protocol.ini a statement like this: responder = 0 in the [datalink] section this causes the card not to respond to 802.2 test and xid messages.