Did you check the full/half duplex setting also? Can the hub be
configured, and locked (forced) to 10 MBit/half duplex? And try locking A to
10/half also. 
	I've seen auto-negotiation (10/100 and full/half duplex) flake out
alot. Especially when wiring might be a problem... Of course, I could be
wrong, and the problem might be something else... :-)

---   David A Woyciesjes
---   C & IS Support Specialist
---   Yale University Press
---   mailto:david.woyciesjes@yale.edu
---   (203) 432-0953
---   ICQ # - 905818


! -----Original Message-----
! From: Jon [mailto:jons@dotnet.com]
! Sent: Friday, October 26, 2001 4:47 PM
! To: port-i386@netbsd.org
! Subject: ping delays
! 
! 
! Machine A = netbsd 1.5.2 (100MBits)
! Machine B = windows 95 (10MBits)
! Machine C = windows 98 (10MBits)
! 
! When A pings B or C there is a 75 second delay before the 
! information starts, no record of this on the ping stats.
! When A pings B or C by NAME, no problem, no delay
! When B or C pings A, B or C by ip - no delay
! 
! What the is problem? any theories.
! 
! I tried to make A run at 10MBits (my hub can tell me if that 
! works by a different color light, it did work)
! 
! All this did was come back - host is down.
! 
! Does this mean I am setting it by the wrong method - I used 
! media 10baseT in the ipconfig file.
! 
! Please help.
!