Last post Feb 17, 2017 02:34 PM by groston
Feb 04, 2017 05:17 AM|groston|LINK
Problem summary: I installed a third-party http-based application on a Windows 7 Pro ‘server’. Due to the presence of another application that uses port 80, I changed the default port for IIS to 8080. I can access the application from the server, but not
from another machine on the same network. This is not a firewall issue – the problem persists when the firewall is disabled.
Details: The server’s IP address is 10.1.100.1. Bindings for the default web site have been set to:
The third party app is a .NET application (framework version 3.5) that resides in C:\Program Files\myApp\web. I believe that file permissions have been appropriately set.
Using IE on the server, if I enter either
the application launches and functions normally.
When I try http://10.1.100.1:8080/myApp from another computer on the network, I get the following message:
Unable to connect. Firefox can’t establish a connection to the server at 10.1.100.1:8080.
Using WireShark, I did see communication between the machines – it is not a firewall problem.
Based on various posts, I have tried:
What do you suggest that I try next. Thx!
Feb 04, 2017 06:17 AM|HostingASPNet|LINK
You could check your server and IIS error logs for more clues.
Feb 06, 2017 05:38 AM|Chris Zhao|LINK
For this issue, you could refer https://support.mozilla.org/en-US/kb/firefox-cant-load-websites-other-browsers-can.
Feb 08, 2017 02:13 PM|groston|LINK
Based on the suggestions, I dug in further:
Using WireShark, I did see communication between the server and an other machine. The other machine sends a ACK request and the server replies with a RST, ACK response. Based on my reading, this means that the port is closed. Note that this is not a firewall
issue - I see the same behavior whether the firewall is active (a rule has been created) or not.
When I run nmap on the other computer, it responds with:
8080/tcp closed http-proxy.
This confirms the above. However, when I run netstat –ab on the server, I see
TCP 0.0.0.0:8080 <servername>:0 LISTENING Can not obtain ownership info
When I run netstat –an, I see
TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING
Thus, the output of the netstat command seems to suggest that the port is open.
Feb 17, 2017 08:25 AM|Chris Zhao|LINK
Try flushing the DNS cache (IPCONFIG /FLUSHDNS) or adding the name to the hosts file on you machines.
Feb 17, 2017 02:34 PM|groston|LINK
Thanks for replying. The issue is not an inability to access the server, the issue is accessing the app on port 8080. Accessing the server via the port 80 app works fine, thus the issue is not DNS-related.