SRCDS Steam group


NAT Firewall Issues
#1
We're having some trouble running srcds behind a Sonicwall 3060 running 1:1 NAT.

Confident that we have correct ports open, and we can connect to the server on the LAN ip via VPN.

Problem is connecting via the WAN ip, no response from server even though the assigned port shows as open using port testing tools.

I have seen conflicting info as to weather running SRCDS in a NAT environment is even possible.

IS there a way to make this work and have the server show up on the stream list?

Thanks
Reply
#2
It sounds like something is blocking the connections. Did you check any other software or hardware firewall that might be blocking the ports?
~ Mooga ...w00t? - SRCDS.com on Twitter
[Image: 76561197965445574.png]
Please do not PM me for server related help
fqdn Wrote:if you've seen the any of the matrix movies, a game server is not all that different. it runs a version of the game that handles the entire world for each client connected. that's the 2 sentence explanation.
Reply
#3
It is possible to run behind a firewall. Here are the ports that need to be open. Make sure they are being forwarded to the correct machine.

UDP 1200 (Friends Network)
UDP 27000 to 27015 (Gameport)
UDP 27020
TCP 27030 to 27039
TCP 27015 (SRCDS Rcon port)
A day without fusion is like a day without sunshine.
Reply
#4
Port 27015 is being reported as open by port check tool.

We have the following open in FW config :

UDP 27000 27015
TCP 27030 27039
UDP 1200 1200
UDP 26901 26901
TCP 27015 27015
UDP 27020 27020
TCP 27000 27010


SRCDS is listening on TCP 27015 and UDP 26901, 27005, 25015, 27020

SRCDS is also connecting 26901 72.165.61.185 27017

This Win2k3 server is lisenting on miltiple ips and SRCDS is binding to the correct LAN ip. The WAN IP can be pinged when ping is enabled in the same rule group as above.


Any Ideas??

Thanks


Mooga Wrote:It sounds like something is blocking the connections. Did you check any other software or hardware firewall that might be blocking the ports?
Reply
#5
for reference: https://support.steampowered.com/kb_article.php?ref=6253-IOAB-2296

Did you remember to add srcds.exe to the FW exceptions list?

You could also try disabling the FW altogether AND assuming your port forwards are correct.

Slight OT: Almost everything on STeam support for SRCDS, shows that all you need is 1 port to forward (TCP/UDP). Not the series of ports everyone keeps listing.

Can someone explain that. My W2K3 only has allows incoming/outgoing of srcds.exe and the port (ie., 27015 server 1, 27016, server 2, 27025 server 3, etc.)
[Image: MJRNUT-1.jpg]
Reply
#6
Looks like, according to this article, NAT is a dealbreaker:

Quote:Router NAT
If you are behind a router that is doing NAT translation, your Server will have a different internal IP address than what is needed to list in the Master List (players can't connect using your internal IP address).

BUMMER.

MjrNuT Wrote:for reference: https://support.steampowered.com/kb_article.php?ref=6253-IOAB-2296



Did you remember to add srcds.exe to the FW exceptions list?

You could also try disabling the FW altogether AND assuming your port forwards are correct.

Slight OT: Almost everything on STeam support for SRCDS, shows that all you need is 1 port to forward (TCP/UDP). Not the series of ports everyone keeps listing.

Can someone explain that. My W2K3 only has allows incoming/outgoing of srcds.exe and the port (ie., 27015 server 1, 27016, server 2, 27025 server 3, etc.)
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)