Quote:
Originally Posted by darklight
[You must be logged in to view images. Log in or Register.]
Sorry for the double post - I didn't see a way to edit my previous post.
Can some others having a problem with the login server try a tracert command from the command prompt and paste it here? And maybe we can compare with a tracert from somebody who has a non-blank server select screen?
Here's mine:
Microsoft Windows [Version 10.0.19042.867]
(c) 2020 Microsoft Corporation. All rights reserved.
C:\Users\[removed]>ping login.eqemulator.net
Pinging login.eqemulator.net [144.121.19.169] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 144.121.19.169:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\chris>tracert 144.121.19.169
Tracing route to 144.121.19.169.lightower.net [144.121.19.169]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms DSR-250 [192.168.10.1]
2 13 ms 18 ms 6 ms cpe-66-68-80-1.austin.res.rr.com [66.68.80.1]
3 27 ms 21 ms 38 ms 66.68.1.129
4 22 ms 8 ms 26 ms agg33.ausxtxir02r.texas.rr.com [24.175.43.245]
5 25 ms 16 ms 15 ms agg22.hstqtxl301r.texas.rr.com [24.175.41.48]
6 21 ms 20 ms 20 ms ge-2-1-0.a0.sea90.tbone.rr.com [66.109.1.218]
7 22 ms 19 ms * lag-11.bear1.Houston1.Level3.net [4.59.126.33]
8 48 ms 52 ms 50 ms ae-1-3511.edge2.NewYork6.Level3.net [4.69.209.78]
9 52 ms 52 ms 48 ms FIBERTECH-N.edge2.NewYork6.Level3.net [4.30.181.126]
10 69 ms 56 ms 61 ms ae3-nycmny83jp1.lightower.net [144.121.35.38]
11 54 ms 48 ms 54 ms 144.121.109.127.lightower.net [144.121.109.127]
12 53 ms 63 ms 51 ms 160.72.248.59.lightower.net [160.72.248.59]
13 73 ms 54 ms 58 ms ae0-brtnmas6j81.lightower.net [65.254.31.58]
14 65 ms 54 ms 54 ms 144.121.7.234.lightower.net [144.121.7.234]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * ^C
C:\Users\[removed]>
The request times out after reaching 144.121.7.234.lightower.net. Based on the IP address, this seems close to reaching login.eqemulator.net [144.121.19.169] but doesn't quite make it...
|
After this morning I just had this issue start occurring. I just did a tracert to login.eqemulator.net and the results to be the same compared to what you've listed. I'm using Wifi in this RV park i'm currently staying in and this morning my wifi dongle (for some reason) disconnected and reconnected. After that happened I've started getting this issue.