Share via

IIS 8 ERR_CONNECTION_RESET

Robert Groux 171 Reputation points
2021-06-17T02:49:52.287+00:00

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!

Internet Information Services
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sam Wu-MSFT 7,211 Reputation points Microsoft Vendor
    2021-06-18T02:29:07.127+00:00

    Hi @Robert Groux

    According to your description, I guess you may not bind the right IP address for the ip.add.re.ss:8080 domain or use the wrong ip address bind with ip.add.re.ss:8080 domain.

    I suggest you could firstly try to use the server's ip address to access your web application to make sure you firewall setting and IP setting is right.

    If your client server and the IIS server are in the same domain and you have installed an DNS server, then you could access the web site by domain. Details about how to set the DNS server, you could refer to this article.

    If you want to test, you could try to modify the hosts file in the C:\Windows\System32\drivers\etc path in your client server.

    For example: 192.168.x.x ip.add.re.ss:8080

    If the answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.