Source Dedicated Server Problem - "Server is not responding"

[Heatsinked]

Hi all. After an exhaustive search of the internet using Google and following numerous step-by-step guides I still haven’t found a solution. So I’m hoping some bright sparks here can help me

Basically I’m trying to setup a CS:Source dedicated server so my friends and I can have a bash over the weekends. I also hope to get Left4Dead, HL2DM and ZP:Source working at some point but, for now, I’ll concentrate on CS:Source.

The problem is that no one, including myself, can connect to my dedicated server via the internet. When I type in the external IP address & port of the server, steam reports that the “Server is not responding”. LAN works fine; I can see the server name and IP address (local). I have triple checked the game config file and it is definitely correct.

Port forwarding, as far as I can tell, has been correctly setup according to the instructions I have read. I have also used a port checking program to confirm this. The port I have forwarded is 27015 for both TCP & UDP traffic to the IP address of the dedicated server. Furthermore, the logs show that traffic is being successfully forwarded to the dedicated server via the port forwarding rule I have setup.

The router I am using is a Netgear RangeMax DG834PN Wireless Router. I have updated the firmware and even tried rolling-back to an older version of the firmware, just in case. The ONLY way I have been able to get this to work is by making the dedicated server a part of the DMZ. It is a simple tick-box in the web interface and allows me to enter an IP address, nothing more. I have been told that this is NOT a solution and is potentially very dangerous.

I firmly believe that my router is the problem, especially after getting it to work using DMZ… I’m just sure if I’ll ever be able to get it working without DMZ. I have tried everything. Perhaps I need a different router?

Can anyone please help?

 

[craptakular]

I assume you are using a home server?

When I last did this a few years back I think you have to use the lan ip if your on the same network.

If you were round your mates house you would type the external ip address, which should work, as long as port forwarding has been correctly setup.

Hope it helps.

 

[kylew]

Any problems I have had over not being able to run Source Dedicated servers have been down to port forwarding.

You've got to forward more than just 27015, you've got to do a few of them.

I'll have a look around my router's config and I'll post he settings I've got mine set up to use.

I'm using a netgear DG384GT, I've configured a PN for a friend though and found the settings to be the same.

Oh, also, I would recommend that you use a DGTeam custom firmware if you aren't already.

 

[Bry]

First of all what type of server are you running?
Is it a dedicated console server or is it the gui version? I am assuming GUI version here.

For the record in a NAT environment you will never be able to connect via your external IP. You will have to connect via your local IP e.g. 192.168.0.2:27015.
External IPS only work for external people in a NAT system (simply put)

Now you say it works fine in a DMZ which instantly runs out things like a windows firewall or antivirus being the cause.
So the issue is definitely with your port forwarding.

The ports you should have open and forwarded are:
UDP 1200 (Friends Network)
UDP 27000 to 27015 (Gameport)
UDP 27020
TCP 27030 to 27039
TCP 27015 (SRCDS Rcon port)

Note: as some of the ports above are in ranges (27000-27015 for example), you should enter them individually (27000, 27001, etc) on the port forward table. There have been several issues with port ranges on some routers

 

[Heatsinked]

I assume you are using a home server?

When I last did this a few years back I think you have to use the lan ip if your on the same network.

If you were round your mates house you would type the external ip address, which should work, as long as port forwarding has been correctly setup.

Hope it helps.

Well, the server is located at home but I'm trying to run the dedicated server for my friends who live elsewhere, so it needs to be accessible via the internet / source in-game browser.

I have tried the external IP address and port, doesn't work...

Any problems I have had over not being able to run Source Dedicated servers have been down to port forwarding.

You've got to forward more than just 27015, you've got to do a few of them.

I'll have a look around my router's config and I'll post he settings I've got mine set up to use.

I'm using a netgear DG384GT, I've configured a PN for a friend though and found the settings to be the same.

Oh, also, I would recommend that you use a DGTeam custom firmware if you aren't already.

Oh right, I didn't realise there were more ports... I thought I just needed 27015. Posting your settings would be great, thanks! Not setup a firewall of any kind yet but intend to, once I've got the dedicated server working properly. Sounds like it's my port forwarding then...

First of all what type of server are you running?
Is it a dedicated console server or is it the gui version? I am assuming GUI version here.

For the record in a NAT environment you will never be able to connect via your external IP. You will have to connect via your local IP e.g. 192.168.0.2:27015.
External IPS only work for external people in a NAT system (simply put)

