The below statement came through the icculus Linux mailing list. However, it is NOT linux specific, this applies to ALL server's regardless of Operating System.
If you run a dedicated server, be aware of the posts that are in use
Quote:
Hi All
Ok when the 1.4 patch came out there was a issue with the can not retrieve session, killing server fault. After looking innto this Treyarch changed some port in it. Here is the summery of what I did
CoD5 v1.1, 1.2 and 1.3 will run with default ports with ETQW server with default ports.
Installed CoD5 v1.4 patch and all of a sudden it would not run. It would log innto the lobby as it should with no problems but at the ned of the server log I was seeing could not retreive session killing server. I shut down all the servers on the box and CoD5 v1.4 came right up just fine and fast. So it had to be another server. What I found is that ETQW sdnet port was NOW conflicting with CoD5 v1.4. Guess what port the sdnet port is for, daemon aka "Session Creation".
I then changed the default sdnet port of ETQW up by 10 and wham both ETQW and CoD5 v1.4 came right up
I do not know what Treyarch did but they did infact change the session port being used. Again CoD5 v1.1 to 1.3 will work just fine with default ports with ETQW at default ports. In CoD5 v1.4 the session creation port was changed and will conflict with ETQW sdnet port if not changed. Since we can not change the CoD5 port I had to change the ETQW sdnet port and once I did that both servers now works perfectly.
This is just for info and if you are getting session creation/retrival errors look at the following port number 3074. If you have another server or process that is using 3074 it could/will conflict with CoD5 v1.4 inref to "Session Creation/retrieval.
Wizz
|
This is indeed an excellant find. Thanks Wizz!!!!!!!!
Linear Mode
