New IIS website is only accessible via the local host
-
This project has been driving me crazy. The windows server 2016 VM on our VMware cluster is brand new with a brand new IIS installation as well.
The ports on the window firewall are set to allow all incoming connections on 443 and port 80. I've set static IP for the VM, which is showing correctly in the DNS manager from the domain controllers. I've changed the website bindings just to use the local IP for simplicity (it never worked before any changes). When I browse the website on the localhost, it will pull up with no problem.
Running Test-netconnection from my workstation fails testing the ports but succeded the ping. I can remote into the machine and everything else is working for the networking of the VM.
If the firewall is set to allow and other VM's can host internal websites without issue what can I check or fix? It seems like the webserver is perfectly fine besides sharing the website.
-
Did you setup the port binding to the IP address?
-
Are you referring to the site bindings? The site bindings in IIS are
443 to *
80 to 192.168.10.240 (the IP of the webserver) -
Yes..I'm just checking the simple things that could prevent the site from working. If you think it's the firewall, I would turn off the firewall just to check...and if it works, then you know it's a firewall issue. If it still doesn't work, it probably is a networking issue.
-
Thank you for the quick response. I've already tried disabling the firewall without success. I'm not sure if it's a firewall or networking issue. What else should I look at?
-
Try one at a time.
Verify that the IIS server can ping the client?
Now, we need to ask if there is an error code showing up or not?
Is the DNS server of both the IIS and client machine the same?
Flush the client's DNS cache.
Restart the IIS, then connect. -
1 Pinging workstation successful, no error codes.
2. Both are using the same DNS server.
after ipconfig /flushdns on the client still no success. -
I do not know at this point. If you've check the firewall setting to allow port 80 incoming, you have reachability in both directions, you can connect to the IIS server from localhost. I think at this point you would have to compare the IIS setup on a working server vs the one you just setup and see if anything different stands out.
-
I figured out the issue. The GPOs were not configured correctly from the MDT deployment.
-
Glad you figured it out! hooray for you.