Now you say it works fine in a DMZ which instantly runs out things like a windows firewall or antivirus being the cause.
So the issue is definitely with your port forwarding.

The ports you should have open and forwarded are:
UDP 1200 (Friends Network)
UDP 27000 to 27015 (Gameport)
UDP 27020
TCP 27030 to 27039
TCP 27015 (SRCDS Rcon port)

Note: as some of the ports above are in ranges (27000-27015 for example), you should enter them individually (27000, 27001, etc) on the port forward table. There have been several issues with port ranges on some routers

Sorry, should have been more specific! I am running the dedicated server console via FireDaemon service manager, definitely NOT the GUI. The only time I use a GUI is when I'm trying to connect to the server from within Steam, to test things.

Thanks for the info regarding ports and the problem with port ranges, I had no idea.... also, that info on NAT and how I won't be able to connect to the dedicated server using my own external address, again, I didn't realise! So I need to ask my friend to test it for me... I'll do that tonight.

Thank you everyone for your quick replies, I'll keep you all posted

 

[Bry]

Ah k good man console is far superior
The startup line i use is:

-console -port 27025 -game cstrike +ip 80.82.141.53 -tickrate 100 +map de_aztec -nocrashdialog +maxplayers 17 +exec server.cfg

obviously replace IP with your external IP

 

[Heatsinked]

Haha, well, I thought if I was going to do it I might as well do it pro-like

Now that is interesting, as several guides I have read conflict with each other regarding that startup line. Some say leave the +IP line out, some say leave it in!!! Some say it should be your internal IP, some say external!!!

Arrrgh! I'll double check mine with yours tonight and give it another go

Thanks for all your help so far.

 

[Bry]

I will admit the IP line can be flakey on NAT so its best to try all combinations

most hosts just dont use NAT as it is a pain for servers.

 

[kylew]

These are the steps I take to set up a router for hosting source based games.

Firstly, you have to add a service to the router.

In security, go to services and add these two services to your router.

and this one too:

This is what my services page looks like:

Then you'll need to go to firewall rules and create the following outbound services:

and

After you have done the outbound services, create these inbound services:

and this one

The LAN server IP will be whatever computer on your network you're using to host the games.

Here is what my Firewall Rules page looks like:

These are the settings I use to enable me to host source games over the internet.

I've used these same settings to configure other routers for the same use.

 

[Heatsinked]

Lot's of useful info...!

Thanks for that, got lots to check now when I get back from work!

Hopefully I'll get this sorted. It may be as simple as not being able to see or connect to the server myself using the external IP, as apparently that is normal... need to get my friends to try connecting after I double and triple check the router / port forwarding settings.

Been reading up on NAT and how some routers handle it better than others... if all else fails, it could simply be that my router is just not up to the job... However, considering the fact that it works fine when DMZ is enabled, does that mean NAT is working ok?

Hang on a minute... if I'm not supposed to be able to connect to the server using the external IP, from within the LAN the server is hosted in, then why does it suddenly work when I enable DMZ for the IP address of the dedicated server? Am I making sense here?!

 

[kylew]

Thanks for that, got lots to check now when I get back from work!

Hopefully I'll get this sorted. It may be as simple as not being able to see or connect to the server myself using the external IP, as apparently that is normal... need to get my friends to try connecting after I double and triple check the router / port forwarding settings.

Been reading up on NAT and how some routers handle it better than others... if all else fails, it could simply be that my router is just not up to the job... However, considering the fact that it works fine when DMZ is enabled, does that mean NAT is working ok?

Hang on a minute... if I'm not supposed to be able to connect to the server using the external IP, from within the LAN the server is hosted in, then why does it suddenly work when I enable DMZ for the IP address of the dedicated server? Am I making sense here?!

I've not used DMZ myself, but I know know that a DG384PN doesn't need it to run hosted games.

If you want some more help, add me to steam or MSN and I'll give you a hand with setting it up and testing your hosting if you would like.

My steam name is kylewaller

My MSN address is [email protected]

 

[Heatsinked]

Cheers fella, I really appreciate it

 

[tolien]

If DMZ fixes it, it's probably a sign that you haven't forwarded the right ports - it'll pass everything that doesn't have a port forward rule to the IP you set as the DMZ.

 

[Heatsinked]

Thank you everyone for yout input! I'm very happy to report that the problem has now been solved. Some custom firmware and rule-tweaking seems to have done the trick. Thanks Kyle! I owe you a beer

Can't seem to close the thread so I'll just leave it to fade away...