cant f'ing connect!

Discussion in 'other software & services' started by dangs, Jan 13, 2006.

Thread Status:
Not open for further replies.
  1. dangs

    dangs Guest

  2. relo

    relo Guest

  3. Close_Hauled

    Close_Hauled Registered Member

    Joined:
    Apr 24, 2004
    Posts:
    1,015
    Location:
    California
    If you know how to ping, you can use www.dnsstuff.com to compare your findings to theirs. If they have the same results as you, then it is probably the site. If it is just you having problems, then it could be your ISP.

    Ping is executed from the DOS prompt. Just put the web site as a parameter after the command:

    Code:
    C:\>ping www.novell.com
    
    Pinging www.novell.com [130.57.4.27] with 32 bytes of data:
    
    Reply from 130.57.4.27: bytes=32 time=47ms TTL=51
    Reply from 130.57.4.27: bytes=32 time=111ms TTL=51
    Reply from 130.57.4.27: bytes=32 time=351ms TTL=51
    Reply from 130.57.4.27: bytes=32 time=103ms TTL=51
    
    Ping statistics for 130.57.4.27:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 47ms, Maximum = 351ms, Average = 153ms
    
    C:\>
    Then go to DNSstuff and have their site ping.
     
  4. iceni60

    iceni60 ( ^o^)

    Joined:
    Jun 29, 2004
    Posts:
    5,116
    that's such a good idea. i used dnsstuff yesterday to check a site but i used traceroute to see what was happening at the last few hops, i didn't even check to see if the last 2/3 routers were the same as the ones i was using :rolleyes: i'll use your method next time.

    i like to use Pingplotter too on windows, it shows where the slowdown is.
    www.pingplotter.com/
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.