Hard Light Productions Forums

General FreeSpace => Multiplayer => Topic started by: Buckshee Rounds on May 29, 2010, 12:07:56 pm

Title: Failed to connect
Post by: Buckshee Rounds on May 29, 2010, 12:07:56 pm: When trying to access multiplayer via the ready room it displays a message: "Failed to connect". I've searched through other topics and couldn't find a solution that worked. Deleted multi.cfg but that didn't work. I'm running the 3.6.12 RC2 build. Tried 3.6.10 but got the same result. As far as I know the fs2net server is up and running?

Multi log is as follows:-
Quote
FreeSpace Multi Log - Opened Sat, May 29, 2010 at 05:28PM
----
----
----

05/29 17:28:36~ psnet_init() detected lan connection
05/29 17:28:36~ psnet_get_ip() reports IP : 0.0.0.0
05/29 17:28:37~ Receive buffer set to 4096
05/29 17:28:37~ Send buffer set to 4096
05/29 17:28:37~ Error on IPX startup 10047
05/29 17:28:37~ Error on IPX startup 10047
05/29 17:28:37~ Found no RAS connections
05/29 17:28:43~ In psnet_use_protocol()
05/29 17:28:43~ Psnet : TCP broadcast
05/29 17:28:43~ Psnet using - NET_TCP
05/29 17:28:44~ NOTICE: Incompatible game tracker IP detected (gt.pxo.net), using default instead (fs2netd.game-warden.com)!
05/29 17:28:44~ NOTICE: Incompatible user tracker IP detected (ut.pxo.net), using default instead (fs2netd.game-warden.com)!
05/29 17:28:44~ NOTICE: Port for game/user trackers not specified, using default instead (12009).
05/29 17:28:44~ NOTICE: Incompatible chat server IP detected (chat.pxo.net), using default instead (fs2netd.game-warden.com)!
05/29 17:28:44~ NOTICE: Incompatible banner URL detected (chat.pxo.net), using default instead (http://fs2netd.game-warden.com/files/banners)!

----
----
----
FreeSpace Multi Log - Closing on Sat, May 29, 2010 at 05:28PM

If this is a common problem with a solution that I missed then I apologise for the new topic.
Title: Re: Failed to connect
Post by: chief1983 on May 29, 2010, 01:41:53 pm: It should be port 12000, not 12009. Do you have a fs2open_pxo.cfg in your data folder?
Title: Re: Failed to connect
Post by: taylor on May 29, 2010, 02:11:42 pm: No, 12009 is correct for the default port.

The server was down so that's the reason for the failure to connect. It should be back up and working now though. :)
Title: Re: Failed to connect
Post by: Buckshee Rounds on May 29, 2010, 02:12:28 pm: I searched for it, couldn't find anything unfortunately. After reading your post I forwarded port 12009 and lo and behold the bloody thing works now. Should've shown some initiative and done it in the first place, never mind. Thanks for the reply.

EDIT: Posted while the above replied.
Title: Re: Failed to connect
Post by: chief1983 on May 29, 2010, 02:31:59 pm: Hmm wonder why my pxo config has 12000 then. Probably shouldn't even have that file around.
Title: Re: Failed to connect
Post by: taylor on May 29, 2010, 03:12:52 pm: Quote from: chief1983 on May 29, 2010, 02:31:59 pm
Hmm wonder why my pxo config has 12000 then. Probably shouldn't even have that file around.
Port 12000 was the default port for 3.6.9, so it was valid in pre-3.6.10 builds. The servers used to run in parallel, which is why the current default is set at 12009, it needed to be an unused port.
Title: Re: Failed to connect
Post by: Darklord42 on August 07, 2010, 11:56:02 pm: Mine wont connect either

I created a file named

fs2open_pxo.cfg

with

fs2netd.game-warden.com
12009

and put it in the data folder. Is the server down, and if so, why does it show up when I load up fs2net on the browser?
Title: Re: Failed to connect
Post by: chief1983 on August 08, 2010, 12:23:24 pm: Yeah, I can't seem to connect either, with or without that file, with quite a few different builds.
Title: Re: Failed to connect
Post by: Darklord42 on August 08, 2010, 09:13:26 pm: There, now it seems to work. Although a command file doesn't seem to be needed. As I removed the file and it still works. Now all i need to do is log on at a time when there are people playing. :p