We're having issues accessing our server remotely. Currently the server is setup using a 192.168.x.x IP and our firewall is redirecting all traffic from our public IP to the server. Port 80, 443, and 8080, 53 are open.
I'm trying to get to: ip.add.re.ss:8080 off the network which is a basic index.html page at the moment. Locally on the server I can load the web page just fine with ip.add.re.ss:8080. Any time I visit the external IP off the server I'm getting ERR_CONNECTION_RESET in chrome and edge. I know I'm reaching the server because IIS logs are being generated for each request.
Things I've already tried...
Checked firewall
Installed apache on the windows server and got a basic web page to load on port 8080 using the public IP address
Checked failed request logs. Logs say Failure Reason STATUS_CODE Trigger Status 200 Final Status 200 ( I can provide logs if needed )
Normal IIS logs show my IP hitting the server with status 200
Confirmed bindings in IIS are correct. Currently set for all unassigned IPs with no hostname defined and port 8080 (HTTP) I also tried adding * in the hostname field.
Tried adding the IP via netsh: netsh http add iplisten:ip.add.re.ss
Checked HTTP sys logs. I see a bunch of: 8080 - - - - - Timer_MinBytesPerSecond - and thats it.
I've tried just about everything I've found online and that I can think of. Hoping someone here can help!