Created Website on IIS - This site can't be reached on client (windows 10) whereas Website is working fine on server (server 2016)

Question

I have created a static webpage on IIS using windows server 2016 with the reference to this link- https://www.atlantic.net/hipaa-compliant-hosting/how-to-build-static-website-iis/#:~:text=Open%20Server%20Manager%2C%20and%20select,Information%20Services%20(IIS)%20Manager.&text=In%20the%20Connections%20pane%2C%20right,and%20then%20click%20Add%20Website.&text=In%20the%20Add%20Website%20dialog,in%20the%20Site%20name%20box.)

& i can able to open the webpage on my physical server without any issues - http:\Mytestpage.com. (IIS Website port - 93)

When i tried the same URL on my windows 10 machines (DHCP), getting an error "This site can't be reached".

Note: Added Port 93 in firewall

IIS Website configuration:

Site Name : MyTestPage.com
Physical path: C:\mysite
Connect As : Application user (passs-through authentication)
Port:93
IP address: 192.168.1.7
Authentication: Anonymous Authentication : enabled (others are disabled)

Testing result:

On server : opened the URL http:\MytestPage.com - Working
On client (DHCP) : opened the URL http:\MytestPage.com - This site can't be reached error.

Please suggest.

Answer 1

Hi @MJ

There are many reasons for this error, generally, this error message gets triggered due to the failure of the DNS lookup. Here, DNS is the network address that is responsible for translating the website name into its respective internet address. Some of the common reasons that you face this error message while visiting the website are:

• Internet connection failure.
• Misconfiguration of internet connection.
• Misconfiguration of network settings.
• The firewall might be preventing Google Chrome from loading the website.

You can try the following methods to solve the problem:

• Clear browsing history, cookies, and cache.
• Resetting settings of Browser.
  -Changing IPv4 DNS Address.
• Restarting DNS Client.

---

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.

Answer 2

Hi,

I might be reading this wrong but from the client browser don't you need to define the none standard port in the URL so http:\MytestPage.com:93 . otherwise you will only hit the web site listening on port 80.

The access via the IP address would drop through to either the default IIS virtual web site or one setup for the IP address port 80 in the binding, the 404 could be because the document root won't contain your page as its the default one C:\inetpub\wwwroot if it the default one, maybe not where you "real" page is.

Regards
Gary

Answer 3

Go to Site-> Go to bindings

Double click on http->remove everything->change it to All unassigned->restart site->now try to open->then revert to old settings/names->restart site->

It should work. thanks