|
|
#1
03-14-2021, 04:54 PM
|
|||
|
blank server screen
today and 2 days ago when i try to log in the server screen is blank any ideas?
| ||
|
|||
|
#2
03-14-2021, 05:06 PM
|
|||
|
This is usually due to a bad connection. Can try re-logging a few times to see if they'll pop up
Any latency/dropped packets will result in this. Wifi connection has been a known cause for some and sometimes its ISP/routing issues and a VPN can be a test/workaround
__________________
Kav
| ||
|
|
|||
|
#4
03-15-2021, 11:06 PM
|
|||
|
I have also been having this problem recently, the timing is odd because it's not just one person having the issue. Tried restarting the router, etc. No such luck.
Pinging login.eqemulator.net results in request timed out on multiple PCs and even on my cell phone, which is not online through my router. | ||
|
|
|||
|
#5
03-16-2021, 09:08 AM
|
|||
|
tracert to login.eqemulator.net
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... | ||
|
|
|||
|
#6
03-16-2021, 02:49 PM
|
|||
|
Okay, just was able to login - I had to UNPLUG my router for a minute to restart it - using the router's soft-reboot feature didn't work, even though it seemingly "restarted" and every other program I tried to use worked fine.
If you're still having problems it's worth trying that before all the other hoops you might try jumping through. | ||
|
|
|||
|
#7
03-23-2021, 01:29 PM
|
||||
|
Quote:
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. | |||
|
|
||||
|
#8
03-24-2021, 12:02 AM
|
||||
|
Quote:
__________________
Bushido - 58 Erudite Wizard
Budoshi - 60 Human Monk Nekst - 60 Ogre Shaman Tsuku - 1 Dark Elf Enchanter Cicada 3301 | |||
|
|
||||
|
#10
03-24-2021, 08:11 AM
|
|||
|
I live in a rural area, and use a WiFi internet service. Sometimes usually in evening The Internet is slow the this happens. Just restart the modem and usually fixes this
| ||
|
|
|||
 |
|
|
Linear Mode
