Ping Time out while transfering files over 2 PCs, help greatly aperciated

[Gomce]

Ok, bellow is the problem
I have 2 computers, win2k pro on each, BNC connected,
one has Realtek Ethernet card the other has Winbond card (w89c940f chipset) (no Hub, just 2 computers, home LAN)
while transferring files I get this (copy pasted bellow)
I want to know why is the reguest timeout ??
When I am not transferring files, I get ping reply <1 and no time outs..can it be a case of bad Lan card or cable ??? or...?



Reply from 192.168.0.2: bytes=32 time=7ms TTL=128
Request timed out.
Reply from 192.168.0.2: bytes=32 time=2ms TTL=128
Reply from 192.168.0.2: bytes=32 time=9ms TTL=128
Reply from 192.168.0.2: bytes=32 time=8ms TTL=128
Reply from 192.168.0.2: bytes=32 time=10ms TTL=128
Reply from 192.168.0.2: bytes=32 time=10ms TTL=128
Request timed out.
Reply from 192.168.0.2: bytes=32 time=13ms TTL=128
Reply from 192.168.0.2: bytes=32 time=10ms TTL=128
Reply from 192.168.0.2: bytes=32 time=9ms TTL=128
Reply from 192.168.0.2: bytes=32 time=1ms TTL=128
Reply from 192.168.0.2: bytes=32 time=8ms TTL=128
Request timed out.
Reply from 192.168.0.2: bytes=32 time<10ms TTL=128
Reply from 192.168.0.2: bytes=32 time=12ms TTL=128
Reply from 192.168.0.2: bytes=32 time=8ms TTL=128
Reply from 192.168.0.2: bytes=32 time=10ms TTL=128
Reply from 192.168.0.2: bytes=32 time=7ms TTL=128
Request timed out.
Reply from 192.168.0.2: bytes=32 time=10ms TTL=128
Reply from 192.168.0.2: bytes=32 time=8ms TTL=128
Reply from 192.168.0.2: bytes=32 time=11ms TTL=128
Reply from 192.168.0.2: bytes=32 time=12ms TTL=128

 

[ScottMac]

Are you running the coax directly to each NIC, or is the cable attached to "T" connectors with terminators?

Gotta know....

Scott

 

[Gomce]

the cable has T-connectors with terminators

 

[Gomce]

help ?

 

[spidey07]

Is one end of the cable segment grounded? 50 ohm terminator on each end of the cable segment?

 

[Saltin]

Obviously the "request timed out" is a result of one or both boxes being to busy to reply, due to the file transfer.
What you could try to do, is modify the ping with the -w switch. The syntax for increasing the time out default time is "ping -w ### where ### is the amount of time in milliseconds you wish to allow for the packet's round trip.
I bet if you increase it, there will be less/no timeouts. I'm guessing it's related to the nature of direct cable connections.

 

[bsobel]

I don't see a problem here. Ping responses are based on availability (e.g. the receiving computer can discard them if too busy). If your transfering files and saturating that line, this is exactly the behaviour you'll see.

Bill