[William Wolfen]

i continually get the unable to connect message, and have followed the multimpalyer setup guide to the letter.  I'm running the 3.6.10exe, with the mediavps.  i also have the multi-mission pack installed as well.  not sure what the problem is, so if anyone has any ideas, it would be appreciated!

[William Wolfen]

never mind, figured out wut i did wrong.

[karajorma]

What was it? Worth knowing for the next person who has this problem.

[The E]

It seems I have the same problem all of a sudden. I keep getting an "Unable to connect to the fs2netd server" message. I redid all the steps in the manual, to no avail.
However, I am able to connect when using TBP, so I'm kinda wondering what's going on here.

[captain-custard]

maybe there has been an update? and we need a new build

[FUBAR-BDHR]

Everyone should be using RC2.  One thing to check for is an old PXO multi.cfg file in your data directory.  If you have one that points to the PXO servers you won't be able to login.  Just delete or rename it.

[The E]

Did that already. Still nothing.

Here's my multi.log from my latest attempt:

Code: [Select]

FreeSpace Multi Log - Opened Fri, May 29, 2009  at 08:51PM
----
----
----


05/29 20:51:03~   psnet_init() detected lan connection
05/29 20:51:03~   psnet_get_ip() reports IP : 0.0.0.0
05/29 20:51:03~   Receive buffer set to 4096
05/29 20:51:03~   Send buffer set to 4096
05/29 20:51:03~   Error on IPX startup 10047
05/29 20:51:03~   Error on IPX startup 10047
05/29 20:51:03~   Found no RAS connections
05/29 20:51:25~   In psnet_use_protocol()
05/29 20:51:25~   Psnet : TCP broadcast
05/29 20:51:25~   Psnet using - NET_TCP
05/29 20:51:26~   NOTICE: Address for game tracker not specified, using default instead (fs2netd.game-warden.com).
05/29 20:51:26~   NOTICE: Address for user tracker not specified, using default instead (fs2netd.game-warden.com).
05/29 20:51:26~   NOTICE: Port for game/user trackers not specified, using default instead (12009).
05/29 20:51:26~   NOTICE: Address for chat server not specified, using default instead (fs2netd.game-warden.com).
05/29 20:51:26~   NOTICE: URL for banners not specified, using default instead (http://fs2netd.game-warden.com/files/banners).


----
----
----
FreeSpace Multi Log - Closing on Fri, May 29, 2009  at 08:51PM


[FUBAR-BDHR]

Do you have 7117 as well as 7808 open on your router?  The lobby uses 7117 and that may not be in the instructions since they were written for 3.6.9 which had no lobby.

[The E]

Yes, both ports are open on both TCP and UDP.
As I said, it works fine when using TBP, but FS2 (both with and without mvps) refuses to connect.

[William Wolfen]

Everyone should be using RC2.  One thing to check for is an old PXO multi.cfg file in your data directory.  If you have one that points to the PXO servers you won't be able to login.  Just delete or rename it.

that was my problem, i didnt have RC2.

[FUBAR-BDHR]

You don't have anything in force port or force IP in the launcher do you?

[The E]

Nope. Nothing at all.

[FUBAR-BDHR]

For troubleshooting copy your multi.cfg from TBP over to FS2 and try getting to the lobby.  Delete it after as it will cause problems otherwise. 

[The E]

Did that, seemed to work.

[captain-custard]

same here .........

has there been a server update one wonders?

i had already done that with the TBP multi, that works

but fso will not load up at all without it on any RC build

[FUBAR-BDHR]

Defiantly a server side issue sometime overnight.  I reset the standalones after midnight and they logged in and still show logged in on my end but not on FS2netD.  Seems to be just the FS2 3.6.10 daemon.  TBP is working. 

[captain-custard]

TAYLOR ...please help !!!!!!

[taylor]

Should be up and going again.

[captain-custard]

thanks loads ..........;