Tracert Question

[dallara]

Many times I cannot access my site from home, I just did a tracert and it comes up as: Unable to resolve target system name giffsfarm.com. I am running windows xp, dial up connection. I have had this issue since first starting my site a few weeks ago. I am a complete newbie at this but want to get it working correctly.

 

One other issue is my DNS report. There are a quit a few errors that need to be fixed. I know I sent a help ticket a while back about it and was told DNS audits were being done and that I should see most of the issues resolved soon. Just wondering what, if anything I can do to fix this.

[dallara]

couple hours later, I can get connected and this is what the tracert reads:

 

Tracing route to giffsfarm.com [72.18.159.10]

over a maximum of 30 hops:

 

1 191 ms 218 ms 202 ms tc3arc1.wzrd.com [216.207.4.143]

2 203 ms 201 ms 202 ms pf-2.wzrd.com [216.207.4.129]

3 203 ms 202 ms 202 ms 63.148.10.1

4 203 ms 218 ms 202 ms 24.75.2.1

5 * * * Request timed out.

6 202 ms 218 ms 234 ms g-2-1.p0-pitb.telcove.net [24.56.96.30]

7 234 ms 234 ms 234 ms phlapa1wce2-pos4-0.wcg.net [65.77.115.33]

8 249 ms 234 ms 234 ms nycmny2wcx3-pos4-0-oc48.wcg.net [64.200.240.37]

 

9 250 ms 249 ms 234 ms 64.200.249.154

10 265 ms 234 ms 233 ms te-4-4.car2.NewYork1.Level3.net [4.68.110.21]

11 234 ms 265 ms 234 ms ae-2-52.bbr2.NewYork1.Level3.net [4.68.97.33]

12 265 ms 265 ms 265 ms as-0-0.bbr2.Denver1.Level3.net [64.159.4.226]

13 281 ms 265 ms 265 ms ge-9-2.hsa1.Denver1.Level3.net [4.68.107.163]

14 281 ms 265 ms 265 ms 4.79.80.14

15 281 ms 263 ms 281 ms core-b.v33.ge-4-5.Level3.edge3.data393.net [208.

42.224.117]

16 265 ms 265 ms 265 ms rtr-dc-dist-a.v12.colo.data393.net [208.42.224.4

2]

17 265 ms 265 ms 265 ms ge-0-3-89.denver.wehostwebsites.com [208.42.236.

182]

18 265 ms 265 ms 265 ms server128.tchmachines.com [72.18.159.10]

 

Trace complete.

[stevevan]

Looks like you're on the right track...routing issue. You might want to monitor every so often and see where things slow down. Hopefully you could detect a pattern that may help solve the problem.

[Madmanmcp]

Sometimes using a dialup connection will be part of the problem. When you dial a number you don't always end up using the location that you dialed. For instance you live in Baltimore and dial into the local exchange for Baltimore but you look at the hostname and it says you are from New York. They are doing load balancing and if all the circuits are busy or in use at the Baltimore location they forward you to New York where there are open lines to use.

 

This is usually not an issue but will sometimes slow down your response times because of all the rerouting that is down. You can run a tracert today and see specific hops and run one tomorrow and find completely different ones, this will just confuse the issue sometimes.

 

What I would suggest is that you make note of what host you are on and hangup and redail and get a different connection. Then see if that corrects the problem. It may just be a slow or bad connection.