Login server connection issues.... (just me?)
 

I appear to be having issues with the login server.

"A connection to the server could not be reached. Please check your internet connection to make sure you are online."

Obviously being connected isn't the problem if i am making a post. Anyone else experiencing difficulties today? I first thought maybe it was an issue with p99 because I was using "Quick Connect". I checked the website and the server is up. So I gave it another go. I can't even reach the server list by hitting "Login"

If no one else is experiencing difficulties can someone give me some pointers on things I might need to check? Keep in mind I haven't had issue and have been playing on the p99 server for about 3 months now. This all occurred over night.


Thanks in advance.

Things to check are that no-one in your house is running BitTorrent at the moment, or otherwise running a large download that is saturating your Internet connection. The UDP protocol used by EQEmu can be sensitive to packet-loss, especially it seems, the login server.

To see if you are getting packet loss, you could open a command prompt and execute
and let it run for a while.

If your DSL/Cable link is not busy, there could still be issues at your ISP or other networks between your ISP and the login server.

If you are using wireless, try a hard-wired connection to your router, if possible.

Thanks, I didn't think to run a ping test. I did have Bit Torrent up earlier but it had been closed for about 30 minutes before I tried to log in and hadn't been downloading/uploading since last last night.

Ping test appears to have been running fine. No time outs or fluctuations in response time. Overall it held pretty solid.

However, still now dice on connecting. Going to reboot and see if that helps. Everything else is running flawlessly. :-? lol


EDIT: After restart still no dice. Ran a speed test also showing everything as normal from my ISP, 20meg down and about 1.5meg up. I'm at a loss at this point.

C:\Users\Chris>tracert www.eqemulator.org

Tracing route to eqemulator.org [67.23.190.71]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.2.1
2 12 ms 9 ms 9 ms ----------------1.dhcp.insightbb.com [-----------------]
3 8 ms 18 ms 20 ms 74-128-19-121.dhcp.insightbb.com [74.128.19.121]

4 10 ms 10 ms 9 ms 74.128.9.229
5 22 ms 24 ms 21 ms xe-4-3-3.edge5.Atlanta2.Level3.net [4.59.12.61]

6 22 ms 21 ms 36 ms ae-17-51.car1.Atlanta4.Level3.net [4.69.150.7]
7 22 ms 26 ms 22 ms NETRIPLEX.car1.Atlanta4.Level3.net [4.53.233.38]

8 30 ms 27 ms 26 ms 67.23.161.137
9 27 ms 26 ms 28 ms te-5-5.rtr2.avl1.netriplex.com [67.23.161.254]
10 26 ms 26 ms 29 ms eqemulator.net [67.23.190.71]

Trace complete.


Removed IP address for safety.

Even went as far as to do a system restore back to a previous date. Still no dice.


EDIT : Also tried a separate install I have configured for EZ Server. Still no dice with the login server. Wanted to make sure it wasn't something weird in the installation that got corrupted or something.
EDIT AGAIN : I only used hard wired connections for gaming. If it were ISP related what would I want to ask them to check? To my unprofessionally trained eyes the trace route appeared fine.


Any suggestions?

Was going to edit this in above bit evidently I'd edited to many times. hahah
Results from the ping test.

Ping statistics for 67.23.190.71:
Packets: Sent = 328, Received = 328, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 55ms, Average = 31ms

Have you changed anything on your computer that might affect it? New firewall or antivirus? Have you rebooted your router and cable/dsl modem?

No new software or anything. I would like to point out the ever so typical "over thinking" of IT issues. Simple reboot of router and modem worked. I honestly never considered it. To think I've been sitting here refreshing the thread other then going back to basics.

Thanks lerxst2112 for making me feel dumb. ;-)

lol, I'm glad it helped. :) I'll admit it's not always the first thing I think of either, but with the way most routers leak memory and other resources, it's never a bad bet when weirdness happens.