| Applies To: |
|
| Summary: |
| I am having intermittent communication
problems on my Citect servers and clients, is there a way to log
network trace messages between the servers and clients. I do not
want to use or install a 3rd party network analysing software on
the citect machines. |
| Solution: |
| Besides the normal 'ping' test, there is
another method to trace and log the network traffic between 2
machines. Running a 'tracert' (short for Trace Route) command can
help identify where the connection problems are occurring. The
tracert program tests the connection from your computer to the
target location you specify and every "hop" in between. Using this
program you can determine at what location the data you are sending
is running into a problem. Steps to run the tracert command - Click Start and then Run - Type command and press Enter - In the command window, type 'tracert IPaddress> C:\tracert.txt' (without the quotes) and press the Enter key. A file will be created on your C: drive called tracert.txt that contains your route information. Please be patient when waiting for the tracert command to complete, it may take several minutes. When you are returned to the command prompt, then the trace is complete. - Type exit and press the Enter key to close the command window. I ran tracert, now what do I do? Open the tracert.txt file. You will see 3 kinds of information regarding the route that internet traffic is taking from your computer to the client/servers: - The number on the far left is the hop number. - The next 3 numbers (with 'ms' after each one) is the length of time, in milliseconds, it takes for your computer to receive a response from the computer you are trying to contact. A high value, for example greater than 200 ms for broadband or 350 ms for dial-up, indicates that traffic is slow, and can cause latency. Asterisks (*) indicate that your computer did not receive a response from the computer you are trying to contact at all, which can keep you from connecting to the servers altogether, or cause you to be disconnected abruptly. - The final piece of information is the DNS (or 'name') and/or the IP number of server you are trying to contact on this hop. If you did not receive any responses from this server, you may receive an error message such as 'Request Timed Out' or 'Destination Net Unreachable'. If you see any error messages or asterisks in your tracert.txt for the hops before you reach the client/servers, you may need to contact your network administrator and provide them your tracert results for further assistance. Bad Trace messages. Tracing route to 192.168.10.2.29. over a maximum of 30 hops 1 <1 ms <1 ms <1 ms AQUARIUS [192.168.10.2.29] 2 * * * Request timed out. 3 * * * Request timed out. 4 * * * Request timed out. 5 * * * Request timed out. . . . . . 30 * * * Request timed out. Trace complete. Good Trace message. Tracing route to www.yahoo.akadns.net [66.94.230.41] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 10.176.233.240 2 1 ms 1 ms 1 ms 203.166.5.201 3 1 ms 1 ms 1 ms 534.ge-4-1-0.GW4.SYD2.ALTER.NET [210.80.189.1] 4 1 ms 1 ms 1 ms 0.so-3-2-0.XT1.SYD2.ALTER.NET [210.80.38.217] 5 160 ms 159 ms 159 ms 0.so-5-1-0.IR1.SAC2.ALTER.NET [210.80.49.1] 6 166 ms 166 ms 166 ms POS2-0.IR1.SAC1.ALTER.NET [137.39.31.190] 7 156 ms 156 ms 156 ms 0.so-0-0-0.TL1.SAC1.ALTER.NET [152.63.0.114] 8 168 ms 168 ms 168 ms 0.so-5-0-0.XL1.SCL2.ALTER.NET [152.63.57.41] 9 160 ms 160 ms 160 ms 0.so-6-0-0.BR1.SCL2.ALTER.NET [152.63.57.49] 10 163 ms 163 ms 164 ms 204.255.173.42 11 169 ms 160 ms 160ms so-1-2-0.bbr2.SanJose1.Level3.net [209.244.3.141] 12 169 ms 160 ms 162 ms ge-10-2.ipcolo3.SanJose1.Level3.net [4.68.123.139] 13 165 ms 165 ms 165 ms unknown.Level3.net [64.152.69.30] 14 160 ms 173 ms 170 ms ten-1-3-bas2.scd.yahoo.com [66.218.82.219] 15 160 ms 160 ms 160 ms p10.www.scd.yahoo.com [66.94.230.41] Trace complete. |
| Keywords: |
| tracert, networks, networking, troubleshooting networks |
Related Links
Attachments