Earlier, I posted a step by step guide on Creating IIS7 sites, applications, and virtual directories using Internet Information Services Manager. In the article, I created a new website named “bloggingdeveloper” and created a single HTTP binding configured to listen on all interfaces, port 81, and without a host-header restriction. The site was accessible via http://localhost:81/. 

Serving over Port 81
Serving via http://localhost:81/


In this step by step tutorial, I will describe accessing a local site via name (e.g. http://bloggingdeveloper/) using the Hosts file.

  1. Start IIS Manager

      To start IIS Manager from the Run dialog box
    1. On the Start menu, click Run.
    2. In the Open box, type inetmgr and then click OK.

      To start IIS Manager from the Administrative Services console
    1. In the Control Panel window, click Administrative Tools.
    2. In the Administrative Tools window, click Internet Information Services (IIS) Manager.

  2. Internet Information Manager 7.0
    Internet Information Manager 7.0


  3. Select your site (bloggingdeveloper) from the left side and select Bindings from the right side under the Edit Site section.

  4. IIS Bindings
    IIS Bindings


  5. In the bindings window Click Add, enter 127.0.0.2 as the IP Address, leave the host header empty and click OK.

  6. IIS Add Bindings
    IIS Add Bindings


  7. Edit the Hosts File

    1. Browse to Start -> All Programs -> Accessories
    2. For Windows Vista Users : Right click "Notepad" and select "Run as administrator"
    3. Click "Continue" on the UAC prompt
    4. Click File -> Open
    5. Browse to "C:\Windows\System32\Drivers\etc"
    6. Change the file filter drop down box from "Text Documents (*.txt)" to "All Files (*.*)"
    7. Select "hosts" and click "Open"

    8. Unedited Hosts File
      Unedited Hosts File


    9. To the end of the file add the following line:

    10. 127.0.0.2 bloggingdeveloper

      Edited Hosts File
      Edited Hosts File


    11. Close Notepad. Save when prompted.

  8. If you skip Step b in Windows Vista and try to modify your hosts file, it will not let you save it. It tells you that you don't have permission. To successfully modify the hosts file, run notepad.exe as an administrator.

    Error when trying to save hosts file without administrative privilages
    Error when trying to save hosts file without administrative privilages


    You may use any IP Address between 127.0.0.2 and 127.0.0.254.

  9. Browse your site via http://bloggingdeveloper/

  10. Serving via http://bloggingdeveloper
    Serving via http://bloggingdeveloper


Want automatic updates? Subscribe to our RSS feed or
Get Email Updates sent directly to your inbox!

Currently rated 5.0 by 2 people

  • Currently 5/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5


Comments

March 2. 2009 18:17

Duuuuuude...... I can't thank you enough for this.

Namaste.

Qwickset | Reply

October 21. 2009 00:00

There's nothing to stop you using 127.0.0.1, either, as long as you set the Host Name in the IIS Bindings to the desired name.  I generally use a fully qualified (but fake) domain name, eg. 'bloggingdeveloper.local'.  I've been using this exact method for years - it works great.

Darren | Reply

October 21. 2009 16:52

I've been using this manner also many times. Only the host file is computer specific.

I want to run the website on lets say: site1.local.
How do I configure this for the entire network from the server?

Not changing the host file on every computer?

Cheers,
Frank

Frank | Reply

October 22. 2009 18:15

Social comments and analytics for this post

This post was mentioned on Twitter by bloggingdev: Accessing Local IIS Web Sites via Name using the Hosts File - http://su.pr/AmJAq9

uberVU - social comments | Reply

Add comment




(Will not be displayed!)








SponsoredTweets referral badge
Free CMS