SRCDS Steam group


Yet another "my TF2 server won't appear in the server list" thread
#16
Stonos Wrote:
MjrNuT Wrote:Stonos,

since your modem is also your router, is it able to DMZ the PC that your running your server from? If so, I'd suggest you try that. Just remember to disable all the port forwarding.

restart the modem

restart the SRCDS

Check the browser list.

Hmmmm ... I get mixed results with DMZ.
I can see the server in the internet tab, but a friend can't.
EDIT: Someone joined the server, so it's visible in DMZ!

Even if DMZ works, I don't want to use DMZ for various reasons.

And by the way, even with DMZ, I had to forward the ports, because an uTorrent's Port Checker said that port 27015 was closed when I didn't have it forwarded.

Stonos,

Setting the TF2 server to be DMZ was only to test. I'm not recommending you keep it that way. DMZ means to have no firewall, all port opened. This is why someone did join your server....and I'm assuming it was NOT a friend of yours and VIA the game browser?

Those kind of details are important to really understand what may or may not be happening.

So, if you're TF2 server is joinable when doing DMZ with above assumptions, then at least I can only draw 2 conclusions:

1. w/o DMZ, you are not forwarding ports correctly.

2. w/o DMZ, your modem/router may not be sufficient device to handle this setup.


Your last paragraph does not make sense to me, but I may be misreading it. Maybe you don't have the TF2 server PC assigned an IP address via MAC address? So you just turned on DMZ altogether??

Bottomline is that you really need to understand your modem/router and its capabilities coupled with really understanding port forwarding setup.

The likelihood of your PC getting attacked b/c it is DMZ is low, unless you've made yourself worthy of one. Toungue
[Image: MJRNUT-1.jpg]
Reply
#17
MjrNuT Wrote:Setting the TF2 server to be DMZ was only to test. I'm not recommending you keep it that way. DMZ means to have no firewall, all port opened. This is why someone did join your server....and I'm assuming it was NOT a friend of yours and VIA the game browser?
No, it wasn't a friend.

MjrNuT Wrote:So, if you're TF2 server is joinable when doing DMZ with above assumptions, then at least I can only draw 2 conclusions:

1. w/o DMZ, you are not forwarding ports correctly.

2. w/o DMZ, your modem/router may not be sufficient device to handle this setup.
I'm pretty sure that it's neither of these reason since, it used to work fine a year ago. But now my server just won't get listed with DMZ off Sad
Don't forget that people can join if they use "connect <ip>" in the console or add the server to their favorites, so probably doesn't have to do with port forwarding.

I even used CurrPorts to see what ports srcds.exe was using. As expected, it was listening only on port 27015 (which I have forwarded correctly since people can join my server if they have the IP), and it was also using some other ports (to be precise: 26901, 27005 and 27020) which nevertheless I forwarded even though they were not inbound ports.

MjrNuT Wrote:Your last paragraph does not make sense to me, but I may be misreading it. Maybe you don't have the TF2 server PC assigned an IP address via MAC address? So you just turned on DMZ altogether??
No, I don't think that's the reason since srcds was showing my external IP when it initialized.
Maybe my router has an extra protection layer that you still need to forward ports even with DMZ on? Not really sure, but I was also surprised to see that I neede to forward the ports even with DMZ on!

MjrNuT Wrote:Bottomline is that you really need to understand your modem/router and its capabilities coupled with really understanding port forwarding setup.
Like I've said, it was working fine a year ago. I haven't changed my ISP nor my router since then. So it must be something else Sad

