UT/UT2K3 client unable to connect to multiple server

[MoorDeeb]

I have set up a Linux server running UT and UT2K3 on ports 7777 and 8888 respectively, however, I am unable to connect with UT2K3 on port 8888. I have modified my ut2003.ini on the client to use 8888 but I keep getting the error that the server is not at the correct patch level. Anyone had success?

[NoOne]

I'm a bit confused as to why you would have to modify your INI on the client. On the server, yes - Because you must define the port to run on (Default is UDP - 7777). Since you say you have UT running at 7777 and UT2K3 running at 8888, you should be able to access the UT2K3 server by a connect to server (IP or DNS) followed by the port number (e.g. 8888).
The format would be 192.168.0.1:8888
Or in URL form UNREAL://www.gamehost.com:8888

I hope that helps.....if not, please clarify what the problem is.

NoOne

[MoorDeeb]

Thanks for the reply. I am unable to connect to either the UT server or the UT2K3 with either client aso I modified my local ini file (ut2003.ini) in an attempt to make it work. For either server, if I change the default UDP port to something other than 7777, neither client an open a connection to the server(s). An error message is produced by the client and although I don't have the exact error message, it refers to version mismatch between my client and server.

[NoOne]

Hmmm.
I don't know where your problem stems from, but you shouldn't have to do anything on the client (almost always the case). The way the connection works is that the server "listens" on the default 7777 port. When a connection is made, it moves it to the next port number up (7779, as 7778 is reserved for query traffic(you know, the server info)). This happens for each new client, so you can see why you need to space the servers apart. If you put a server on a port other than 7777, you have to tell the client where the server is (thus, the ip:port number). That should cover the issue of the port the server is running on. As for the client, the only issue you would have is if the server is a higher version than the client and requires a higher minimum version for compatibility (you should be at 436 for UT). Also, there are known issues in a ServerPackage called DE. If you see an entry in your UT server's .INI listed as serverpackages=de you should REM(a term for REMark, to ignore as text) it out by using a semi-colon infront of that line( ;).

Let me know how that goes.... I'll let someone else take on the UT2K3 problems, as I haven't run that one as a server. But the same basic rules apply to it as it is similar in design.

NoOne

[MoorDeeb]

I figured it out and should have tried this before DUH.... When you launch the game from your workstation and open a connection, just put in the IP address of the server with a colon and port number that the server is running For example, 192.123.123.4:8000. And that's how you tell the client to use the new port. This works for UT2K3 and I suppose it will work for UT also.