Hi,
I've seen this happening on AMD Opteron servers before I installed the AMD
driver for windows 2003. The driver corrected the clock-timer issues that
resulted in the same strange behavour.
You say you have Dual Core Intels so no match there, but maybe you need to
install the latest drivers and firmware on your server too. Check the HAL.
hope this helps.
Eric Vegter
"ChanKaiShi" wrote:
> It's not only I'm getting ridicilously high pings as I also getting ridicrivefsailously
> 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.
> > > > >
> > > > >
> > > > >
|