locked
Can't Access Web Site from Internet RRS feed

  • Question

  • Using the steps in Windows Home Server Unleashed by Paul McFedries, I was able to set up internet remote access to my WHS using a static IP address and can see the default remote access home page from outside my home network using a name.homeserver.com address.

     

    Now I would like to host a second web site open to the public. Again following the steps in Unleashed, I set up a second static IP and used IIS to set up a new web folder pointing to the new IP address. I also assigned it to port 81 and made sure it was open in the WHS firewall and my router (Linksys WRT54GL). I also set up a dynamic DNS service with a www.newname.com address. When I attempt to access the new web site, I get the error message, “Bad Request (Invalid Hostname)”. If I use https://www.newname.com, it opens my default remote access page.

     

    Are there additional settings I need to check to get this to work?

    Thursday, January 31, 2008 5:36 PM

Answers

  • Umm, sorry. I didn't notice that you weren't already doing that. That's the way the internet works: if you want to put a web server on a different port, you normally have to specify the port in the URL. You could try configuring host headers in IIS so that you could have http://yourserver.homeserver.com go to the standard web site, and http://www.newname.com go to your new web site. Then both sites could "be on port 80". (This is really the preferred solution for IIS, BTW.)
    Thursday, January 31, 2008 8:57 PM
    Moderator

All replies

  • It's not clear from what you've written that you've forwarded port 81 from your router to your server, which is also required. But more likely DNS hasn't propagated yet. Try opening up a command prompt and pinging the new name.
    Thursday, January 31, 2008 6:12 PM
    Moderator
  • I have configured the router to forward the ports to the server IP address and when I ping www.newname.com I get a reply from the IP address assigned to my router. The weird thing is when I run Port Detective, it says my ports 80 and 81 are not open. I'm also using a DSL modem from verizon. Do I need to configure somthing there?
    Thursday, January 31, 2008 6:43 PM
  • That sounds like you're being blocked by Verizon, who definitely block at least some ports. I generally use Shields Up! for this sort of testing.
    Thursday, January 31, 2008 7:12 PM
    Moderator
  • I tried using Shields UP and it does show that ports 80 and 81 are open.  After messing around some more, I find if I enter http://www.newname.com:81 I can connect to the new web site from the internet.  If I just use http://www.newname.com it still goes to my default access page.
    Thursday, January 31, 2008 8:21 PM
  • Umm, sorry. I didn't notice that you weren't already doing that. That's the way the internet works: if you want to put a web server on a different port, you normally have to specify the port in the URL. You could try configuring host headers in IIS so that you could have http://yourserver.homeserver.com go to the standard web site, and http://www.newname.com go to your new web site. Then both sites could "be on port 80". (This is really the preferred solution for IIS, BTW.)
    Thursday, January 31, 2008 8:57 PM
    Moderator
  • Thank!!. I reset using host headers and the same IP and everything works!! Guess my next purchase will be IIS For Dummies!!


    Thursday, January 31, 2008 10:05 PM