Not showing up

[flash64]

I'm running out of ideas here and I'd really like to get my server listed. Could someone please help me solve this?

1. People can connect to my server using its domain or ip without any problems.
2. The server is not listed in gametiger, steam or the ase.
3. I have opened ports 1200 and 27000-27050.
4. I have forwarded 27015 and 27020 to 10.0.0.10 (the box running srcds).
5. I have tried linux as well as windows with the same result.

Network info:
Linux router using iptables.
eth1 for lan (10.0.0.1, 255.0.0.0, 10.0.0.255)
eth0 for wan/ppp0 (10.0.0.2, 255.0.0.0, 10.0.0.255)

Linux srcds server
eth0 for lan (10.0.0.10, 255.0.0.0, 10.0.0.255)

I'll happily post my ip/domain if that would help test stuff.
Maybe someone could portscan(nmap) me to see if these ports are really open?

Thank you
Flash64

BTW: Nice site and very helpfull tutorial!
However the tutorials seem to be a bit outdated (i.e. register steam account).

[m0gely]

You can't see the server online while behind the same NAT as the server. Smarter networking people thatn I understand the why, but it's by design. Ask a friend to check his server list (or use a web based one) and you will find it's probably on there. Also, you don't need to forward all those ports for what you're doing. You only need to foward the port the server runs on, for example 27015 UDP by default.

[Goofy666]

m0gely Wrote:You can't see the server online while behind the same NAT as the server.

You can 'fix' this by using the Windows hosts file though (more information).

m0gely Wrote:You only need to foward the port the server runs on, for example 27015 UDP by default.

If you want rcon and other services to work as well you need to forward a bunch of other ports as well (more information).

[m0gely]

If your server runs on port 27015, then check off TCP as well as UDP if you connect to your home server from outside your home, and want RON access (srcds only, hlds does not require the TCP part). I didn't think he would so this. Also, you don't need a "bunch of other ports" forwarded. Those other ports are required if you block outgoing traffic as well, and 99% of home users out there don't have a router that can even do that.

As for the hosts file trick, I will have to try it out. It's interesting but too easy to forget about for most I think.

[Goofy666]

A lot of people here (with a home router) were helped with that list, by forwarding all of them they didn't had any 'port-related' troubles anymore, so I doubt it very much that it wouldn't make a difference.

The hosts file just redirects a dynamic URL (or WAN IP) to your servers' local IP, so it is just the same as using that local IP for accessing the server. But it can be handy if you are able to access your router through that URL/IP.

Btw, the hosts file works, no doubt about that. It is just *because* a lot of people forget it, that I remind you about it. If you know the trick, and you find it to be handy, you won't easily forget it.

[m0gely]

You can forward all those ports and a ton more if you want. I'm not sure the nature of your reply though. Are you dissagreeing with me? The list is not wrong, it's just uneccessary to forward all those ports inbound. You only need one port, the port that the server runs on.

[Goofy666]

m0gely Wrote:You can forward all those ports and a ton more if you want.

Sure, but the list I posted are relevant srcds ports. Quiet a difference, no? Since the threadstarter wants his server to be accessed from the internet (so it isn't only a local gameserver) it is wise to forward all sufficent ports.

What I am saying is that you could try to forward those ports to and see if it helps, if it doesn't than at least you tried that possibility. I have known a lot of people with similar problems, forwarding the right ports helped for most of them.

m0gely Wrote:Are you dissagreeing with me?

So what if I would? Forums are made for discussions, you shouldn't be so surprised if you think that somebody is disagreeing with you .