My windows server has two IP addresses. I have two IIS Web Sites, one running on each IP address. The first one is bound to the main IP -- so I can use the machine name as the website name ( http://MACHINENAME/site/default.aspx ... ). However, to access sites on the second, I have to use the full IP address (http://nnn.nnn.nnn.nnn/site/default.aspx ). Is there a way to add a second "machine name" so that I can address that second site by name (and without adding a DNS entry manually).

[Reply or follow-up to this message]

In Apache I use different ports, or a virtual host - allowing many websites to be hosted with the same IP. I don't know if IIS can be configured in that way but you could do a search on IIS virtual host and see. Either way, you should consider a dynamic DNS server to create a hostname that points to your dynamic OR static IP, there are many free services on the web.

[Reply or follow-up to this message]

Yes. You will need to go into the IIS Manager (the same thing with which you've probably 
already gotten familiar), and right click on your web site (the first one is generally 
named "default web site"), and select properties.





On the tab named "Web Site" you will see the following: 
IP Address:  Usually says "All Unassigned" and then an "advanced" button. Click the 
advanced button, and then press "add..."

Now, instead of putting in an IP Address, type to which you want it to respond.  
MyServer.ExampleSite.Com  for example. You can also just put  MyServer. (I only use 
upper and lower case letters so it is easier to read. Capitalization doesn't matter. 
)

Do this for both, and when you click OK, and go back to the first screen, the one 
with the properties for your Web site, make sure that in "IP Address" it now says 
"MyServer" or "MyServer.ExampleSite.com," or whatever you typed. Do this for both 
of your Web sites, and they should respond. If you would like further information, 
this is referred to as using "host header names" for multiple sites. 

Also, here are two Microsoft tutorials for doing so, just in case my instructions 
were not clear enough. 

http://support.microsoft.com/kb/324287


http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/883a9544-3f70-4d46-a6df-bbadbd1fe7de.mspx?mfr=true


Both links tell basically the same information, but it's always good to have it written 
a few different ways, because sometimes what makes perfect sense to me may be complete 
gibberish to the person on the other end.
 

Reply here if you have any further questions, and I will endeavor to get your problem 
resolved.








On Monday, March 24, 2008 at 12:01 pm, John Bailo wrote:

>

>My windows server has two IP addresses.

>

>I have two IIS Web Sites, one running on each IP address.

>

>The first one is bound to the main IP -- so I can use the machine name as the website 

>name ( http://MACHINENAME/site/default.aspx  ... ).   

>

>However, to access sites on the second, I have to use the full IP address (http://nnn.nnn.nnn.nnn/site/default.aspx 

>).

>

>Is there a way to add a second "machine name" so that I can address that second 
site 

>by name (and without adding a DNS entry manually).

>

>
 

[Reply or follow-up to this message]

This is great information, but I think it leads me to a conclusion that was not what I hoped for! In my situation I have two IPs running two Web Sites. Yes, I can set a "host header" for each one, however, it sounds like the only way to get that to propagate is to then update the company DNS (this is intra-net only). I was hoping that I could add a second machine name and use that for my website thinking the machine name would propage via WINS without having to contact the system administrators.


On Monday, March 31, 2008 at 5:29 am, Wolven wrote:
>Yes. You will need to go into the IIS Manager (the same thing with which you've probably
>already gotten familiar), and right click on your web site (the first one is generally
>named "default web site"), and select properties.
>

[Reply or follow-up to this message]

You are correct in your assumption. No, this won't propagate through WINS. May I 
ask why it is such an issue to update DNS?  If all things are set up correctly, everyone 
should be pointing to your Active Directory server for DNS information anyway. (Otherwise 
you have that insanely long log-in time.) If you want to force the issue, to make 
them "aware" of the changes faster, I can walk you through a few steps to do so.

I'm glad to help in any capacity that I may. I understand the difficulties in dealing 
with the Microsoft way of doing things. :) 









On Monday, March 31, 2008 at 10:41 am, John Bailo wrote:

>

>This is great information, but I think it leads me to a conclusion that was not 
what 

>I hoped for!

>

>In my situation I have two IPs running two Web Sites.

>

>Yes, I can set a "host header" for each one, however, it sounds like the only way 

>to get that to propagate is to then update the company DNS (this is intra-net only).

>

>I was hoping that I could add a second machine name and use that for my website 
thinking 

>the machine name would propage via WINS without having to contact the system administrators.

>

> 

[Reply or follow-up to this message]

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum