Well, most FAQ’s I have read go into too much technical detail for most people to understand. Basically a trace is like a map from your modem right through to the web site, news group, etc. It defines each step that your connection takes to get from you to the address. Think of it like giving someone directions to get their house to yours, giving them the best route to get there. That is what a trace does. Finds the best route to a web address or news/mail address. And we all know things can go wrong sometimes when trying to reach a certain address. What causes this? Well, again most FAQ’s are very technical; so let me explain it like this. Remember the older days when phones where more or less new technology? And when you wanted to phone someone you had to go through an operator, who then perhaps passed you on to another operator and so on until you reached the person you wanted? Well, imagine what would happen if one of those operators wasn’t available. You would get passed to that exchange and then… Nothing. You wouldn’t be able to get any further than that with your call. This is basically what happens when you can’t reach an address. As for why this happens, most non-technical people don’t want or need this information for posting and support will usually fill you in on what is causing it once they have looked into the problem.
Many people seem to have problems with doing traces, not even knowing where to start. And it can get frustrating when all support will say is “please post traces to the addresses you are having problems with”, but don’t tell you how to carry it out. Well, this is a basic (and I hope, easy to understand) break down of how to carry out a trace. There are two ways to do a trace, both ways heaving their own sticking points. The first method is simple is you know how to look for a file, as it writes the trace up in the file you specify. The second way is easy if you know how to use a DOS box, but if the traces are long they can disappear off the top of the box and you lose that part of the information. I, however, prefer using method two, as you don’t need to go looking for any text files as it is all done on the one screen. But, I will let you decide the best method for using yourself.
The screen should start to scroll up with information looking something like this:
Tracing route to v38.go2net.com [206.253.217.38
over a maximum of 30 hops:
1 153 ms 139 ms 149 ms usr1389-edi.cableinet.co.uk [213.48.66.218]
2 145 ms 149 ms 149 ms 213.48.58.2
3 165 ms 149 ms 149 ms 194.117.133.50
4 175 ms 150 ms 148 ms ATM5-ED-HSD-GSR-LINX.cableinet.net [194.117.140.162]
This is the information support look for. Once the dos prompt has come back, the trace is finished. To copy it over into a post:
The trace can be done for several of the sites you are having problems with and copied and pasted accordingly. Once this is all done, send your post. Again, make sure you post to the correct ng, otherwise it may be ignored.
Suggested site for tracert’s include the BBC - http://www.bbc.co.uk and Virgin Media - http://www.virginmedia.com However we would also suggest trying Google - http://www.google.co.uk
Powered by WordPress