Networks

Ask something
Discussion Locked

First ping always times out

0 helpful
7 replies

by mike_m 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Environment: LAN with NT4 PDC, abt 15 clients

Problem: One client, W2K, semms to be sluggish on the network, exhibits several login failures, but works fine and transfer files correctly an quickly.

Pinging any other station from this PC alwaysresults in a timeout ONLY on the first request
i.e.

> Request timed out
>
> answer from x.y.z.t in 20mS
> answer from x.y.z.t in 22mS
> answer from x.y.z.t in 16mS
> answer from x.y.z.t in 28mS

Using longer ping length up to 32000 has same result ( no lost packet if long)

Using repeat count up to 200 has always the first packet lost.

WINS is up and seems to work fine.

LMHOST has #PRE on DOM, server and WINS server

Adding entries on LMHOSTS (and reloading) doesn't help.
Hint: command nbtstat -RR often results in "impossible to unload, retry later"

Mapped units come up Unconnected 75% of the times, the connect immediately at first attempt.

Another Symptom: Some client occasionally loses all icons on desktop,and rebuild immediately.
All the rest seem to qork fine

Any hint by anybody ? Thank you, Mike

7 replies

by rapidad

To start with, compare the gateway values on the boxes that work and on the ones that dont. Also check for netbuei on the tcp/ip properties on boxes that work/dont..........
let us know

by rg11

Check the cabling. Swap computers with the bad one. If you still get the same problems on the new computer then check your cabling. You could get data loss from a bad connection..

by techkid

Sounds like a switch problem. If your switch is auto-negotiating speed/duplex set it manually so it doesn't do that.

Missing the first ping isn't too unusual when you have a switching problem. The switch will time out the first ping while it updates it's CAM table, subsequent packets can then connect.

This discussion is closed to new replies.