It's the first time I've posted on one of these customer support forums, but I couldn't get the serial number correct in the live chat registration screen, so here I am.
Both this morning and for the duration of yesterday evening I've been trying to forward port 2302-2305 to the local IP address of 192.168.1.6. That IP is assigned to one of my HP Proliant servers running Windows Server 2008. Yesterday I started a DayZ (video game) server on it and it started running correctly through the LAN. When I forwarded the ports, they just never opened.
I selected the correct device to point it to, set everything to what it normally should be- everything seems fine- but it just won't forward.
Now here's the weirder thing.
Before yesterdays endeavor, I had port 80, 22, and 7777 open just fine. Port 80 and 22 were (and are) going to 192.168.1.2, and 7777 to 192.168.1.3. (Both other HP Proliants)
I then thought the issue could be the Windows Firewall (thought it was turned off) so I tried forwarding port 21 to 192.168.1.2 which is running Ubuntu Minimal with no firewall at all what so ever. That didn't work either.
Then, I un-forwarded port 80 and 22 to see what would happen. It closed the ports just fine, so then I re-forwarded them and they opened again. That's what normally happens of course. Then I closed 7777, tried to reopen it, but it never opened.
I know this is all somewhat confusing, but see the screenshots below as they may help. As of now, 80 and 22 are the only ports that can open, and 2302-5 and 7777 are closed.
I've tried resetting the router and forwarding just 2302 and that didn't work. I tried disabling UPNP and that didn't work either. I even tried unplugging everything and messing up the entire home network and that didn't work.
Heh... nevermind, solved. The reason the port check tool saw that it was closed was because the server wasn't even running correctly. It was just connecting to nothing :rolleyes:
