Author Topic: solutions for those naster "server failed" messages on the opening screen  (Read 1113 times)

Technomage

  • Traveller
  • *
  • Posts: 12
    • View Profile
ok, some (if not all) of you have noticed at times that the server (laanx.fragnetics.com)
appears to be unreachable by your client. mostly, this is due to either a server hiccup
(common) or DNS failure.(also common).

this post addresses the latter.  8)

firstly, you need to know the ip address for laanx.fragnetics.com (its 203.81.44.242)!  :thumbup:

you add and entry to your hosts file (in windows its under /windows/system32 or /winnt/system32)
and in linux its /etc/hosts (you may have to search in windows as each version might put it in a place ither than listed).

the entry to add is:
203.81.44.242     laanx.fragnetics.com

once added, your machine should be able to find it without worrying about those pesky dns timeouts.  \\o// :sorcerer: :thumbup: :woot:


Caarrie

  • Forum Addict
  • *
  • Posts: 3369
  • We want no UNFIXED bugs!!!!!!!!!!!!!
    • View Profile
    • PlaneShift3dMods
Re: solutions for those naster "server failed" messages on the opening screen
« Reply #1 on: December 03, 2007, 11:59:42 am »
I would not recomend doing this, as the ip address for fragnetics DOES change. The better solution would be to open /data/servers.xml and add a new line
Code: [Select]
<server name="laanx" ip="[current ip address for laanx]" port="7777" />

putting in the current ip address and then logging in.

Induane

  • Veteran
  • *
  • Posts: 1287
  • What should I put here?
    • View Profile
    • Vaalnor Inc.
Re: solutions for those naster "server failed" messages on the opening screen
« Reply #2 on: December 03, 2007, 09:18:57 pm »
Caarrie is correct here.  I might call the 2nd one laanx_alternate or similar but its still a better solution than changing your hosts file. That way you can see both and if the alt is working and laanx main is not then you know its the dns problem, if both are failing then likely the server is down.

Changing your hosts file basically ensures future problems because once the server ip changes then it won't ever work again until you modify the host file manually.

  Also I'm fining you 4000 trias for excessive smiley usage! ;)
« Last Edit: December 03, 2007, 09:24:24 pm by Induane »

Metaltyty

  • Wayfarer
  • *
  • Posts: 1
    • View Profile
Re: solutions for those naster "server failed" messages on the opening screen
« Reply #3 on: December 06, 2007, 09:31:57 pm »
i'm sorry, i did all the thing you wrote but the server still appear "failed".


config:
Toshiba satellite A200
Windows XP Pro sp2
Graphic card: NVIDIA GeForce Go 7300  (256 Mo)
Processor   Mobile DualCore Intel Pentium M, 1866 MHz (14 x 133)
Wireless connection

tell me exactly the information you need for help me

(i'm french, sorry if you don't understand my english...)


Technomage

  • Traveller
  • *
  • Posts: 12
    • View Profile
Re: solutions for those naster "server failed" messages on the opening screen
« Reply #5 on: December 29, 2007, 11:34:54 am »
Caarrie is correct here.  I might call the 2nd one laanx_alternate or similar but its still a better solution than changing your hosts file. That way you can see both and if the alt is working and laanx main is not then you know its the dns problem, if both are failing then likely the server is down.

Changing your hosts file basically ensures future problems because once the server ip changes then it won't ever work again until you modify the host file manually.

  Also I'm fining you 4000 trias for excessive smiley usage! ;)

considering that laanx.fragnetics.com is a fixed IP (assigned by fragnetics), I rather much doubt it will change for the foreseeable future (unless someone sets up multiple servers and has them all mirrored across the net for redundancy).

*edit*

i'm sorry, i did all the thing you wrote but the server still appear "failed".


config:
Toshiba satellite A200
Windows XP Pro sp2
Graphic card: NVIDIA GeForce Go 7300  (256 Mo)
Processor   Mobile DualCore Intel Pentium M, 1866 MHz (14 x 133)
Wireless connection

tell me exactly the information you need for help me

(i'm french, sorry if you don't understand my english...)

There are going to be times where the "server failed" message will appear that has nothing to do with DNS issues.
this temp fix was just to correct the DNS problems (of which there tseem to be a lot of cox.net services where I am)
« Last Edit: December 29, 2007, 02:21:19 pm by neko kyouran »

Caarrie

  • Forum Addict
  • *
  • Posts: 3369
  • We want no UNFIXED bugs!!!!!!!!!!!!!
    • View Profile
    • PlaneShift3dMods
Re: solutions for those naster "server failed" messages on the opening screen
« Reply #6 on: December 29, 2007, 02:32:18 pm »
Caarrie is correct here.  I might call the 2nd one laanx_alternate or similar but its still a better solution than changing your hosts file. That way you can see both and if the alt is working and laanx main is not then you know its the dns problem, if both are failing then likely the server is down.

Changing your hosts file basically ensures future problems because once the server ip changes then it won't ever work again until you modify the host file manually.

  Also I'm fining you 4000 trias for excessive smiley usage! ;)

considering that laanx.fragnetics.com is a fixed IP (assigned by fragnetics), I rather much doubt it will change for the foreseeable future (unless someone sets up multiple servers and has them all mirrored across the net for redundancy).

How about the SERVER has had the IP address change and it has changed a FEW times, so PLEASE do not do this