EQEmulator Forums - Checking for connection

another tool you can use to check for connection before thinking there is a problem with EQEmu's login servers is Trace Route. Open a command prompt window and type this:

tracert newlogin1.eqemulator.net

You can also create a batch file similar to this on your desktop for the easiest access.

Code:

@echo off

echo Pinging newlogin1.eqemulator.net

ping newlogin1.eqemulator.net >Logger.txt

cls

echo Running a trace route to newlogin1.eqemulator.net

tracert newlogin1.eqemulator.net >>Logger.txt

cls

Echo all done, read Logger.txt for details

echo press any key to exit

pause

if you copy paste the above code in to a batch file (.bat), put it on your desktop, and double click it after you save it, it will generate on your desktop a file called Logger.txt, you can then open that up with notepad or wordpad or whatever melts your boat and see exactly where a break down in communication is between you and the login servers.

output from my desktop

Quote:

Pinging dedicated.eqemulator.net [207.36.180.194] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 207.36.180.194:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Tracing route to dedicated.eqemulator.net [207.36.180.194]
over a maximum of 30 hops:

1 9 ms 11 ms 11 ms 10.77.0.1
2 9 ms 36 ms 11 ms POS1-1.SHPTLAHE-RTR1.sport.rr.com [24.170.96.17]
3 23 ms 23 ms 24 ms srp15-0.austtxrdc-rtr4.texas.rr.com [24.93.33.81]
4 30 ms 32 ms 32 ms son0-1-1.hstqtxl3-rtr1.texas.rr.com [24.93.33.221]
5 30 ms 32 ms 32 ms pop1-hou-P0-3.atdn.net [66.185.133.149]
6 30 ms 32 ms 34 ms bb1-hou-P0-0.atdn.net [66.185.146.96]
7 37 ms 39 ms 37 ms bb1-dls-P6-0.atdn.net [66.185.152.132]
8 38 ms 37 ms 39 ms bb2-dls-P2-0.atdn.net [66.185.153.29]
9 47 ms 50 ms 49 ms bb2-kcy-P6-0.atdn.net [66.185.152.129]
10 48 ms 50 ms 49 ms bb1-kcy-P1-0.atdn.net [66.185.152.126]
11 60 ms 63 ms 61 ms bb1-chi-P6-0.atdn.net [66.185.152.124]
12 64 ms 62 ms 61 ms pop1-chi-P0-0.atdn.net [66.185.141.85]
13 62 ms 61 ms 60 ms Qwest.atdn.net [66.185.150.210]
14 61 ms 62 ms 70 ms cer-core-03.inet.qwest.net [205.171.139.149]
15 80 ms 79 ms 78 ms dca-core-01.inet.qwest.net [205.171.8.165]
16 79 ms 84 ms 91 ms dca-core-02.inet.qwest.net [205.171.9.6]
17 87 ms 88 ms 86 ms tpa-core-01.inet.qwest.net [205.171.5.74]
18 86 ms 86 ms 88 ms tpa-core-02.inet.qwest.net [205.171.27.182]
19 93 ms 93 ms 92 ms nap-edge-01.inet.qwest.net [205.171.27.174]
20 93 ms 95 ms 94 ms 65.124.216.54
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.

As you can see, it traces to a certain point then times out, so any connection issues I have are not directly related to EQEmu.