PDA

View Full Version : Protocol 45 Error


sevnn
10/09/00, 02:42 pm
I am trying to set up a small LAN server for a few friends of mine to play on. I initially had 2 machines running 1.17 and when the second machine joined the server (non-dedicated) he would join with only 10 health. This posed an obvious problem for whomever was playing on that machine. I tried restarting the server with the same results. I tried moving the server to the other machine and the first server could not join it. I don't remember the exact problem but I belive the server wouldn't show in the list.

I aplied the 1.25 patch to both machines and started the server again on the first machine. When the second and third machines (had #3 installed w/ 1.25) tried to join, they gave "Server is running Protocol 45" errors.

I am runnin Win2000 Pro on all machines with only TCP/IP installed. The first 2 machines are running static IP's reserved from my DHCP server. The third is a dyanmic IP from that server. I am running Win2000 ICS from a Win2000 Adv Server and that is the DHCP machine also. The IP range is 192.168.0.0. Tribes and Half-Life have no problems running in this situation. My friends are begging for Q3A and I have yet to be able to deliver. Please Help!!! Thank You.

Dekard
10/09/00, 03:17 pm
Sounds like he had handicap enabled on his machine.. http://63.167.10.249/admincentral/ubb/smile.gif Have him start up a regular game and see if it's the same way.. http://63.167.10.249/admincentral/ubb/biggrin.gif

And on the issue of the other machines seeing the game servers.. make sure all of the machines on the inside of your network have the same "workgroup" (shouldn't need to be) and you have no firewall software running on any of the machines.. (Just figured that out the other day myself..)

------------------
Dekard
Admin Central (http://www.admincentral.net)
dekard@admincentral.net

[This message has been edited by Dekard (edited 10-10-2000).]

Viruseater
10/10/00, 02:07 pm
Also. to add.

the protocol error is because the server has the patch but the client doesn't. add the 1.25 patch to the client machines as well.

(1.25 is not backwards compatible)