Hello.  I just watched the entire Installing DNN on Windows 7 tutorial.  It was, as usual, excellent.  I installed two sites, once using the first db method and then using the method in the fifth video.  Working great, thanks.

If I am on the Windows 7 machine locally (which is a Windows Virtual PC), I can access the sites using http://localhost/sitename.  However, I would like my boss to view my work on her computer.

I gave that Virtual PC a static ip address, added a dns entry for the sites at that ip address.  From another workstation I can ping the address or the host names, it resolves, great.  In DNN I configured the Portal Alias setting to include the intended name.

Uh, but how exactly do I connect that to the sites?  I think this is a IIS question now.  Seemed easier in earlier versions of IIS.  Seemed like I would connect the sites to the ip address and configure host headers.  But I dont see where to do that.

Am I barking up the wrong tree? 
Doxey

I think that you've done all of the right things.

What is the name associated with the site in IIS?

DNS routes requests for the URL to IIS. IIS routes the requests to DotNetNuke. DotNetNuke uses the portalalias table to route the requests to the portal.

If this is not working for you, what is wrong?

Thanks for the consideration. Yes well, what are the names of the sites? Well that may be the crux. They are not really configured as sites. They are applications, per the tutorial. There are three. For instance, one is called, cleverly, DNNTest. See attached snippet. But if I configure the application, dnntest, there is no place for binding configuration, thus nowhere to input ip address and host header. I can configure binding information on the site, Default Web Site, which I did. But then DNS simply resolves to the default IIS 7 welcome page, which my browser displays. How do I instruct IIS to give ip addresses and host headers to the various applications underneath? Sorry if this is elementary.

This was, in fact, elementary. I simply created a new site, gave it the right ip address and host header, pointed to the correct folder, and off I went. I was all tripped up on using the Default Site but once I gave that up it came along quickly. Meant to close this one last week.

Thanks for the update.  I'm glad that you got that fixed.