Local IP of the server: 192.168.0.1
Port Forwarding: http://i.imgur.com/rJCZ1.jpg
Router: I'm not entirely sure what to put down since I'm still a newbie to this, but it's a Linksys router. I do have a wired connection to it.
I had my own dedicated server up and running a few weeks ago, and I decided to update it through HLDSUpdate tool.
The problem is that now my server won't show up on the Internet tab and people can't connect to the server. It was fine before I had to update it.
It shows up in the LAN tab, but only I can connect to it. In the server cfg, I set sv_lan to 0, so I dunno what's going on.
Your port forwarding look fine. It covers the necessary ports for the server. Have you tried including -ip XXX.XXX.XXX.XXX in your startup command line? You need the external ip of your server, not the internal ip.
Were people able to connect to the server before the update with that same setup you listed? Or only you were able to connect to the server?
Earn Points, get Free Rewards with your Amazon Points! Points2Shop
Local IP of the server: 192.168.0.1
Port Forwarding: http://i.imgur.com/rJCZ1.jpg
Router: I'm not entirely sure what to put down since I'm still a newbie to this, but it's a Linksys router. I do have a wired connection to it.
I had my own dedicated server up and running a few weeks ago, and I decided to update it through HLDSUpdate tool.
The problem is that now my server won't show up on the Internet tab and people can't connect to the server. It was fine before I had to update it.
It shows up in the LAN tab, but only I can connect to it. In the server cfg, I set sv_lan to 0, so I dunno what's going on.
Your port forwarding shows ip 192.168.0.105 but you mentioned your server ip is 192.168.0.1?
I added the -ip <local ip> for my setup and it worked. When I tried -ip <internet ip>, it gave me an error.
(08-15-2012, 03:08 AM)Ghost Assassin Wrote: Have you tried including -ip XXX.XXX.XXX.XXX in your startup command line?
I tried putting that, and I got an engine error. It might be the same one Noodle mentioned above. I remember before I got this server working, I actually had to take out the -ip (local ip) command in my startup.
(08-15-2012, 03:08 AM)Ghost Assassin Wrote: Were people able to connect to the server before the update with that same setup you listed? Or only you were able to connect to the server?
I didn't change anything with my setup at all, all I did was run the HLDS Update Tool since my server was running an older version of the game.
(08-15-2012, 07:57 AM)noodlenoggan Wrote: Your port forwarding shows ip 192.168.0.105 but you mentioned your server ip is 192.168.0.1?
I added the -ip <local ip> for my setup and it worked. When I tried -ip <internet ip>, it gave me an error.
Yeah, I ran an ipconfig on the command prompt and apparently my ip for ethernet was .100. All I had to do was change the IP addresses for the port forwarding and it showed up on the Internet tab.
I'm going to see if it can work again after I update for the Mann Vs Machine update before I put it up as resolved.
I have tried setting inbound rules for all the ports in the image above in windows firewall, I have tried doing -ip (local) and -ip (internet.) Local doesn't fix anything, and internet gives me an error.
look for your server ip then paste that in your server.cfg where is says writeip i believe
the network ip is kinda the same for everyone, its your PUBLIC IP that matters
google "my ip"
(09-19-2012, 02:25 AM)notdemon Wrote: look for your server ip then paste that in your server.cfg where is says writeip i believe
the network ip is kinda the same for everyone, its your PUBLIC IP that matters
google "my ip"
Will the people trying to join be required to use the port numbers?
