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.

    SamAndrew81
    • 264
    • 1
    • 5
    • 20
    • Thank you, PJ. I am indeed trying to use port 80 as the binding, yes. If I try to browse to http://localhost I get the 404 Error, just as I get with http://192.168.1.70 and/or http://192.168.1.70:80 – SamAndrew81 Oct 22 '15 at 04: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). – SamAndrew81 Oct 22 '15 at 04: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.... – SamAndrew81 Oct 22 '15 at 05: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? – Pimp Juice IT Oct 22 '15 at 05:14
    • Actually no, it only works with It does not work when I try to browse to or – SamAndrew81 Oct 22 '15 at 05:16
    • I must have broken IIS 8 when I deleted all the default sites and added my own. I'm reinstalling IIS on the server now to start from scratch... – SamAndrew81 Oct 22 '15 at 16:44
    • **FIXED IT!! Reinstalling IIS 8 was the solution.** Thanks again for your help, PJ! – SamAndrew81 Oct 22 '15 at 17:24

    1 Answers1

    0

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

    SamAndrew81
    • 264
    • 1
    • 5
    • 20