question

RobertGroux avatar image
0 Votes"
RobertGroux asked SamWu-MSFT commented

IIS 8 ERR_CONNECTION_RESET

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!










windows-server-iis
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

SamWu-MSFT avatar image
0 Votes"
SamWu-MSFT answered SamWu-MSFT commented

Hi @RobertGroux

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.

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thanks for the response Sam. The public IP is not actually added to the server. We have a firewall before the server that acts like a DMZ (I should have mentioned that). So when someone hits the public IP they first go through the firewall and that traffic gets sent to the private IP 192.168.x.x which is on the server. I've tried all bindings in IIS. "All unassigned Ips" and also binding the local IP. I'm not using any domains here just trying to connect directly to the IP. When I try and connect to ip.add.re.ss:8080 remotely it does not work I get the error in the title. When I connect to ip.add.re.ss:8080 on the server itself it loads fine. I'd also like to point out as my post said that this worked fine when I loaded Apache on the windows server and had it display a page on ip.add.re.ss:8080 with no issue.

0 Votes 0 ·

Have you tried disabling the firewall and then try again?

0 Votes 0 ·