Has anyone been able to get Wolfenstein: Enemy Territory working through ISA. (Client or Server)
I sent a request to ID Software support, who were very quick to respond, although not entirely helpful.
Apart from stating "NOTE: Activision does not support the use of routers or firewalls." and suggesting I try the forums at www.planetwolfenstein.com, they provided me with the following:
Return to Castle Wolfenstein relies on Internet communication via the IP protocol and UDP ports 27950, 27960, 27965 and 27952. These are the ports that the game uses for connection, message of the day, server browsing, and so forth.
After setting up rules (I thought) appropriate for these, the game now hangs when attempting to retreive the server lists. (After removing the rules, the game now just doesn't find any servers again.)
I will connect a PC to the internet directly with a Sniffer on, as soon as I get the chance.
But in the mean time, any help would be appreciated.
Not so Far, All I can find is other people complaining about NAT problems.
I have found several people who have decided that there is no way to make this work through a NAT connection (Not just ISA). It doesn't actually seem to be a firewall problem, seems the software can't handle network address translation properly.
I hooked a Machine directly to the internet with a packet sniffer running and found that it also uses UDP port 27951.
Most of the conversation used port 27960 though.
I'm setting up an ISA server at the moment to try running the game directly on.
Theory being I can start a dedicated server on the ISA Server, NAT will not be a problem.
My internal PCs can connect using the Local network option, Outsiders can connect via the internet.
You probably couldn't slip this configuration on at work without any one noticing though.
Most likely you'll need to define protocol definitions in the policy elements that specify the particular ports and whether it's using tcp or udp transmission to get ISA to pass traffic thru. Check on this page here to see how to create definitions. Once you create these, you should then be able to add the rule to allow your client to connect or to publish your server.
ET is working for me just fine. Previously, in the Gaming forum, I posted a solution to Army Operations. It opened the necessary ports for using the GameSpy network. I'm assuming these same settings will work with ET, since they do allow me to set up most games (new & old). I also have the firewall client on the workstation I'm running the games on. Hope this helps.
I tried what worked for the two of you but still nada. I can't see the server list whether I'm at the gateway comp or client stations. Any more ideas, also I'm new to net.administration, so if you think there's something simple I'm missing, go ahead and call me on it.
PS -NickM- if your slowing down w/2 or more clients playing have you tried adding +set net_port 27660 to the command line of the first client then 27661 to the second and so on? I heard ET needs separate ports for each client playing behind a gateway. Thanks.