Coffeehouse Thread

11 posts

Ping from Hell!

Back to Forum: Coffeehouse
  • User profile image
    Tom Servo

    I don't know what to say, but I think it might be related to my internet going down the crapper.

    M:\Documents and Settings\Administrator>tracert www.google.com
    
    Tracing route to www.l.google.com [64.233.183.103]
    over a maximum of 30 hops:
    
      1     8 ms  4294967239 ms     8 ms  1-160.244.81.adsl.skynet.be [81.244.160.1]
      2    10 ms  4294967243 ms  4294967242 ms  169.237-201-80.adsl.skynet.be [80.201.237.169]
      3    10 ms  4294967242 ms  4294967242 ms  ge1-0.intlmar1.isp.belgacom.be [194.78.0.147]
      4    11 ms  4294967243 ms  4294967243 ms  cbu-pcbru25-skynet-tge24.car.belbone.be [80.84.20.38]
      5    21 ms  4294967253 ms  4294967253 ms  72.14.198.17
      6  4294967253 ms  4294967253 ms    21 ms  72.14.238.244
      7  4294967254 ms  4294967254 ms  4294967254 ms  216.239.43.91
      8  4294967256 ms  4294967256 ms  4294967256 ms  72.14.232.141
      9  4294967255 ms    62 ms  4294967281 ms  72.14.233.77
     10  4294967265 ms  4294967267 ms  4294967261 ms  216.239.43.34
     11  4294967256 ms  4294967256 ms  4294967257 ms  64.233.183.103
    
    Trace complete.
    
    M:\Documents and Settings\Administrator>


    What the hell? Considering how fast it responds, this must be packets from the future. This is on 64bit Windows, please help!

  • User profile image
    SlackmasterK

    Ain't no way.  These numbers say you were waiting for > 3 days for that tracert to complete.  Something is seriously messed up here.

    Does this happen from another machine on your network?  If so, you may want to contact your provider.

  • User profile image
    Sven Groot

    It's interesting that all the "wrong" values are very near the maximum values of an unsigned integer.

  • User profile image
    Alt-F4

    Tom Servo wrote:
    4294967239 ms


    AIEEE!

  • User profile image
    cheong

    Sven Groot wrote:
    It's interesting that all the "wrong" values are very near the maximum values of an unsigned integer.

    And note that there's some lines with all the 3 values set to the number, and still displays the IP address of the router instead of "Request timeouted."

    It does seems convincable to me that the packet has travelled that long from 3 days before the OP's ping... Tongue Out

    Recent Achievement unlocked: Code Avenger Tier 4/6: You see dead program. A lot!
    Last modified
  • User profile image
    SlackmasterK

    cheong wrote:
    "Request timeouted."

    What language pack do you use?  Mine says "timed out".

  • User profile image
    cheong

    Chinese... anyway, you get what I mean... Tongue Out

    Recent Achievement unlocked: Code Avenger Tier 4/6: You see dead program. A lot!
    Last modified
  • User profile image
    SlackmasterK

    cheong wrote:
    Chinese... anyway, you get what I mean...


    But in this case "time" is the verb.  "out" is what it times.  Therefore, it "times" out.

  • User profile image
    Tom Servo

    Sven Groot wrote:
    It's interesting that all the "wrong" values are very near the maximum values of an unsigned integer.

    After pinging localhost and seeing values going from 65ms to -65ms (yes, negative ping, which is the same as in tracert, which however uses uint instead of int), I poked the web for a bit and apparently the problem was that I didn't install the AMD64 CPU drivers (why would I need to to beginwith Perplexed ). I'll test things again after this machine ran for a couple of hours again.

  • User profile image
    cheong

    And the result?

    Recent Achievement unlocked: Code Avenger Tier 4/6: You see dead program. A lot!
    Last modified
  • User profile image
    Tom Servo

    Seems to be fixed. The CPU driver apparently controls the power states and CPU clock. Since this is a dual core, I suppose the timers of both cores desynced and showed it to me when the command line tools and the TCPIP driver ran on different cores from each other.

Comments closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.