Results 1 to 2 of 2

Thread: Can anyone help me? This looks bad.

  1. #1
    Junior Member
    Join Date
    Jul 2007
    Posts
    12

    Can anyone help me? This looks bad.

    Well I used the network tools thing because for some reason I cant seem to connect to battle.net after around 3:30 everyday. Its really annoying me and I just wanted to know if there is anyway to fix it. Well here it is so can anyone look at this and tell me whats wrong or anyway to fix it.

    Resolve/Reverse Lookup:

    208.9.112.88 resolved to 208.9.112.88

    DNS Query Results:

    208.9.112.88. 655360 IN A 208.9.112.88


    WWWhois Results:

    IP Whois Results:

    Connecting to whois.arin.net...

    Sprint SPRINTLINK-BLKS (NET-208-0-0-0-1)
    208.0.0.0 - 208.35.255.255
    AAFES/Barracks SPRINTLINK (NET-208-9-112-0-1)
    208.9.112.0 - 208.9.119.255

    # ARIN WHOIS database, last updated 2007-07-23 19:10
    # Enter ? for additional hints on searching ARIN's WHOIS database.

    Checking Port 80...

    Port 80 does not appear to be open.

    Ping Results:

    PING 208.9.112.88 (208.9.112.88) 56(84) bytes of data.

    --- 208.9.112.88 ping statistics ---
    5 packets transmitted, 0 received, 100% packet loss, time 3999ms


    Traceroute Results:

    traceroute to 208.9.112.88 (208.9.112.88), 30 hops max, 40 byte packets
    1 66.230.216.1 (66.230.216.1) 0.256 ms 0.249 ms 0.239 ms
    2 e3f.dr5.as30217.net (84.40.24.85) 0.587 ms 0.798 ms 1.036 ms
    3 e3-1.co2.as30217.net (84.40.24.81) 0.345 ms 0.429 ms 0.497 ms
    4 e1-4.co1.as30217.net (84.40.24.102) 0.384 ms 0.458 ms 0.462 ms
    5 66.113.197.42 (66.113.197.42) 5.483 ms 66.113.197.53 (66.113.197.53) 13.226 ms 66.113.197.42 (66.113.197.42) 5.458 ms
    6 atl-bb1-link.telia.net (213.248.90.101) 13.339 ms mai-b1-link.telia.net (213.248.81.9) 6.074 ms atl-bb1-link.telia.net (213.248.90.101) 14.557 ms
    7 dls-bb1-link.telia.net (213.248.80.37) 35.639 ms ash-bb1-link.telia.net (213.248.80.141) 26.773 ms dls-bb1-link.telia.net (213.248.80.37) 35.635 ms
    8 sl-st22-ash-3-0-0.sprintlink.net (144.232.18.73) 30.071 ms 30.067 ms sprint-115390-dls-bb1.telia.net.92.248.213.in-addr.arpa (213.248.92.34) 32.114 ms
    9 sl-bb24-rly-13-0.sprintlink.net (144.232.20.188) 32.182 ms sl-bb27-fw-6-0.sprintlink.net (144.232.20.82) 32.810 ms sl-bb24-rly-13-0.sprintlink.net (144.232.20.188) 32.319 ms
    10 sl-bb24-fw-14-0.sprintlink.net (144.232.11.73) 33.300 ms sl-bb25-rly-10-0.sprintlink.net (144.232.14.150) 32.300 ms sl-bb24-fw-14-0.sprintlink.net (144.232.11.73) 33.279 ms
    11 sl-bb20-atl-6-0.sprintlink.net (144.232.20.174) 56.023 ms sl-bb22-orl-2-0.sprintlink.net (144.232.9.36) 69.327 ms sl-bb20-atl-6-0.sprintlink.net (144.232.20.174) 56.115 ms
    12 sl-gw6-orl-0-0-0.sprintlink.net (144.232.2.212) 73.517 ms sl-bb21-orl-2-0.sprintlink.net (144.232.20.87) 75.742 ms sl-gw6-orl-0-0-0.sprintlink.net (144.232.2.212) 73.373 ms
    13 sl-gw6-orl-0-0-0.sprintlink.net (144.232.2.212) 75.284 ms sl-aafes1-89123-0.sprintlink.net (144.228.113.206) 88.284 ms 88.231 ms
    14 sl-aafes1-89123-0.sprintlink.net (144.228.113.206) 88.990 ms * 88.971 ms
    15 * * *
    16 * * *
    17 * * *
    18 * * *
    19 * * *
    20 * * *
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *
    30 * * *

    This is a line quality test I did on dsl reports

    http://www.dslreports.com/linequality/nil/2256205
    Last edited by Derrty; 07-24-07 at 06:07 PM.

  2. #2
    I have reviewed the results of the tests on DSLReports. Something you need to know about that test set, there are computers that have the ICMP service shut off on their computers, there for if you ping them you will get a 100% loss or destination is unreachable if you try to do a traceroute on them, as if they don't exist but you can plainly see in the list they are running and are there.

    What you did was a ping timing test which really doesn't mean anything other than you see an average amount of ping timing for your computer vs. other computers in your pathway over the Internet.

    What I want you to do is ping your ISPs DNS routers, they should all be less than 60 ms on all pings, if they are higher especially around 100 up to 1000 ms, either you have a bad corrupt image on your modem meaning it needs to be updated / reflashed or you have a bad image on your modem and severe line problems, like noise or improperly wired stuff. If you need help on how to do this stuff just ask.

Similar Threads

  1. Debate with me on “how bad kids are these days”.
    By RoundEye in forum General Discussion Board
    Replies: 55
    Last Post: 07-04-07, 01:37 AM
  2. Are ya havin' a Bad Day???
    By minir in forum General Discussion Board
    Replies: 2
    Last Post: 10-16-06, 08:57 PM
  3. The good, the bad, and the ugly...
    By DaddyLongLeg in forum General Discussion Board
    Replies: 12
    Last Post: 08-01-05, 03:04 PM
  4. I'm A Bad American
    By Jamie_R in forum General Discussion Board
    Replies: 13
    Last Post: 07-10-05, 09:46 AM
  5. when life is bad, its really really bad... but when its good...
    By Meggie in forum General Discussion Board
    Replies: 14
    Last Post: 05-03-05, 10:18 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •