Strange server problem.

Hi everyone, I'm new to the server scene, but today, I finally managed get a server online.

I know this for a fact, since some random player joined my server.

Since I was happy my server was finally working, I asked my friend to join me on my new server.
Here comes the problem:
I gave him my servers IP address from "whatismyip.org" and it didn't work.
Not by simply joining it or using the console command "connect".

He tried joining me through he friends tab, and through the steam chat window.
Nothing worked.

yeah, having dmz on should disable the hardware firewall, though its a terrible idea to leave it on all the time <_<

if you have all the firewalls off your most likely culprit should be port forwarding (dmz should also do this, but ive found it frequently doesn't work), or you might have one of the annoying routers that requires you to set up virtual servers...
eh...it should all be in the guide, so im not going to retype it

yeah, having dmz on should disable the hardware firewall, though its a terrible idea to leave it on all the time <_<

if you have all the firewalls off your most likely culprit should be port forwarding (dmz should also do this, but ive found it frequently doesn't work), or you might have one of the annoying routers that requires you to set up virtual servers...
eh...it should all be in the guide, so im not going to retype it

Click to expand...

Well, yeah, I'd actually already read your guide before you posted here.
I've got a D-Link DI-624+.
And I already have Virtual Servers set up since my attempt on a CSS server.

And I've forwarded everything on our router, even looking remotely right.
And I don't know what else to try....

basically you have ports forwarded, you have a static ip, your software firewall is off and you can confirm its entirely off (they can lie), you have virtual servers at the right places, you have your computer set to dmz, you have your router set to accept all inbound ips, and you have it set to respond to wan ping requests. Beyond that all you can really do is keep playing with the other firewall/filtering settings and hope it works...

Id suggest adding a few more virtual servers perhaps, you "need" them at 27015 and 27010 minimum.

EDIT: Also, tried adding my server to GameTracker.com, when my software firewall was turned off, I was DMZ and had added more visual servers.

It said this:

Gametracker could not scan the server.
One of the following suggestions may help you:
Your server is currently offline.
GameTracker needs your server to be online before you can add it to our database. Please restart your server and make sure it's up before hitting ADD SERVER again.
You entered the wrong query port.
Please update your query port and hit scan again
Your server is firewalled.
Please turn off any firewall you have that may block scanning.

EDIT2:
Asked my friend to try to join the server, while I was on the server.
It said my friend managed to join.
But his loading-meter froze trying to connect.

The Server itself, said that he had timed out.

Then 2 other random people joined the map while I was doing something else, and
it seems they had no trouble joining.

and what your describing is exactly what happens to me while my software firewall is active...
get that friend to try and ping your computer, see if it goes through

what im not liking is that your network ip is listed as a local ip and not your external ip...

check your router to be 100% sure that ports 27000-27050 are forwarded to 192.168.0.100 (i assume thats your computer), and that its using tcp/udp (or it might say both, or have separate settings for both and you just mirror it)

yeah...im not really seeing anything wrong with the cfg...though ive never declared my ip/port in the cfg, but i can't see that being the problem...

i don't know...im kinda out of ideas, inclined to believe that portforward link that says your router can't properly run a server...

Click to expand...

Actually, I think I managed to get my server online, cuz my friend could find it using "favourites".
I think the problem was that when I arranged my ports on the virtual servers, I used my external IP instead of my internal, I changed that now.

The IP shown in the console screenshot is a local IP. That should be the external one.
We have our servers not having their ip declared on server.cfg or command line. This should make sure they get an external ip automatically.
Our Ports are defined at command line (for instance with: -port 27015)
Lastly, srcds.exe has been added to the firewall exceptions.

You yourself should also try to connect to it on remote ip. If you can do that, then you should be almost there...

The IP shown in the console screenshot is a local IP. That should be the external one.
We have our servers not having their ip declared on server.cfg or command line. This should make sure they get an external ip automatically.
Our Ports are defined at command line (for instance with: -port 27015)
Lastly, srcds.exe has been added to the firewall exceptions.

You yourself should also try to connect to it on remote ip. If you can do that, then you should be almost there...

Click to expand...

Thanks a lot for trying to help...
xD
I don't understand what you mean though.
English isn't my first language, so could you simplify what you just said, a little?

1. The IP shown in the console screenshot is a local IP.
That should be the external one.
2. We have our servers not having their ip declared on server.cfg or command line. This should make sure they get an external ip automatically.
3. Our Ports are defined at command line (for instance with: -port 27015)
4. Lastly, srcds.exe has been added to the firewall exceptions.

5. You yourself should also try to connect to it on remote ip. If you can do that, then you should be almost there...

Click to expand...

1. The IP shown in the console screenshot is a local IP. It should instead be the external ip, in other words it should be the one listed at http://www.whatismyip.com/
2. Your server.cfg is specifying your external ip and ports within it, its a very unusual thing to do. You should remove those lines and it might help.
3. You can declare the ports as a launch parameter for the server, however should you decide to just use port 27015, then its not necessary, as it defaults there.
4. Open your software firewall and add whatever program your running the server from to the exceptions list, and allow all connections, try to do the same with the hardware firewall (router) as well if it allows it. Exactly what program to allow depends whether your running it from srcds, or the source dedicated included with steam.
5. Not 100% sure on this one, perhaps try pinging your ip from another and see if it goes through?

1. The IP shown in the console screenshot is a local IP. It should instead be the external ip, in other words it should be the one listed at http://www.whatismyip.com/
2. Your server.cfg is specifying your external ip and ports within it, its a very unusual thing to do. You should remove those lines and it might help.
3. You can declare the ports as a launch parameter for the server, however should you decide to just use port 27015, then its not necessary, as it defaults there.
4. Open your software firewall and add whatever program your running the server from to the exceptions list, and allow all connections, try to do the same with the hardware firewall (router) as well if it allows it. Exactly what program to allow depends whether your running it from srcds, or the source dedicated included with steam.
5. Not 100% sure on this one, perhaps try pinging your ip from another and see if it goes through?

heres a minimalist server.cfg to try out

Click to expand...

Oh, Thanks~

Doesn't help very much though.
I had already specified the port as a launch parameter...
I have opened almost everything I can with my SW-Firewall.
I'll try looking at my HW-Firewall one more time though.

Removing the lines didn't work, since the problem with the int.IP instead of ext.IP
is shown in the console, before the server.cfg is loaded.

[...]
5. Not 100% sure on this one, perhaps try pinging your ip from another and see if it goes through?
[..]

Click to expand...

1-4. That is quite right MrAlBobo! Thnx!

5. What I meant is that you can see your server on your lan. When you connect to it, you'll probably connect to its local ip (192.x.x.x). Try searching for the server on its external ip and port (with "find games at"). Then connect to it by that external address.
I'm curious if you experience the same problems this way.

I discovered that even though I specified my port as 27015, the real server port was 60049.
:S

Anyway, I managed to add my server to gametracker.com, and it recognizes it as Alive/Online,
So if I'm allowed, then here is the server IP.
78.70.107.39:60049
If you feel you have time, try joining it. :3