Re: Getting ridicilous ping times on Win2003 R2

It's not only I'm getting ridicilously high pings I also getting ridicilously
low as well. And this one does not go through switch, it's actually pinging
Guest machine on the same box.

C:\Documents and Settings\gregory>ping dc2 -t

Pinging dc2.artisticcheese.com [10.0.1.6] with 32 bytes of data:

Reply from 10.0.1.6: bytes=32 time=157944ms TTL=128
Reply from 10.0.1.6: bytes=32 time=157946ms TTL=128
Reply from 10.0.1.6: bytes=32 time=1ms TTL=128
Reply from 10.0.1.6: bytes=32 time=158045ms TTL=128
Reply from 10.0.1.6: bytes=32 time=158043ms TTL=128
Reply from 10.0.1.6: bytes=32 time=1ms TTL=128
Reply from 10.0.1.6: bytes=32 time=158138ms TTL=128
Reply from 10.0.1.6: bytes=32 time<1ms TTL=128
Reply from 10.0.1.6: bytes=32 time=-158231ms TTL=128
Reply from 10.0.1.6: bytes=32 time=-158231ms TTL=128
Reply from 10.0.1.6: bytes=32 time=158239ms TTL=128
Reply from 10.0.1.6: bytes=32 time=-158238ms TTL=128
Reply from 10.0.1.6: bytes=32 time=1ms TTL=128
Reply from 10.0.1.6: bytes=32 time<1ms TTL=128
Reply from 10.0.1.6: bytes=32 time<1ms TTL=128

Ping statistics for 10.0.1.6:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = -158231ms, Average = 31577ms
Control-C
^C
C:\Documents and Settings\gregory>



"ChanKaiShi" wrote:

I doubt that it's cable or port related. I switched cables already and I
connected NIC to 100 Mb switch and still the same issue. Moreover I connected
another NIC on the same box (100 BaseT NIC) and still seeing the same issue.
Also those huge pings are not actually affecting network perfomance so I
ping will have 1 ms round trip time and exactly next one will 1259353 ms
round trip which is impossible since it's 340+ hours.
I'm pretty sure it's either OS or driver for NIC but both are at latest
version, I also run Intel tests on cable, port, NIC itself and all came back
clean but this anomaly with ping still continues.

"Technicalmajor" wrote:

I had very similar problem just after I installed and config'd my backup DC,
The only conclusion that I got to was the server was replicating and that
what was causing the stupidly slow ping times!

Other than that could there be a problem with your switch such as a dodgy port

"ChanKaiShi" wrote:

Cables goes directly from server to Gig switch which is connected other
computer is connected to as well.
Tracert from server to host is having 1 hop since both on local subnet
C:\Documents and Settings\Administrator>tracert 10.0.1.1

Tracing route to 10.0.1.1 over a maximum of 30 hops

1 1250353 ms 1250353 ms 1250353 ms 10.0.1.1

Trace complete.

Perfomance of NIC is fine, average network bandwidth used for file copy is
around 10 MBps

"Iuri Cuznetov" wrote:

Hello,I'm getting ridicilous ping times when pinging server on local
subnet.
What can be the reason for this? All latest drivers and patches are
installed.

It could be your cables or switches. Is your LAN tested for TIA/EIA
standards? If it is, try to change patch-cords and show us a tracert to your
local server.

BTW, do you mesured NIC's performance on your server?

Iuri.



.

Relevant Pages

  • Re: Weird Network Connectivity Problem
    ... choose a different switch port than the one you've been using. ... When this happens x199 can ping anything on the ... local network EXCEPT the SBS server, ... I've changed NICs, workstation IP, all the simple ...
    (microsoft.public.windows.server.sbs)
  • Re: What program is doing the pinging
    ... IP outside of his network and started happening about a month ago. ... >>> The server doing the pinging is just a file server not a DC, ... The computer it is trying to ping (my ...
    (microsoft.public.security)
  • Multihomed Server Routing Woes: Two network segments cant communi
    ... I'm having problems with a multihomed Windows 2003 server that I've ... Both NICs are connected to the same switch. ... and it's got a number of virtual machines on it with IPs of: ... Any other machine on 192.168.1.x cannot ping any machine on 170.34.179.x. ...
    (microsoft.public.windows.server.networking)
  • Ping results again...
    ... Pinging microsoft.com with 32 bytes of data: ... you were asked for the result of ping ... from the server, run these commands in a dos window, and post the output. ... other MS sites via their IE6 installation. ...
    (microsoft.public.windows.server.sbs)
  • Re: Name resolving in domain
    ... However if I use ping command in the workgroup server, ... > Pinging by single name or FQDN makes a difference. ... Connection-specific DNS Suffix. ...
    (microsoft.public.win2000.dns)