Quote:
Originally Posted by imsickofwebpro
C:\Documents and Settings\scott>tracert netfirms.com
Tracing route to netfirms.com [64.141.108.254]
Not a DNS issue, as the domain name is being resolved.
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 32 ms 55 ms 28 ms 10.224.0.1
3 * * 31 ms
vl-201.gw03.bloor.phub.net.cable.rogers.com
[66.
185.90.1]
4 76 ms 33 ms 41 ms
te-15-1-0.gw01.bloor.phub.net.cable.rogers.com [
24.153.5.29]
5 46 ms 43 ms 36 ms
so-3-2-0.gw02.wlfdle.phub.net.cable.rogers.com [
66.185.80.174]
6 30 ms 29 ms 27 ms
pos-4-0.igw01.front.phub.net.cable.rogers.com [6
4.71.240.53]
7 37 ms 33 ms 31 ms rc1sh-ge9-0-2.mt.shawcable.net
[66.163.66.25]
Not a rogers issue, because the traffic is leaving their network
8 30 ms 42 ms 28 ms ra2sh-ge4-3.mt.shawcable.net
[66.163.66.46]
There are two possibilities for the connection going dead here.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Thanks in advance.
|
It is possible something at Netfirms has blocked your traffic, or it is possible that something at one of the intermediary routers between your ISP and your hosting provider has gone wrong. These strike me as the most likely possibilities, and I have experienced both. Um, except for triggering an IDS... never done that...
It is possible that you have inadvertently triggered an IDS. It is not hard as these systems are designed to be rather sensitive. You could get blocked by something as simple as entering the wrong port number when trying to access a remote administration utility for example. To check, you would need to contact someone at the security division at your hosting company who can actually check the IDS and blacklists.
If a router has gone down, you are at the mercy of the service provider until the issue is fixed. Most Internet communications pass through routers from two-four different companies before getting to their destination. Because the traffic is leaving your ISP's network before getting lost, your ISP would have to work with the other service providers along the chain to get traffic rerouted to bypass the bad router. However, the traceroute report should at least give your ISP a starting point to track down the problem if this is the cause.