0

Getting a "HTTP 404 Not Found" when I enter the server's LAN IP in a browser (http://192.168.1.70 - which the site has bindings for) or simply try to browse to localhost in IE 11. However, in IIS 8 I can successfully browse to "http://Server.MyDomain.com on 192.168.1.70" and everything works as intended. The static DNS A record already exists and was created for the hostname before I installed IIS 8 role.

    So far, I have tried:

  • Adding 192.168.1.70 and Server.MyDomain as trusted sites in IE
  • Deleting/re-adding the site in IIS
  • Restarting IIS Admin Servicing and rebooting the server.
  • What could be the issue here? Thank you.

    7
    • Thank you, PJ. I am indeed trying to use port 80 as the binding, yes. If I try to browse to localhost I get the 404 Error, just as I get with 192.168.1.70 and/or 192.168.1.70:80 Oct 22, 2015 at 4:44
    • If I ping MyServer.MyDomain.com I was getting only an IPv6 reply, so I disabled IPv6 on the NIC and now I just get ::1: (just loopback, I believe. There is no loss). Oct 22, 2015 at 4:55
    • Everything is being done internally, just on the single web server right now. I think you're right in that it's a DNS issue, but I can't find anything wrong in DNS. I will re-enable IPv6 and see if the address that pings back to the hostname machines.... Oct 22, 2015 at 5:10
    • Just so I understand here, it ONLY works on the server when you go to localhost from network PC it does NOT work with http://192.168.1.70 or http://Server.MyDomain.com correct? Oct 22, 2015 at 5:14
    • Actually no, it only works with <!--Server.MyDomain.com--!> It does not work when I try to browse to <!--localhost--!> or <!--192.168.1.70--!> Oct 22, 2015 at 5:16

    1 Answer 1

    0

    In my particular case here, reinstalling the IIS 8 role was the solution.

    You must log in to answer this question.

    Not the answer you're looking for? Browse other questions tagged .