This information has been posted in bits and pieces for ages! So I wrote and posted this on my FL Admins board. Most of our FL admins have perused this so it should be complete enough for establishing a good FL server. The OS this guide is written for is WinXPPro but other XP versions and Win2K should also work quite well.


1. Get FL, install it and run it once. There are two types of installs, full and FL server only. If you have a server (another word for a 'puter that will run something for someone else on another 'puter) which will run nothing but a FL server, just do the FL server install. Remember running just the FL server program (flserver.exe or flserver for short) will not require the FL CD be in the CDROM drive. That's for playing the game (otherwise known as an FL client). Also running flserver at least once will create the needed directories and files (especially flserver.cfg, see #4. below, thanks Pinger ).

2. Read the Readme.rtf in the Freelancer directory, especially the part about FL servers. We will reference back to that.

3. (Optional) Install FLMM and load your mod your server will host. This can be done now or later but better now so you don't forget. Of course no FL software should be running while in FLMM!

4. Install FL admin program(s). At the very least install IFSO mk. V as you simply cannot admin a FL server effectively without it. Configure IFSO as follows:
- Ensure flserver.exe path is correct.
- Ensure flserver.cfg path is correct.
- Ensure the title of the flserver window is an EXACT copy of that in the flserver Window Name box.
- Set one of the two date formats, then change the format under Control Panel /Regional and Language Options /Regional Options tab/Customize button/Date tab. Select a Short date format that matches what you set in IFSO configuration.
- Ensure flserver.exe Checks is enabled and checking every 30 seconds. No need for quicker checking and it takes CPU cycles.
- Time to choose your INCOMING port. flserver needs only one INCOMING port but the Readme.rtf suggests a small range, ports 2303-2304.
-- If you wish to keep the INCOMING 2302-2304 port range, leave flserver Command Line Options box clear.
-- If you choose to set to one INCOMING port, choose your port and enter it in the flserver Command Line Options box preceded by a /P, i.e. /P2302. I suggest this option with a port in the 2300 range. These are relatively known DirectPlay (part of DirectX) ports and less likely to interfere with other software.
- All other IFSO options can be set later.

5. Setup your software firewall. Most software firewalls have a learning capability. Enable it and they will keep a tunnel open through the firewall for flserver's INCOMING port.
- In most cases especially WInXP's firewall, the first time you run flserver it should prompt you asking if you want to open an INCOMING port for flserver. Say yes, it should always remember.
- Zonealarm is a little different. Since it's a OUTGOING as well as INCOMING firewall, both directions must be learned. No biggie though as a prompt should pop up as mentioned before.

6. Setup your gateway. Now many manufacturer's call these things routers but they do much more than just route! Things like logging on, DHCP server, NAT server (hardware firewall) and more so I call it a gateway. The gateway connects between your own network (called Local Area Network or LAN) and the Internet (sometimes called the Wide Area Network or WAN). The gateway must have a few things set up to allow the FL server to the Internet and this is usually done by browsing the gateway LAN IP address.
- Set the server with a fixed LAN IP address. Get the MAC address from the server through the status screen or ipconfig /all in a DOS window. Then set this MAC address to a LAN IP address of your choice in the gateway (sometimes the screen is called Host IP). Say you have 192.168.0.1 as your gateway (gateways end with 1), then you could set any LAN IP address of 192.168.0.2-254. We'll say 192.168.0.200.
- Set the server's LAN IP address automatically. In Control Panel /Network Connections /right-click on Local Area Connection /select Properties /General tab/select Internet Protocol (TCP/IP) /Properties button/General tab. Ensure the Obtain an IP address automatically is selected.
- In the Status window of the Local Area Connection /Support tab, hit the Repair button. This will change the server's LAN IP address to what was set earlier, 192.168.0.200 in our example. Verify through the Status window.
- Go back to browsing the gateway and set the INCOMING port tunnel. Sometimes called Virtual Server or Port Forwarding, enter in the INCOMING port ranges or one INCOMING port (however you did it in #4.) and link to your server's LAN IP address, i.e.192.168.0.200. Basically this ensures anything INCOMING to your gateway on this port(s) will always be routed to JUST your server, like a tunnel from the Internet to the server.

7. Verify the server is running correctly. Start flserver and any FL admin programs on the server. Open the console window instead of the status window in flserver. Look for the following:<pre><font size=1 face=Courier>...
Server running, ready for log in.
Connecting to list server...
Established connection to list server...
Sending game information to list server... </font></pre>If you see this then your flserver has contacted and got itself listed on the FL global list server! This insures DirectX works, network connections work and all OUTGOING requests are routed fine.

8. Verify FL clients can log into your server. As soon as a FL player on a FL client NOT on your LAN can log in and undock on your server, then you have success! This insures INCOMING requests are routed fine and (in some cases!) your mod (if applicable) is installed ok. Now you have an FL server up and running.


Voila! Now if a mod would sticky this it can answer the number one question on this forum in mostly one post.

_____________
Earendil
SysAdmin of Boston Freelancer server
Server community website & forum: EarendilsPlace.net (server rules)