On Thu, Aug 16, 2001 at 08:30:56PM -0400, Ben Collins wrote: > Yeah, I suspect that is from getaddrinfo() call. The netbios is > impossible, since I have nothing that should be using that. Perhaps > something else on the lan.
Nope. There are no local windows boxes on this lan and those IP addresses are not local. > > A few things to try. How about sending larger ping packets > > > > ping -s 1000 # ping -s 1000 64.21.79.61 PING 64.21.79.61 (64.21.79.61): 1000 data bytes 1008 bytes from 64.21.79.61: icmp_seq=0 ttl=255 time=3.2 ms 1008 bytes from 64.21.79.61: icmp_seq=1 ttl=255 time=0.5 ms 1008 bytes from 64.21.79.61: icmp_seq=2 ttl=255 time=0.5 ms 1008 bytes from 64.21.79.61: icmp_seq=3 ttl=255 time=0.5 ms 1008 bytes from 64.21.79.61: icmp_seq=4 ttl=255 time=0.5 ms --- 64.21.79.61 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 0.5/1.0/3.2 ms > > Was this on 100 base-T or 10 base-T connections? Full or half > > duplex. I have only got a 10 base-T connection at the moment maybe > > that has something to do with it. > > Did check. I'm check that later aswell. It autonegotiates 100Mbps FDX under solaris. The Linux driver doesn't report the speed -- is there any way to obtain this information from ifconfig? I can have the network engineer force the port to 100FDX, so we can be sure that's what it's at if there is no other way to tell. --Adam -- Adam McKenna <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>