Workaround for current patcher problem

[bigjohn]

neither solutin works for me still the patcher fails to connect and keeps opening its self over and over again.

on a fresh clean instal it just gets stuck looking for a file

mail when its fixed

yawn :/

It dont work for me as well... Running Vista and cmd command with the ipconfig /flushdns does not fix it at all.

[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.

[xfluffee]

Ooh, cool. That could have been the source of my problems, as the patcher was trying to contact 85.25.140.85.

I'm not confident enough to be willing to disconnect to test it, but I will definitely watch what it's doing with the host file change next time I do have to reconnect.

Now I'm really curious what kind of data was being received from that server. The size seems a little high for just an unreachable message.

[demaea]

Nothing so far works for me at all.
Been playing for several months...
Tried all the fixes listed - even a full reinstall.
Nada...

[zerlatik]

This fix is not working for me, either. If I re-enable the patcher, it still fails to work correctly and refuses to run/crashes in the system tray multiple times. If I disable the patcher, I'm getting the game to load in the same glacially slow process that worked last night, but it gets only about halfway through and I end up with Error code 1. Not even 10 hours ago it was working, did something change?

[kiamh]

Neither worked for me. Fresh install was a no go as well.

[blaah]

start->run->notepad "c:\windows\system32\drivers\etc\hosts"
and add line at the end (to new line ofcourse)

Code: Select all

85.25.140.88 dl1.gfsrv.net

this is the temporary fix kaetemi was talking about. you should remove that line after gameforge gets .85 ip server back online or changes dns, whichever comes first.

[demaea]

start->run->notepad "c:\windows\system32\drivers\etc\hosts"
and add line at the end (to new line ofcourse)

Code: Select all

85.25.140.88 dl1.gfsrv.net

this is the temporary fix kaetemi was talking about. you should remove that line after gameforge gets .85 ip server back online or changes dns, whichever comes first.

Finally it is connecting.
My steps that worked:
1. Reinstalled game. ( saved the save folder first )

2. edited the client_default config file:
Added the 2 following command strings:

BackgroundDownloader = 1;

StartupHost = "rslogin.juk.shards.nevrax.com:40916";
(deleted the old startuphost line)

3. edited the hosts file:

start->run->notepad "c:\windows\system32\drivers\etc\hosts"
and add line at the end (to new line of course)
I added this line to the very bottom:
85.25.140.88 dl1.gfsrv.net

4. saved changes to all files
rebooted

restarted Ryzom.
it is now doing the full patch
YEAH!

Good Luck Homins

[Marjo]

We're investigating the issue and will fix this asap.

[thlau]

Wouldn't it be possible for GF to configure the IP 85.25.140.85 as an virtual IP to one of the working servers? The effect should be immediatly. And GF can do a roll back ones the defect server is running again.