View Full Version : this is bad right?
overclucker
03-16-08, 11:09 PM
Pinging austin-main [127.0.0.1] with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time=-6ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = -6ms, Average = 1073741822ms
=ACID RAIN=
03-16-08, 11:30 PM
What's wrong with it? It's the same as localhost, everything is normal. -6 milliseconds is probably just a misparsing of data.
overclucker
03-16-08, 11:34 PM
What's wrong with it? It's the same as localhost, everything is normal. -6 milliseconds is probably just a misparsing of data.
this is.
Average = 1073741822ms
also i have been having very weird web browsing issues.. i get really fast link speeds on the LAN and the WAN but when browsing websites seem to pause at "connecting to google.com" for example and sometimes it just times out.
i tried repairing my TCP stack and Winsox.. it helped for 30 minutes and then it went to crap again.. also tried reinstalling the NIC drivers... the same happened.. it only happens to this computer on the network.
=ACID RAIN=
03-17-08, 01:29 AM
Oh I see, yeah that crazy number is just the program saying WTF?@!~ and spitting out some crap. Don't sweat that just yet.
If you have slow resolving, that's usually a simple DNS issue. Find another DNS server besides your ISP primary, set the new one manually, and see how it behaves then. I like to use 4.2.2.4 since it is a known verizon DNS server that has 100% uptime. It's pretty much in the exact geographic middle of the US, so for me it's pretty fast.
Edit: It's getting late for my brain haha. I just noticed you said it's only on that machine. Check DNS setting just for kicks please, then you might try replacing the patch cable as well, just for testing purposes.
thideras
03-17-08, 01:34 AM
That isn't what I'm questioning. Why do you have a negative 6ms time? The computer predicted the ping and sent it early?? :confused:
=ACID RAIN=
03-17-08, 01:40 AM
Prefetch.
LMAO
I don't know, but it may be a system glitch that has nothing to do with his problem. Loopback is deep enough in the system that it may be another separate issue from what he is describing. I'm touching on the simple stuff first, then we go into the system deeper when/if the simple variables are exhausted.
ShadowPho
03-17-08, 06:57 AM
Average = 1073741822ms
That is what we call a conversion from signed to an unsigned number ^^.
There is a guy here (http://forums.pcper.com/showthread.php?t=430695) claiming it's the AMD dual core CPU causing a discrepancy between the two cores.
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.