Dedicated server won't go public, keeps being on lan :: Team Fortress 2 General Discussions

Store Page

Team Fortress 2

All Discussions Screenshots Artwork Broadcasts Videos Workshop News Guides Reviews

Team Fortress 2 > General Discussions > Topic Details

Profesorius Kalėdauskas has Team Fortress 2

Mar 1, 2014 @ 2:05pm

Dedicated server won't go public, keeps being on lan

So i decided to make a server.
Everything was going smoothly until i launched and invited a friend to join - he could'nt.

I did the whole Port Forwading thing (hopefully correctly)

in the server.cfg there is a line "sv_lan 0"

And srcds is checked allowed for public networks as well as private

This is the ip i used in the "local host" space while port forwading 192.168.1.169 since it showed up as Ipv4 in cmd

the server appears on the lan tab in game with the ip of 192.168.1.169:27016

Any thoughts on what should i do?

< >

Showing 1-10 of 10 comments

PerplexedArcticWolf has Team Fortress 2

Mar 1, 2014 @ 2:07pm

Play on an empty server or buy a server. Or just don't play with your friends.

JarateKing (very rusty) has Team Fortress 2

Mar 1, 2014 @ 2:09pm

That hopefully correctly thing is wrong, if sv_lan is 0 but you can only connect through lan then it's got to be an issue getting it to the rest of the internet.

192.168.1.xxx is the internal IP address. You need your external IP address, which you can use this for.[www.myipaddress.com]

Profesorius Kalėdauskas has Team Fortress 2

Mar 1, 2014 @ 2:45pm

ok so i changed "local host" in port forwading to my ip which is 78.56.38.55

when i run the server it still runs on the ip: 192.168.1.169:27016

this is how the port forwading looks: http://i.imgur.com/sOXAq5H.png

:'(

Inde

Mar 1, 2014 @ 3:18pm

Try to port forward

Hydrogen

Mar 1, 2014 @ 3:30pm

Are you running the server in the same machine that has the steam client installed?

If so, put your steam client into Beta mode.

JarateKing (very rusty) has Team Fortress 2

Mar 1, 2014 @ 3:59pm

Originally posted by TheFieryBreeze:
ok so i changed "local host" in port forwading to my ip which is 78.56.38.55

when i run the server it still runs on the ip: 192.168.1.169:27016

this is how the port forwading looks: http://i.imgur.com/sOXAq5H.png

:'(

Sorry for not explaining well, I misread a bit (or was just completely wrong and was an idiot, I've forgotten already). Those port forwarding settings you had before were fine (probably, I don't use that brand).

Possible issue A) your server.cfg isn't actually a server.cfg and is instead a server.cfg.txt file, confuses things a lot. Of course it could also just be misspelt like srever.cfg or something, just test by throwing in a bunch of

echo "" echo "" echo "if you find this then server.cfg got executed" echo "" echo ""

Possible issue B) You need to change the map for sv_lan to change. Not sure if this is true or not.
Possible issue C) Think you pointed out that you added hlds as an exception in your firewall. If not do that.

I would try hydrogen's advice though, I'm not very well informed on this.

Last edited by JarateKing (very rusty); Mar 1, 2014 @ 4:00pm

Hydrogen

Mar 1, 2014 @ 4:44pm

As for why I said to put the steam client into beta:

If you're running a dedicated server on the same operating system that has the steam client installed, a recent TF2 (and possible steamcmd) update broke the steam support library connection between a dedicated server and the valve servers, thus forcing the server to always boot in LAN mode (and if you go in to your own server, you will have no item server connection).

Forcing the steam client into beta mode fixed the issue somehow (my guess is a steam library collision or something of that sort broke something).

As a serious last-ditch attempt, put your machine in DMZ mode. This is a resort I took when I became extremely annoyed at port forwarding, and I have had no problems ever since. It is a security hazard, since all the ports are open from the internet to your server, but it fixes the issue of your server not being accessible to the internet. Again, only do this as a last resort and/or if you don't care about the security of your server/computer.

Profesorius Kalėdauskas has Team Fortress 2

Mar 2, 2014 @ 3:45am

Thank you for the responses

JarateKing, i'm pretty sure that the issues you listed aren't present here

And hydrogen, I would try, but i wanna point out that i don't lose connection to the item servers when i start playing through lan.

So yeah... This is pretty mysterious to me, here are some screenshots, that might give some idea of what everything looks like:
http://imgur.com/a/GUIxM

and this is the guide i used: http://portforward.com/english/routers/port_forwarding/Pirelli/DRG-A125G/Team_Fortress_2.htm