I find it hard to believe nobody would want to do this ..

It sound to me like you're wanting to set the server up to be automated, yet remotely accessable? I'm I on the right page with you?

Here's the deal ..

In order for me to launch the server as it is now, I have to login via terminal server and start it, this prevents any other terminal server connections.

The ideal solution, which I have used for running quake, UT, MOHAA and various other games in the past.. is to set it up to run as a service so I can start it and then logoff.

If I start it now and logoff, the server stops..

Then have you considered starting the server right through the resident terminal server software? From that point on it would be a simply matter of remotely connecting to the computer via the terminal server software to monitor/restart/shut down the FL server. Doing so gives you rights to desktop items (ICONS) or anything you desire once you configure the software locally.

Been done with FL. There are others way beside this to make it happen too.

That's exactly the problem.

In order for the FL server to be running, I have to be logged into windows, being logged in prevents someone else from logging in even if I'm disconnected from the terminal server session.. Terminal server licensing looks at the number of people logged in, not at the number of people connected.. even a console login counts, which is stupid if you ask me ..

I need to get the FL server to remain running when I logout.. I'm not the only one who needs access to the server, so I can't simply leave myself logged in 24/7

So the solution is to make FL run as a service as I've done with other games in the past, but FL doesn't seem to like this.

---

So the solution is to make FL run as a service as I've done with other games in the past, but FL doesn't seem to like this.

---

This part of your post I would need some clarification on because it's a pretty general statement. I have seen the FL server work in the very way I've described above. I can only tell you what I know. What specific problems do you seem to be having because at this point I'm clueless why I can do it and you can not.

Clarification .. let me see

Do this ..

Log into your server with terminal server, start up the FL server and then log out of windows.

The FL server, as well as any other non-service apps, close.. they terminate as you log out of windows.

Only way to keep the FL server running is to disconnect, but remain logged in.. This is fine and dandy, but windows sees that I am logged in and the terminal server license is taken up, noone else can connect via terminal server until I reconnect and logout of windows.. and as a result, FL closes again.

The only way for the FL server to survive my logging out is if it were running as an XP service.. services run as the system user and remain running in the background, regardless of who is logged on.

It's important that I can run FL in this way.. other games have no problem with this, Gamehost, Firedaemon, Srvany .. these are all programs designed for things like this.. making normal apps survive a logoff.

I hope that helps..

---

Log into your server with terminal server,start up the FL server and then log out of windows

---

That right there is the difference! You can use the terminal server software on the computer you're going to host the Freelancer server software and actually initiate the Freelancer server within the terminal server software (confused yet?). While doing this you can set up the terminal server so it will accept remote logins/passwords. Then you can connect from afar and start/stop/restart the server software to your heart content.

Yes, you will need to actually stay logged into the computer running the terminal server software (which is also being used to run the Freelancer server software) but that means you don't have to be sitting at the server to administer the thing.

Works like a charm! On XP it's called a Remote Desktop Connection.

Edited by - Stinger on 27-02-2003 01:32:56

I'm never physically at the machine, I use terminal server/remote desktop 100% of the time.

The problem is, I'm not the only one who needs access to this computer via terminal server and as long as I am logged into the computer, whether it be through terminal server or whether it's physically at the console.. it's still logged in and consumes the terminal server license.

Terminal server/Remote desktop doesn't care if you're actually connected or not, a login counts against you, so as long as I'm logged in, noone else can login and via TS/RD.

So the bottom line becomes this ... I need a solution that allows me to run Freelancer and not be logged in at all, one way to do this is to have Freelancer run as an XP service because services run in the background and do not require you to be logged in and therefore do not consume a TS/RD license..

If I'm able to get it to run as an XP service, like I've done with games like medal of honor for example .. I could login and go to the services control panel, start the service and then log off entirely.

As I've said, I can get the process "flserver.exe" to load as an XP service, but it seems that the game isn't actually listening for connections when I do this, even if I use the /C switch that I discovered.

It's like the game depends on it's GUI interface to function, that would be the first I've seen like that... maybe it has something to do with directplay/DX9, I really don't know.. but it does work if I launch it via terminal server/remote desktop and remain logged in.. which is what I'm trying to get away from.

Long winded reply, yes hope it worked

Directplay basically has alot to do with when you want to talk of TCP/IP is all! For example when you run a voice setup in XP it use's the dircet play for that and I know like if you run a software firewall it can mess up direct play which will casue your sound card to think it can not run Full Duplex! Which when this happens you can not use porgrams like Roger Wilco ect because direct play controls this dealing with your sound. Then if your in FL and want to talk to a friend useing RW or whatever program then it will not work! So Direct Play should not cause any issues with the server due to it deal with voice cabilites! Sounds like to me it's the way your going about trying to setup the server in the first place! I have not seen any documentation on FL dealing with setting up a server but I would not be running Teriminal Server or it's services unless you did not have a choice! Best thing is it can be strictly a dedicated FL server only if your trying to run other thing's or do other things with the server that their alone going to add more wood to the fire. But again I have not really seen any information not much on configureing FL server! Should not be that hard but all depend's on too on how they configured it too! Good Luck if I found out anything will let you know!

Solved my own problem ..

flserver.exe will not run as SYSTEM, it has to run as a user on the system .. SO

you can use the free version of firedaemon and set it up like this..

Working directory: Full path to freelancer EXE folder
Executeable: Full path and filename to flserver.exe
Parameters: /C /P2302

- Once you install the service, go to the service control panel and stop it ..
- double click on the service to bring up the properties
- select the logon tab
- select "this account" and put in the username and password of a valid account on the system.

start the service!!

Open up a command line and type netstat -p udp -an and you should see the port number you listed in the /P parameter above.

Now it's running.

LOGOFF of your system and it stays running, if you set it to "automatic" start, it will load with windows.

Have fun.

PS. You can download firedaemon from http://www.firedaemon.com/ .. it works on Windows 2000 and XP


Edited by - riven1128 on 27-02-2003 21:45:17

I think this would be a great addition to the FAQ by the way .. I can imagine this as being very useful information to server admins.

Consider it done! Great work!

Yes! exactly what i was looking for! you solved my biggest problem