Server arguments

The server accepts the following command-line arguments:

/helpdisplay this help 
/port numberuse specified port number for TCP/UDP sockets Useful for working around firewalls. Note that the server's port number must match the port number specified in the client's network settings, or connection attempts will fail. If not specified, the port number defaults to 35321.
/noudpdon't launch UDP server to answer find broadcasts Useful for working around firewalls. If combined with the /client argument, the server does not create any listening sockets, which is often what triggers the firewall. If this option is enabled, the client's finder will not find the server; the user must specify the server's hostname or IP address in the client.
/hidemake server invisible by hiding its console window This prevents users from accidentally killing the server by closing its window. To exit the server, use the client's Servers dialog, or kill the server's process in the Task Manager.
/client addressconnect to client at specified IP address or hostname Useful if you want to connect over the Internet, but the server isn't visible to the outside world; so long as the client is visible, the server can connect to the client. Note that the client's Listen for servers option must be enabled. Also useful for working around firewalls; see /noudp argument above.
/bind addressbind server to specified IP address Allows you to specify the server's IP address, instead of letting sockets assign an address. Useful on a multi-homed host, i.e. a host with more than one network interface and IP address. On a laptop with both a wireless and a wired connection, use this option to control which connection the server uses.
/threads countcreate specified number of rendering threads The thread count defaults to the number of CPUs reported by Windows. This is typically optimal, but reducing the thread count could potentially improve performance on a Hyper-Threading processor.
/fpuuse FPU instead of SSE2 for rendering math SSE2 is normally optimal; for more information, see the client's Use SSE2 option.