Page 2 of 2
Re: Stuck while checking for patches
Posted: Tue Mar 27, 2007 2:16 am
by oldmess
oldmess wrote:... getting the same problem as the original poster.
Update: turning off my firewall completely is allowing the patching system to work. If there is a change in which ports the game is using, could someone point me to that documentation so I can configure the firewall properly instead of just leaving it off completely? Thanks
Turning it back on after the patch allows me to play ok, but will it hit me again at the next patch? Guess I'll find out.
Update #2: Was told by a guildie when I finally got logged in that a server reboot or crash or something had just occurred; it's possible that's what was causing my problems. So, if there are no firewall/port changes... nevermind.
Re: Stuck while checking for patches
Posted: Tue Mar 27, 2007 2:59 am
by ejizzle
well ive still got this problem, ive even uninstalled and reinstalled Ryzom, and now when i try to connect it tries to get the file: ryzom_00610.ldx. it stays there for a bout a min and then it crashes. ive reinstalled twice now, same ****. ive also disabled norton while trying to launch. this sux !!! i needs ma fix ! anyone help ?
Re: Stuck while checking for patches
Posted: Tue Mar 27, 2007 11:39 pm
by adamfsu
Same problem here, been working on it for several hours. Still no luck.
Re: Stuck while checking for patches
Posted: Wed Mar 28, 2007 12:03 am
by kaetemi
So... They gave us this nice little test page, and from there I did some small tests:
http://dl1.gfsrv.net:40916/patch_live/test.txt <- this one.
When you do a dns lookup on the dl1, you get 3 IPs:
85.25.140.88, 85.25.140.85, 85.25.140.86
Which means that the following are most likely also valid urls (assuming that they're not virtual hosts):
http://85.25.140.88:40916/patch_live/test.txt <- WORKS
http://85.25.140.85:40916/patch_live/test.txt <- DOES NOT WORK
http://85.25.140.86:40916/patch_live/test.txt <- WORKS
So basically, it's just 1 server of the three under the domain that does not seem to be working. (Your system randomly chooses 1 of them.)
Suggestion: Let the login server system give multiple patch server IPs to the client instead of randomly choosing one from the dns system, and when one of them fails, the patcher can still use the next one and automatically report that one is down.
Temporary Fix: Edit your hosts file, only if you know what you're doing.