Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

OK, so maybe not the "proper use" of network resources, but we enjoy the odd COD game during lunch hours. When we played COD4, we had a dedicated server setup at the back of the server room. With MW2, we need to be able to connect to steam to be able to play multi-player.

I've found this support article here:

https://support.steampowered.com/kb%5Farticle.php?ref=8571-GLVN-8711

Which outlines all the ports I need to open. I went through and created the following rules in ISA 2000 (I'm stuck with 2000 for now).

Protocol Definition: Steam Primary connection: Port 27000, UDP, Send Receive Secondary Connection: Port range 27001-27030 Send Receive

Protocol Definition: Steam TCP In Primary connection: 27014, TCP, Inbound Secondary Connection: Port range: 27015-27050, Inbound

Protocol Definition: Steam 4380 Primary connection: 4380, UDP, Send Receive

When I start steam on my local workstation (I did add an exception to the Vista Firewall to allow steam), the steam client sits on "Updating Steam" for 5 minutes then errors out with: You must connect to the internet first.

Any ideas? I assume I missed something.

Thanks for your help.

share|improve this question

closed as off-topic by Zoredache, Ward, Falcon Momot, TheCleaner, voretaq7 Feb 3 at 21:28

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions must be relevant to professional system administration. Server Fault is dedicated to professional system and network administrators. End user and enthusiast questions are off-topic (contact your system administrator or hire a professional to help you out). Please see the Help Center for more information." – Zoredache, Ward, Falcon Momot, TheCleaner, voretaq7
If this question can be reworded to fit the rules in the help center, please edit the question.

    
+1 for gaming on the office network. At least you know how to have fun :) –  Tom O'Connor Jun 8 '11 at 13:31

3 Answers 3

Why did you define TCP inbound connections? They should be outbound, if the internal client is going to talk to some Internet server using those ports.

Also, after defining those protocols, did you actually create a policy to allow them from the internal network to the external one?

share|improve this answer
    
Sorry, typo. Yes, they are outbound. Yes, I also created a Protocol Rule to allow access from internal to external. –  twlichty Nov 25 '09 at 21:51

Is your proxy server transparent or explicitly defined on the clients?

Are your programs definitely routing through the proxy (can you see blocked traffic in ISA monitor?)

It may be the case that your apps are not hitting the proxy and are trying to jump directly through the network gateway.

share|improve this answer

Secondary protocols are only supported when using the Firewall Client - they don't work with pure IP ("SecureNAT") clients.

With ISA 2000, you'll need one protocol definition per port to support SecureNAT. Later versions treat "All outbound traffic" as including unidentified ports - ISA 2000 didn't, from memory.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.