Failed to connect to server
Failed to connect to server
my brother got disconnected from server and then tried to login and it said failed to connect to server, after a while it happened to me as well. is there a way to solve this? thank you!
Guild: the Forsaken
charecters: Kibaki(SG), Rehny(Wiz), JosueK(Crus)
charecters: Kibaki(SG), Rehny(Wiz), JosueK(Crus)
Re: Failed to connect to server
It seems there's a problem with the IP routing.
I'll see about releasing a patch for a quick fix -- which should help with the coming server migration as well.
I'll see about releasing a patch for a quick fix -- which should help with the coming server migration as well.
Re: Failed to connect to server
ok thnx
Guild: the Forsaken
charecters: Kibaki(SG), Rehny(Wiz), JosueK(Crus)
charecters: Kibaki(SG), Rehny(Wiz), JosueK(Crus)
Re: Failed to connect to server
Seems that it's responding now, but if it happens again, I'll release the patch (no need to patch unnecessarily afterall).
Re: Failed to connect to server
no. its still saying failed to connect to server!
Guild: the Forsaken
charecters: Kibaki(SG), Rehny(Wiz), JosueK(Crus)
charecters: Kibaki(SG), Rehny(Wiz), JosueK(Crus)
Re: Failed to connect to server
forget it! its working XD
Guild: the Forsaken
charecters: Kibaki(SG), Rehny(Wiz), JosueK(Crus)
charecters: Kibaki(SG), Rehny(Wiz), JosueK(Crus)
Re: Failed to connect to server
I've released the patch anyways.
For anyone technical, the client uses a FQDN to connect to the server -- rather than a normal IP. This patch switches it temporarily back to a normal IP. The reason we use the FQDN is to seamlessly switch hosts without having to issue a new patch every time, but in instances where the re-routing DNS kills itself (which is completely rare), we have these issues where people can't connect -- but others stay connected. This affects the login-server ONLY as the char/map-servers utilize the plain IP address.
The reason why the old methodology is actually better though is since it updates immediately, whereas the supposed "seamless" method can taken anywhere from 5 minutes to 2 hours.
For anyone technical, the client uses a FQDN to connect to the server -- rather than a normal IP. This patch switches it temporarily back to a normal IP. The reason we use the FQDN is to seamlessly switch hosts without having to issue a new patch every time, but in instances where the re-routing DNS kills itself (which is completely rare), we have these issues where people can't connect -- but others stay connected. This affects the login-server ONLY as the char/map-servers utilize the plain IP address.
The reason why the old methodology is actually better though is since it updates immediately, whereas the supposed "seamless" method can taken anywhere from 5 minutes to 2 hours.
Re: Failed to connect to server
Ugg im getting this lame error now.
It's like "Failed to save patch file: 2009-9-12-fdata.rar (CreateFile, GetLastError: 5)
And then it closes.
It's like "Failed to save patch file: 2009-9-12-fdata.rar (CreateFile, GetLastError: 5)
And then it closes.
Re: Failed to connect to server
Did u run it as administrator? And make sure your RO isnt open [possible on MC] when patching.Jipp wrote:Ugg im getting this lame error now.
It's like "Failed to save patch file: 2009-9-12-fdata.rar (CreateFile, GetLastError: 5)
And then it closes.
Re: Failed to connect to server
Adding note that yes that was an Administrator issue. This has been resolved.