>>>>>Hi,
>>>>>
>>>>>I am trying to understand what is a better choice for an Intranet ASP.NET application? (note that not Internet but Intranet): Web Site or Virtual Directory.
>>>>>
>>>>>When I go to the Web server, I can add a Web Site to the Web Sites Item in the IIS. Or I can expand Web Sites and then right-mouse click on Default Web Sites and Add Virtual Directory to the Default Web Site. I really don't understand the difference and therefore don't know which one has an advantage for ASP.NET intranet application.
>>>>>
>>>>>I would appreciate any input or suggestions.
>>>>
>>>>Is IIS currently using the default web site for content other than your app? If so it might be preferable to create a new web site on a different IP address - that way you can start and stop it, control access etc without affecting the default site.
>>>
>>>After reading whatever I could find on the web about new web site vs. virtual directory, I agree with you that I need to create a new web site. The only thing I don't understand is what IP address to enter when creating new web site? How do you determine what IP to choose/enter?
>>
>>Add a suitable additional static TCP/IP address using the 'Advanced' button on the Windows TCP/IP Properties form.
>>In IIS create the new website, open it's Properties page, click the 'Advanced' button in Web Site/ Web Site Identification and edit the IP address to use the required address.
>>HTH,
>>Viv
>
>Thank you for your help. I found an article on the web on how to create internal DNS server for "friendly" names with a LAN. I am a little confused as to which way to go but I will study your suggesting and the approach of DNS server.

I think you're mixing up two issues. DNS will map a 'friendly' URL to an IP address - but you should still use a static IP address for the web site if at all possible.

Regards,
Viv