Port Forwarding problem

[spaps]

So for a while now, I've been trying to host a TF2 server, but every time I try to test it with someone else, they always get a "Server not responding" message. This is annoying because I have my ports forwarded, unblocked by Windows Firewall and my security system, and I always set my server to sv_lan 0, but I can never get the damned thing working. I can't even seem to host LAN servers, as every time I play TF2 or CS:GO with a friend at my house, my friend can't connect. But when the friend hosts, I can connect fine. Can anyone help me figure out what in the hell is going on? If you need more information, message me on Steam.

 

[DC 740]

Double check the ports you opened are TCP and not UDP, right? That usually helps me.

What's your anti virus software? I've found that to be the culprit in a number of things to stealthily blocking ports to not allowing registry changes (as in, couldn't install someone's damn printer until we disabled the anti virus)

One thing I'd had to do back in the day was when I dedicated a computer to being a server is I changed the settings in my modem (which acted as a router also) to just be a passthrough and sign in directly to the ISP through Windows/Linux itself. Then I'd turn on Internet Connection Sharing with my other card to get Internet to my other stuff. That was probably my most efficient way of making a dedicated server while having easy access to the computer. Probably a big risk though, don't put anything sensitive on there this way.

 

[spaps]

Hmm. I opened both TCP and UDP. Every guide I read says I have to forward both. As for my security, I'm using ESET.

EDIT: So wait, should I open TCP or UDP? Your wording is a little confusing.

 

[DC 740]

(I'm going to try posting again, I done fucked up the last one)

Sorry I'll try to clarify. Usually if you are hosting a port from your IP for the interwebz to use, you'll want to make sure TCP is what is forwarded for that. I've found UDP works for my local network and it's own devices but doesn't hit outside to the public. A lot of guides will tell you to open TCP and UDP just to ensure the user is set up correctly anyway. I could be completely wrong though as it's been a while since I've done this. I don't think it should be an issue to have both ports open though.

I've never run ESET, Googling brought me this though: How do I open or close (allow or deny) a specific port on my ESET Smart Security Personal firewall? (4.x). I'm assuming you've done that though based on what you've said, one thing I'd do is turn off ESET completely and see if it's an issue with Windows Firewall and vice versa.

Are you making sure people are trying to connect through your public IP and port? For example, 192.168.1.1:1234 . Usually 192 is for local networks, you'll need to make sure you have your actual public address which you can usually find in your modem's status or settings, or you can just check here (whatsmyip.org). I haven't tried hosting a TF2 server myself, are there tools to use for this process?

I think I'm asking too many questions now lol sorry

 

[spaps]

Okay, disabling the Firewall didn't work.

So I just noticed this. On my Port Forwarding tab in my router setup page and saw this:

I had set the IP that's supposed to get its ports forwarded to my local IP it seems. Should these all be my external IP instead? (sorry if my wording is bad)

EDIT: Nevermind, it won't let me save the settings if I have the external IP instead of the local one. So I'm out of ideas.

 

[spaps]

I'm beginning to think that it's some kind of gypsy curse. Like I said earlier, I can't even host locally, but a friend can host on their computer with the exact same internet. And that same thing happened with my old computer from a year ago. That's not normal, man.

Like, I can't figure out for the life of me what the problem is. I followed every guide for port forwarding and hosting servers exactly. A gypsy curse is really the only explanation.

 

[DC 740]

I know you added me on Steam but I'm at work atm and trying to think this over a bit. One problem I can think of is if you have multiple NAT's or a NAT issue in your local network but I'm not exactly sure how you have this set up. Does your router/modem give you any option to enable and use DMZ? You might want to assign your computer a static IP if you haven't and give that a shot. Just be careful with though, this would basically disable ANY firewall/protection on the modem's end and would be up entirely to your software firewall on your computer.

 

[Some JERK]

Okay, disabling the Firewall didn't work.

So I just noticed this. On my Port Forwarding tab in my router setup page and saw this:

I had set the IP that's supposed to get its ports forwarded to my local IP it seems. Should these all be my external IP instead? (sorry if my wording is bad)

EDIT: Nevermind, it won't let me save the settings if I have the external IP instead of the local one. So I'm out of ideas.

No that's right. The router already knows what its own public IP is (BTW you don't need to black out the IPs in this image, they're all class C private IPs that everyone has, unless you're being super-secure and don't want anyone to know what your addressing scheme is on the local side.)

On some routers that use a range of ports for forwarding, I've found that they don't like ranges that aren't ranges (ie: 9777-9777) it's stupid but it's been my experience that sometimes changing that range to something like 9777-9778 will actually make it work. also, try updating your router firmware, as these problems happen.

When someone is on your home LAN they can't connect directly even after they're on your local network? Then your router isn't the problem anyway. Something is going on on your machine. You say windows firewall is open on those ports. what happens when you disable WF completely? Is anything else trying to use those ports on your machine?

Also, in general networking/security follows the most restrictive permission/rule first. Make sure that there isn't some other rule in place that's blocking this port or type of traffic, because that will overrule the firewall exception.