Connection problems

[Ultra Morgan]

Hello. Since last week I've been having connection problems.

From what I've seen, the connection isn't stable. The game runs normally until—at some point in a room—I kill a few monsters; then, after a few seconds, the loot appears and everything goes back to normal for a while (in the best-case scenario). But usually, the loot doesn't appear, and I get Error #100 telling me to check my network cable.

I live in Argentina (I know, I'm far from the server) and I play on PC with a wired connection. I've been playing on the server for months; this used to happen occasionally—maybe once or twice a week max—but now I can't finish a single run. I realize it's likely an issue with my ISP... or the routing between my home and the server.

I’d like to know if there’s a way to increase the timeout duration before the game closes the session, or a way to check my connection to the server before I start playing... or anything really. My current situation is quite frustrating.

P.S.: If I happen to try logging in during those moments of disconnection, I get Error #903.

P.S.2: Ty Ender <3

 

[Ultra Morgan]

Ok, I ran a ping test to ephinea's web. Here are the results:
Ping statistics for 74.91.117.244:
Packets: Sent = 2652, Received = 2606, Lost = 46
(1% loss),
Approximate round-trip times in milliseconds:
Minimum = 225 ms, Maximum = 274 ms, Average = 230 ms


I don't know if this information is representative of how my connection to the game servers works, but I wanted to give it a try.

 

[Ender]

I’d like to know if there’s a way to increase the timeout duration before the game closes the session, or a way to check my connection to the server before I start playing... or anything really. My current situation is quite frustrating.

The client's disconnect timeout has been disabled for a few years here. The server does have a timeout if a client doesn't respond to some packets after enough time. The game uses TCP so a timeout here means your client probably isn't sending any packets to the server, and a dropped *connection* for TCP means the connection is broken.

P.S.: If I happen to try logging in during those moments of disconnection, I get Error #903.

The only thing in the server logs is that you're disconnecting due to ping timeout a few times. Some of your disconnects are your client closing the connection unexpectedly.

It really sounds like your ISP just doesn't like the server. BTW the login and Fodra are at ephinea1.pioneer2.net. The website is on a different host entirely. So you might want to try pinging that instead.

 

[Ultra Morgan]

BTW the login and Fodra are at ephinea1.pioneer2.net. The website is on a different host entirely. So you might want to try pinging that instead.

Ok, the new test gave me this results:
Ping statistics for 34.223.124.214:
Packets: sent = 9882, received = 9864, lost = 18
(0% loss),
Approximate round-trip times in milliseconds:
Minimum = 220ms, Maximum = 346ms, Average = 225ms

It looks better, but keep in mind that the test was conducted during off-peak hours.
If the problem persists, I’ll be contacting my ISP later this week... though, sadly, I don't have much faith that it's something they can fix.

I will keep you informed of any updates.