also from our host......
Hi are there any commonalities between these users? Is it possible to have them run a tracert and send to us along with their working ip found by googling Whats my ip
How to Run a Tracert
Traceroute shows you the path a packet of information takes from your computer to the destination computer. It list’s all the routers it passes through on the way to the destination, or fails and is discarded. In addition, it tells how long each 'hop' routers takes.
In Windows7, select Start > enter “cmd” in the search window
This will give you a window like the one below.
Enter the word tracert, followed by a space, then the domain name.
The following is a successful traceroute from a computer in New Zealand to mediacollege.com:
Tracert Example
First shown is the destination, then the IP address of the domain and the maximum number of hops before it times out.
Next shown is information about each router (hop) it passes on the way to the destination server.
1. Is the starting network this tracert was from.
2. Is the ISP the originating computer the trace was from
3. Is also in the originating network
4. Is a time out.
5 – 9. Are routers on the same NZ network
10 – 14. Are all on the the same US network
15 – 17. Are also on a US network but a different one.
18. Is a router located on the mediacollege.com network
19. Is the server mediacollege.com resides on
Each column is a response from that router, Looking at the second line, the hop took 240ms (240 milliseconds), then 421 ms, finally 70ms.
Notice line 4 'timed out', meaning the router didn’t respond and another was successfully tried (202.50.245.197). In addition, on line 8, the time it took quadrupled.
This is useful information in diagnosing an unreachable site. You can see a failed or slow connection. It’s a good idea to run a traceroute when the site is working perfectly. Then you’ll have a baseline to compare to when it isn’t. Just know that the route may be different with each run, but the networks it run through will mostly be similar.
In the example, had it continued to time out after line 9, that network become suspect and no the destination server.
If the time out was after line 1, the problem is connecting to your ISP (you would not be able to connect to the internet).
Typically if your website that is unreachable, run both the traceroute and ping commands before contacting your ISP or host as have this information can speed the diagnosis.
I ask as this is what I see on Time Warner in Southern Calif
http://screencast.com/t/vBXtgt1RZKq
And get smiler results in global tests
http://screencast.com/t/7d0gGr47r71S
Hi are there any commonalities between these users? Is it possible to have them run a tracert and send to us along with their working ip found by googling Whats my ip
How to Run a Tracert
Traceroute shows you the path a packet of information takes from your computer to the destination computer. It list’s all the routers it passes through on the way to the destination, or fails and is discarded. In addition, it tells how long each 'hop' routers takes.
In Windows7, select Start > enter “cmd” in the search window
This will give you a window like the one below.
Enter the word tracert, followed by a space, then the domain name.
The following is a successful traceroute from a computer in New Zealand to mediacollege.com:
Tracert Example
First shown is the destination, then the IP address of the domain and the maximum number of hops before it times out.
Next shown is information about each router (hop) it passes on the way to the destination server.
1. Is the starting network this tracert was from.
2. Is the ISP the originating computer the trace was from
3. Is also in the originating network
4. Is a time out.
5 – 9. Are routers on the same NZ network
10 – 14. Are all on the the same US network
15 – 17. Are also on a US network but a different one.
18. Is a router located on the mediacollege.com network
19. Is the server mediacollege.com resides on
Each column is a response from that router, Looking at the second line, the hop took 240ms (240 milliseconds), then 421 ms, finally 70ms.
Notice line 4 'timed out', meaning the router didn’t respond and another was successfully tried (202.50.245.197). In addition, on line 8, the time it took quadrupled.
This is useful information in diagnosing an unreachable site. You can see a failed or slow connection. It’s a good idea to run a traceroute when the site is working perfectly. Then you’ll have a baseline to compare to when it isn’t. Just know that the route may be different with each run, but the networks it run through will mostly be similar.
In the example, had it continued to time out after line 9, that network become suspect and no the destination server.
If the time out was after line 1, the problem is connecting to your ISP (you would not be able to connect to the internet).
Typically if your website that is unreachable, run both the traceroute and ping commands before contacting your ISP or host as have this information can speed the diagnosis.
I ask as this is what I see on Time Warner in Southern Calif
http://screencast.com/t/vBXtgt1RZKq
And get smiler results in global tests
http://screencast.com/t/7d0gGr47r71S