Tech support question -> tech support section
I can only think of a few causes of disconnections not associated with lag:
* Network issues that manifest as a temporarily dropped connection, rather than lag (including ISP problems as well as bad routers, wifi problems, etc)
* Power management shutting down parts of the computer that RO needs. To make RO stay running, the only thing you can turn off is the display. Power management for everything else needs to be turned off. Most of these settings are under "change advanced power settings" not the idiot-mode screen at Control Panel -> Power Options -> Edit Plan Settings. I have one network adapter (Dell E6400 built-in wired) which ignores power management settings and goes into power save mode anyway.
Some questions to narrow down what we're dealing with:
* What kind of disconnections are they? Is it "disconnected from server", or "disconnected due to time gap"?
* Are they preceeded by a lag spike? (where everything stops for a while before the game recognizes the DC)
* Do they happen while actively playing, or only while AFK? (if only while AFK, this strongly suggests a power management issue)
* How regularly timed are the DC's, if you know? If it's a consistent length of time (particularly if it's a round number), that really narrows things down.
* Are you using wifi, or wired connection between router and computer? Try using wired connection. It is not unusual for a WiFi network to not be stable enough for gaming.
A tracert is not going to be very useful for debugging this, because you would need to be taking it while the problem occurs to see anything - though sometimes I've had success entering the tracert command with -d option in command window (ie, tracert -d iro.ragnarokonline.com the -d is important when trying to catch a transient problem like this; it disables resolving domain names at each hop, so it runs faster, and you're more likely to catch the problem before it goes away again), then as soon as RO starts to DC, tab back to it and hit enter, and if you're faster than the problem fixes itself, you might see the source of it. But this is not as useful, because it's only a positive test - it can tell you for sure it's a problem on the network, but if it doesn't show the problem, you don't know if you just missed it, or whether it's something unrelated. Tracert is much better suited towards detecting ongoing lag. See the pinned thread in tech support section for more info on running tracerts and posting results.
Edited by DrAzzy, 19 March 2014 - 07:54 AM.