Problem with Port Forwarding and running a dedicated server

Jessew1089

Distinguished
Jan 25, 2015
62
0
18,640
Hey guys, im brand new to the server thing. Im trying to run a dedicated server for Rust. So far ive gotten it to work for only me. i can log into the game and use a command to log into my server. But when i try and get my friends to join, theyre telling me they get a message saying server not responding. so heres my problem, ive literally been at this for the last 16 hours. been all over the internet and heres what ive gathered. i need to have my ports forwarded. Which i did. still didnt work. so i went into my modem/router and set it to bridge mode so im only running off the second router. still doesnt work. everytime i use any of the port checkers online they all say the ports are closed. Also, i tried everything with my windows firewall. i set inbound and outbound rules to no avail and then turned it completely off just to test the ports and it said theyre still closed... so im completely lost. I have the Modem/Router set to bridge mode, the router has the ports forwarded and windows firewall isnt the problem either... any help would be GREATLY appreciated. this is infuriating lol
 

BuddhaSkoota

Admirable


Have you confirmed the modem/router is in bridge mode by ensuring the second router is being assigned the public IP address?

Did you assign a static IP address outside of the DHCP range of your router?

I wouldn't put a lot of stock in the online port checkers, which may be better at testing common services rather than game server ports. I'd recommend using another service (e.g. FTP) to test port forwarding through the router.
 

BuddhaSkoota

Admirable


Check the status page on the second router. The WAN IP address must be a public IP address.

Bumping the static IP by 20 is probably not enough. Check the DHCP range and set the static IP outside of this range (e.g. if range is 192.168.1.100-199, set it for 192.168.1.10-90.

Assuming the ports are properly forwarded and you're giving your friends the correct IP address, the server should respond., unless you have an unconventional link to your ISP (WISP, apartment router, MIFI, etc.) or ports are being blocked elsewhere.
 

Jessew1089

Distinguished
Jan 25, 2015
62
0
18,640


im looking at my netgear routers page now and i dont see an option to make it public. these are the options i have for the Wan setting page


Disable SPI Firewall

Default DMZ Server ...

Respond to Ping on Internet Port

MTU Size(in bytes)

NAT Filtering Secured Open
Disable SIP ALG
 

BuddhaSkoota

Admirable


You'll just want to make sure the WAN IP address is not 192.168.x.x or 10.x.x.x, which would indicate a private IP address when it should be a public one (any other IP address).

There could be other issues which would cause port forwarding to fail, but without knowing more details, all I can do is offer some suggestions based on the description of problem.
 

Jessew1089

Distinguished
Jan 25, 2015
62
0
18,640



Ok, just checked it and its not a 192.168 or 10. What else do i need to look for? Is the static ip i made correct? its a 192.168
 
You should start worrying about port forwarding once your second router' WAN port gets public IP address.
- disconnect second router from everything;
- reset your primary modem / router to defaults. Connect your PC directly to that modem, and change it to bridge mode. Restart the modem, and when it restarts, confirm from your PC that it has received public IP address (that is, one which does not start with 10.xxx.xxx.xxx, 172.16.xxx.xxx or 192.168.xxx.xxx);
- reset your second router to defaults; connect it to the modem, and configure it without touching port forwarding;
- confirm you have internet working thru the second touter
- now is the time to start messing with port forwarding