MjrNuT Wrote:The likelihood of your PC getting attacked b/c it is DMZ is low, unless you've made yourself worthy of one. Toungue
Well, security is obviously one reason I don't want DMZ on. The other reason is that there are other computers connecting to the internet with this router via a switch. I don't think that this would work well with DMZ on. (tbh, I didn't try it). I would probably have to use ICS, but that would require the other computer to be permanently on.
Reply
#18
Stonos Wrote:
MjrNuT Wrote:Your last paragraph does not make sense to me, but I may be misreading it. Maybe you don't have the TF2 server PC assigned an IP address via MAC address? So you just turned on DMZ altogether??
No, I don't think that's the reason since srcds was showing my external IP when it initialized.
Maybe my router has an extra protection layer that you still need to forward ports even with DMZ on? Not really sure, but I was also surprised to see that I neede to forward the ports even with DMZ on!

You really didn't answer my question there... Big Grin

Some routers can DMZ specific IPs while others cannot and thus DMZ everything.

Stonos Wrote:
MjrNuT Wrote:Bottomline is that you really need to understand your modem/router and its capabilities coupled with really understanding port forwarding setup.
Like I've said, it was working fine a year ago. I haven't changed my ISP nor my router since then. So it must be something else Sad

MjrNuT Wrote:The likelihood of your PC getting attacked b/c it is DMZ is low, unless you've made yourself worthy of one. Toungue
Well, security is obviously one reason I don't want DMZ on. The other reason is that there are other computers connecting to the internet with this router via a switch. I don't think that this would work well with DMZ on. (tbh, I didn't try it). I would probably have to use ICS, but that would require the other computer to be permanently on.

So, a year ago when this worked.....did you also have the switch and all those other PCs connected to it?
[Image: MJRNUT-1.jpg]
Reply
#19
Make sure you forward ports 27000-27040 on both UDP and TCP. Also port checkers won't tell you the port is open unless you have the server running, so make sure its up when you're checking.
Reply
#20
MjrNuT Wrote:
Stonos Wrote:
MjrNuT Wrote:Your last paragraph does not make sense to me, but I may be misreading it. Maybe you don't have the TF2 server PC assigned an IP address via MAC address? So you just turned on DMZ altogether??
No, I don't think that's the reason since srcds was showing my external IP when it initialized.
Maybe my router has an extra protection layer that you still need to forward ports even with DMZ on? Not really sure, but I was also surprised to see that I neede to forward the ports even with DMZ on!

You really didn't answer my question there... Big Grin

Some routers can DMZ specific IPs while others cannot and thus DMZ everything.
I believe that my router is in the first category.

MjrNuT Wrote:
Stonos Wrote:
MjrNuT Wrote:Bottomline is that you really need to understand your modem/router and its capabilities coupled with really understanding port forwarding setup.
Like I've said, it was working fine a year ago. I haven't changed my ISP nor my router since then. So it must be something else Sad

MjrNuT Wrote:The likelihood of your PC getting attacked b/c it is DMZ is low, unless you've made yourself worthy of one. Toungue
Well, security is obviously one reason I don't want DMZ on. The other reason is that there are other computers connecting to the internet with this router via a switch. I don't think that this would work well with DMZ on. (tbh, I didn't try it). I would probably have to use ICS, but that would require the other computer to be permanently on.

So, a year ago when this worked.....did you also have the switch and all those other PCs connected to it?

Yes.

Wylker Wrote:Make sure you forward ports 27000-27040 on both UDP and TCP. Also port checkers won't tell you the port is open unless you have the server running, so make sure its up when you're checking.
Tried forwarding that range. Didn't help Sad
And the server was running when I did the port check.
Reply
#21
Try add -heathbeat 2 in your startup line.
Reply
#22
realchamp Wrote:Try add -heathbeat 2 in your startup line.

I believe you meant -heartbeat right?

I tried both, but I still can't see my server in the internet tab Sad
Reply
#23
Yeah that was what I ment, my fault!

Do you run with Steam on your hosting PC?
Reply
#24
realchamp Wrote:Do you run with Steam on your hosting PC?

Yes.
Reply
#25
Maybe therefore. Sometimes it works and then not.

If you can, shut down Steam and then give it a try once agian.
Reply
#26
Stonos Wrote:I believe that my router is in the first category.

LOL.

Sorry Stonos, it's not something to believe. Goes back to understanding your router and what it is capable of. Usually you can find online the manual for your brand/model.

Post it up here if you'd like ppl to look closely for you. Big Grin

Stonos Wrote:
MjrNuT Wrote:Bottomline is that you really need to understand your modem/router and its capabilities coupled with really understanding port forwarding setup.
Like I've said, it was working fine a year ago. I haven't changed my ISP nor my router since then. So it must be something else Sad

MjrNuT Wrote:The likelihood of your PC getting attacked b/c it is DMZ is low, unless you've made yourself worthy of one. Toungue


So, a year ago when this worked.....did you also have the switch and all those other PCs connected to it?

Stonos Wrote:Yes.


Aside from my comment above about statically assigning the IP address to game server, I wonder if you have your Windows Firewall enabled. Turn it off and see what happens.
[Image: MJRNUT-1.jpg]
Reply
#27
realchamp Wrote:Maybe therefore. Sometimes it works and then not.

If you can, shut down Steam and then give it a try once agian.
Tried it, didn't work Sad

MjrNuT Wrote:
Stonos Wrote:I believe that my router is in the first category.

LOL.

Sorry Stonos, it's not something to believe. Goes back to understanding your router and what it is capable of. Usually you can find online the manual for your brand/model.

Post it up here if you'd like ppl to look closely for you. Big Grin
http://www.blackfoot.com/pdf/ST536_UserGuide.pdf

DMZ is mentioned in page 83.

realchamp Wrote:
Stonos Wrote:
MjrNuT Wrote:Bottomline is that you really need to understand your modem/router and its capabilities coupled with really understanding port forwarding setup.
Like I've said, it was working fine a year ago. I haven't changed my ISP nor my router since then. So it must be something else Sad

MjrNuT Wrote:The likelihood of your PC getting attacked b/c it is DMZ is low, unless you've made yourself worthy of one. Toungue


So, a year ago when this worked.....did you also have the switch and all those other PCs connected to it?

Stonos Wrote:Yes.


Aside from my comment above about statically assigning the IP address to game server, I wonder if you have your Windows Firewall enabled. Turn it off and see what happens.

Turned it off and unfortunately, it didn't make a difference Sad
Reply
#28
Stonos....you crack me up man.

1. I think you need to update your OP. I went back and saw you state using the Steam Dedicated Server tool. Are you NOW using Source Dedicated Server (SRCDS)?

Let's just clarify that up front b/c the Steam forums is where ppl are posting the same issues as you when using the STEAM dedicated server.

2. If you are indeed running SRCDS now, provide your commandline startup in code tags here for us.

Now to your Router setup. (My gut tells me last year you were using Steam DS and since its launched when you are logged in, that those ports are open, but for some reason, recently, it doesn't work. and you're not the only one out there)

1. Everyone has their method of setting up their LAN, so some opinions will be relevant. I like to make all device setting within the router, rather than on the PC. Since you have X number of PCs on the LAN, you will want to ASSIGN a LAN static IP to the PC that will run your TF2 game server (this assumes you will NOT play on the same PC).

2. Log into your Router and go to Home Network > Devices in order to see what devices are connected to your router. Pages 70-72. Assuming you know what PC is going to be teh TF2 server, select that device from the list to see it's details (page 74). It will show you the MAC address and the IP address assigned to it. Check the box: ALWAYS use the same address. Remember that IP address, write it down. Now that PC has its OWN LAN IP, which will be used for port forwarding.

3. Make sure the FIREWALL setting of the router is at least set to Standard (page 60). You cannot have it set to BLOCKALL for obvious reasons.

4. Now to do the port forwarding, see page 50 Section 4.5.3. Can't tell from that list, but possible SOURCE or HalfLife2 or w/e is in that list, which is predefined port protocol. If it's listed, then select it and assign it to the TF2 server DEVICE. If not, then proceed to Section 4.5.4 to CREATE a new GAME Definition.

5. Since you are hosting from home and you want to play on your own server, then your COMMAND line startup for TF2 must have -port 27016 or any number, just NOT 27015. Why? B/c you locally have to connect on that port. Big Grin

6. Router should be all set now. Reboot it and your PC just for extra. DISABLE the windows firewall on the PC running TF2 for now.

7. Assuming you know how to setup your BAT file for launching the TF2 server using SRCDS, go ahead and do it.

Let us know how it goes and provide some screenshots to help show your situation/experience. This should not in any way impact the other PCs. (Note, I did see that the SpeedTouch can DMZ specific PCs)


Remember, update your OP for your situation.

Cheers and good luck
[Image: MJRNUT-1.jpg]
Reply
#29
MjrNuT Wrote:1. I think you need to update your OP. I went back and saw you state using the Steam Dedicated Server tool. Are you NOW using Source Dedicated Server (SRCDS)?

Let's just clarify that up front b/c the Steam forums is where ppl are posting the same issues as you when using the STEAM dedicated server.

2. If you are indeed running SRCDS now, provide your commandline startup in code tags here for us.

Did a small update to the first post Smile
If you need any more information just tell me Smile

MjrNuT Wrote:1. Everyone has their method of setting up their LAN, so some opinions will be relevant. I like to make all device setting within the router, rather than on the PC. Since you have X number of PCs on the LAN, you will want to ASSIGN a LAN static IP to the PC that will run your TF2 game server (this assumes you will NOT play on the same PC).

2. Log into your Router and go to Home Network > Devices in order to see what devices are connected to your router. Pages 70-72. Assuming you know what PC is going to be teh TF2 server, select that device from the list to see it's details (page 74). It will show you the MAC address and the IP address assigned to it. Check the box: ALWAYS use the same address. Remember that IP address, write it down. Now that PC has its OWN LAN IP, which will be used for port forwarding.
Oh, that's what you meant.
I have already assigned a static internal IP on my computer (192.168.1.8 like I said in the first post), so no need to do that. However, I had to enable DHCP to use DMZ.

Quote:3. Make sure the FIREWALL setting of the router is at least set to Standard (page 60). You cannot have it set to BLOCKALL for obvious reasons.
Firewall already at standard level (I've also tried completely disabling it; didn't help Sad)

Quote:4. Now to do the port forwarding, see page 50 Section 4.5.3. Can't tell from that list, but possible SOURCE or HalfLife2 or w/e is in that list, which is predefined port protocol. If it's listed, then select it and assign it to the TF2 server DEVICE. If not, then proceed to Section 4.5.4 to CREATE a new GAME Definition.
I've just created a new application with range 27000-27040 TCP/UDP forwarded. The port is forwarded correctly since canyouseeme can see me Toungue

Quote:5. Since you are hosting from home and you want to play on your own server, then your COMMAND line startup for TF2 must have -port 27016 or any number, just NOT 27015. Why? B/c you locally have to connect on that port. Big Grin
Nah, I don't think this has actually matters since my server also isn't visible in the server list when TF is closed. Anyway, I've switched to 27016.

Quote:Let us know how it goes and provide some screenshots to help show your situation/experience.
Well, the screenshot below is not any useful at all; just shows my problem:

[Image: servernotonlist.png]



Also, I'd like to thank everyone who is trying to help Smile
Reply
#30
On this go around, I didn't say to do DMZ.

I didn't say changing the port to 27016 for the server was going to prevent listing, it would only prevent you from joining.

your startup line in your OP, change to the following:

do a stock map first.

Code:
-game tf -console +ip WANIP -port 27016 +maxplayers 24 +exec server.cfg +map cp_dustbowl


WANIP = your public IP address.

or this

Code:
-game tf -console -hostip -port 27016 +maxplayers 24 +exec server.cfg +map cp_dustbowl

Disable Windows Firewall.

If this does not work, then I'm done dewd and sorry. Sad
[Image: MJRNUT-1.jpg]
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)