Page 2 of 2
Posted: Fri Jan 23, 2004 7:45 am
by hoxu
I suggest you either run the server in screen (1) or use the -detach parameter.
Posted: Fri Jan 23, 2004 3:12 pm
by Guest
When I go to find my server in my client, its not there though....
Posted: Fri Jan 23, 2004 3:15 pm
by LinuxServer
ok, we have got it all figured out, except for one thing; we are trying to make the server secure, and we are using a firewall to do so. The only thing is, the firewall is making it so that noone else can join. Do we use TCP/UDP, just UDP, or just TCP? we have tryed several combinations, but none seem to want to work. I beleive that this will be the last problem too. I hope so at least.
Posted: Sun Jan 25, 2004 12:23 am
by Avion
The default port is TCP 13327 for client connection and optionaly - if you want to register with the (a?) metaserver that uses port 13326.
If your server is not on the metaserver and not local - you need to know the host name of your cf server and have to be able to resolve it from your client...
Posted: Tue Jan 27, 2004 2:24 am
by Leaf
Avion wrote: If your server is not on the metaserver and not local - you need to know the host name of your cf server and have to be able to resolve it from your client...
Or, you can specify the server in when launching the client via the command line, like so:
gcfclient -server <server_name or IP> -<options>
Example: gcfclient -server metalforge.real-time.com -cache
Posted: Wed Jan 28, 2004 5:04 pm
by Avion
leaf wrote:
Or, you can specify the server in when launching the client via the command line, like so:
gcfclient -server <server_name or IP> -<options>
Example: gcfclient -server metalforge.real-time.com -cache
True, but what I meant is that you need to either know the IP of the server or be able to resolve the name (a host name record or DNS entry...).
Posted: Wed Feb 04, 2004 10:24 pm
by LinuxServer
Done, and it works now.. thank you all very much.