PrivateIdaho
06-01-2002, 10:29 AM
I've spent probably 25 hours in the last 7 days playing on several different peoples servers, and I see several common issues:
1. disconnection while in game
2. click on server, get to char screen, inability to get into game
3. click on server, get dumped back to server screen.
Focusing on #3, which is happening on my own personal server, sitting 6ft from me..
The error that I get in the world log is thus (sorry, scrolled by, not a direct quote)
"Attempt to login while not connected to login server"
I think 1,2 and 3 might all be releated to the same thing, TCP timeouts to login server.
Here's what I see in the world log, when the server is sitting idle:
Connected to LoginServer: eqlogin1.eqemu.org:5999
64.81.113.117:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin2.eqemu.org:5999
67.82.235.162:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin2.eqemu.org:5999
67.82.235.162:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin2.eqemu.org:5999
67.82.235.162:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin1.eqemu.org:5999
64.81.113.117:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin1.eqemu.org:5999
64.81.113.117:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin2.eqemu.org:5999
67.82.235.162:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin2.eqemu.org:5999
67.82.235.162:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin1.eqemu.org:5999
64.81.113.117:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin2.eqemu.org:5999
67.82.235.162:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin2.eqemu.org:5999
67.82.235.162:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin1.eqemu.org:5999
64.81.113.117:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin1.eqemu.org:5999
64.81.113.117:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin1.eqemu.org:5999
64.81.113.117:5999: TCPConnection::SendData(): Connection timeout
Error: LoginServer::Connect: ''
Error: LoginServer::Connect: ''
Connected to LoginServer: eqlogin2.eqemu.org:5999
67.82.235.162:5999: TCPConnection::SendData(): Connection timeout
However, it's not a Layer2/Layer3 problem IMHO, but higher up... why do I say that?
--- gremlin.eqemu.org ping statistics ---
1000 packets transmitted, 1000 packets received, 0% packet loss
round-trip min/avg/max = 87.3/89.5/94.5 ms
In my novice opinion, this appears to be a problem with the login server itself. Ideas? Thoughts? Tell me what I'm doing wrong?
I'd be happy to help troubleshoot this in any way that I can.
1. disconnection while in game
2. click on server, get to char screen, inability to get into game
3. click on server, get dumped back to server screen.
Focusing on #3, which is happening on my own personal server, sitting 6ft from me..
The error that I get in the world log is thus (sorry, scrolled by, not a direct quote)
"Attempt to login while not connected to login server"
I think 1,2 and 3 might all be releated to the same thing, TCP timeouts to login server.
Here's what I see in the world log, when the server is sitting idle:
Connected to LoginServer: eqlogin1.eqemu.org:5999
64.81.113.117:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin2.eqemu.org:5999
67.82.235.162:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin2.eqemu.org:5999
67.82.235.162:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin2.eqemu.org:5999
67.82.235.162:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin1.eqemu.org:5999
64.81.113.117:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin1.eqemu.org:5999
64.81.113.117:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin2.eqemu.org:5999
67.82.235.162:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin2.eqemu.org:5999
67.82.235.162:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin1.eqemu.org:5999
64.81.113.117:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin2.eqemu.org:5999
67.82.235.162:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin2.eqemu.org:5999
67.82.235.162:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin1.eqemu.org:5999
64.81.113.117:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin1.eqemu.org:5999
64.81.113.117:5999: TCPConnection::SendData(): Connection timeout
Connected to LoginServer: eqlogin1.eqemu.org:5999
64.81.113.117:5999: TCPConnection::SendData(): Connection timeout
Error: LoginServer::Connect: ''
Error: LoginServer::Connect: ''
Connected to LoginServer: eqlogin2.eqemu.org:5999
67.82.235.162:5999: TCPConnection::SendData(): Connection timeout
However, it's not a Layer2/Layer3 problem IMHO, but higher up... why do I say that?
--- gremlin.eqemu.org ping statistics ---
1000 packets transmitted, 1000 packets received, 0% packet loss
round-trip min/avg/max = 87.3/89.5/94.5 ms
In my novice opinion, this appears to be a problem with the login server itself. Ideas? Thoughts? Tell me what I'm doing wrong?
I'd be happy to help troubleshoot this in any way that I can.