Yamdoot 0 Posted July 4, 2023 How To Run a Trace Route for APB reloaded. I am unable to enter into lobby. it automatically kicks me out all the time. Asked my ISP they are asking for the trace route of reloaded. Quote Share this post Link to post Share on other sites
BlatMan 657 Posted July 5, 2023 Here's how to get the IP addresses APB is trying to connect to: - Launch APB, but do not login yet. - Run Resource Monitor. Open the network tab. Check APB.exe. - Login to APB. Don't connect to a district yet. - Check the IP addresses and ports. One of these should be the login server. The ports are not needed for the trace route, but your ISP may want them to troubleshoot. For me I see: 205.220.229.39; Local: 2899, Remote: 1001 54.173.179.85; Local: 2900, Remote: 443 3.225.184.84; Local: 2898, Remote: 443 34.237.217.247; Local: 2902, Remote: 443 Now open Command Prompt, and run the tracert command for each IP address. For my example, here's 205.220.229.39: tracert 205.220.229.39 Tracing route to 205.220.229.39 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 2 ms 6 ms 6 ms lo0-100.CMDNNJ-VFTTP-325.verizon-gni.net [72.82.234.1] 3 13 ms 15 ms 15 ms B4325.NWRKNJ-LCR-21.verizon-gni.net [100.41.3.250] 4 * * * Request timed out. 5 8 ms 12 ms 12 ms customer.alter.net [152.193.0.114] 6 61 ms 63 ms 70 ms ae12.cr4-lax1.ip4.gtt.net [89.149.128.174] 7 * * * Request timed out. 8 62 ms 63 ms 63 ms 205.220.229.39 Trace complete. You can ignore the * * * Request timed out if it continues to the next hop. If you reach 30+ hops and it's still only giving you * * *, then you know the issue is at the last hop that replied. For example, if mine looked like this, it would mean there's an issue at hop 3, IP address 100.41.3.250. tracert 205.220.229.39 Tracing route to 205.220.229.39 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 2 ms 6 ms 6 ms lo0-100.CMDNNJ-VFTTP-325.verizon-gni.net [72.82.234.1] 3 13 ms 15 ms 15 ms B4325.NWRKNJ-LCR-21.verizon-gni.net [100.41.3.250] 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 * * * Request timed out. 8 * * * Request timed out. ... 1 Quote Share this post Link to post Share on other sites
Yamdoot 0 Posted July 5, 2023 Thank you so much brother. Merged. Tracing route to ec2-3-213-249-23.compute-1.amazonaws.com [3.213.249.23] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.0.1 2 1 ms <1 ms <1 ms MYGROUP [192.168.1.1] 3 2 ms 1 ms 1 ms 103.117.14.2 4 3 ms 2 ms 1 ms 103.117.14.49 5 3 ms 3 ms 2 ms 121.240.110.109.vsnl.net.in [121.240.110.109] 6 23 ms 22 ms 22 ms 172.28.176.177 7 23 ms 22 ms 23 ms ix-ae-1-100.tcore2.mlv.as6453.net [180.87.39.25] 8 223 ms 223 ms 223 ms if-ae-2-2.tcore1.mlv.as6453.net [180.87.38.1] 9 * * * Request timed out. 10 222 ms 222 ms 222 ms if-be-21-2.ecore4.emrs2-marseille.as6453.net [195.219.174.129] 11 221 ms * 222 ms if-ae-8-2.tcore2.l78-london.as6453.net [195.219.186.20] 12 * 222 ms * if-ae-2-2.tcore1.l78-london.as6453.net [80.231.131.2] 13 * * * Request timed out. 14 219 ms 219 ms * if-ae-1-3.tcore4.njy-newark.as6453.net [216.6.57.6] 15 219 ms 219 ms 219 ms if-bundle-12-2.qcore2.aeq-ashburn.as6453.net [66.198.155.32] 16 224 ms 223 ms 223 ms 63.243.137.136 17 218 ms 217 ms 218 ms 216.6.87.251 18 * * * Request timed out. 19 * * * Request timed out. 20 219 ms 218 ms 225 ms 52.93.28.246 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. If am right, there's an issue at hop 20 or I have tracert wrong address? Quote Share this post Link to post Share on other sites
BlatMan 657 Posted July 5, 2023 You might have the wrong address. It times out for me as well. There should be 3 or 4 addresses listed. I don't know which one APB uses for logging in. Quote Share this post Link to post Share on other sites
