Duplicate Name in IIS 5.0
-
Any time I try to create a new website, or a new ftp site, the wizard pops up and all goes smoothly until I try to start it. When I attempt to start the new site, I receive the error message "A duplicate name exists on the server." It does not. And there are no clues other than this message. I've searched Technet for this exact message, but there is nothing in the Knowledge Base that matches this phrase, and any looser search returns only totally irrelevant articles. Is there an unmentioned limitation to one website and one ftp site in Win2K Server SP2? There are no duplicate names anywhere on the machine; not sites, folders, or files. Clues would be most welcome... "When in danger, fear, or doubt, run in circles, scream and shout!" - Lorelei and Lapis Lazuli Long
-
Any time I try to create a new website, or a new ftp site, the wizard pops up and all goes smoothly until I try to start it. When I attempt to start the new site, I receive the error message "A duplicate name exists on the server." It does not. And there are no clues other than this message. I've searched Technet for this exact message, but there is nothing in the Knowledge Base that matches this phrase, and any looser search returns only totally irrelevant articles. Is there an unmentioned limitation to one website and one ftp site in Win2K Server SP2? There are no duplicate names anywhere on the machine; not sites, folders, or files. Clues would be most welcome... "When in danger, fear, or doubt, run in circles, scream and shout!" - Lorelei and Lapis Lazuli Long
Roger Wright wrote: Is there an unmentioned limitation to one website and one ftp site in Win2K Server SP2? If there was, I don't think you would be the first person to find it. :-) I aint ever used 2k server apart from telnetin and pure Ftp. But is it a duplicate name or a duplicate name space. Talking about spaces, I hate the idea of using them in names. I remember this use to screw an old DOS version bad. Regardz Colin J Davies
Sonork ID 100.9197:Colin
You are the intrepid one, always willing to leap into the fray! A serious character flaw, I might add, but entertaining. Said by Roger Wright about me.
-
Any time I try to create a new website, or a new ftp site, the wizard pops up and all goes smoothly until I try to start it. When I attempt to start the new site, I receive the error message "A duplicate name exists on the server." It does not. And there are no clues other than this message. I've searched Technet for this exact message, but there is nothing in the Knowledge Base that matches this phrase, and any looser search returns only totally irrelevant articles. Is there an unmentioned limitation to one website and one ftp site in Win2K Server SP2? There are no duplicate names anywhere on the machine; not sites, folders, or files. Clues would be most welcome... "When in danger, fear, or doubt, run in circles, scream and shout!" - Lorelei and Lapis Lazuli Long
Yes,when I try to create a new ftp site other than default ftp site in IIS,everything is ok, But when I want to start it,errors pop up. Are there any veteran web administrators who can give us some advices? :confused: this is my signature for forums quoted from shog*9: I can't help but feel, somewhere deep within that withered, bitter, scheming person, there is a small child, frightened, looking a way out.
-
Any time I try to create a new website, or a new ftp site, the wizard pops up and all goes smoothly until I try to start it. When I attempt to start the new site, I receive the error message "A duplicate name exists on the server." It does not. And there are no clues other than this message. I've searched Technet for this exact message, but there is nothing in the Knowledge Base that matches this phrase, and any looser search returns only totally irrelevant articles. Is there an unmentioned limitation to one website and one ftp site in Win2K Server SP2? There are no duplicate names anywhere on the machine; not sites, folders, or files. Clues would be most welcome... "When in danger, fear, or doubt, run in circles, scream and shout!" - Lorelei and Lapis Lazuli Long
Each web-site in IIS must have a unique "address", which is a combination of:
- The IP address it listens to;
- The port it listens to - normally 80 for HTTP and 443 for HTTPS;
- (For HTTP sites only) The Host Header name;
Assuming you are just setting up standard HTTP sites, you can host multiple sites on the same machine by changing one of these three parts. Since you will probably be using a single IP address, and you don't want to change the port, this leaves the Host Header name. Set this to the domain part of your site's URL - for example,
www.site1.com. Assuming the DNS forwww.site1.comis pointing to your server, you will then be able to openhttp://www.site1.comin your browser and see the pages for Site 1. If one site serves multiple URLs, you can add other entries by clicking the "Advanced" button in the properties of the site. NB: If someone requests a URL which is pointing to your server, but the domain is not set up as a Host Header name, the request will be passed to the default site, which has no Host Header name set. The simplest way to deal with this is to create an "Under Construction" page as the only page in your default site. FTP does not have the Host Header name, so if you need to host multiple FTP sites, you will either need to change the port, or configure multiple IP addresses on your machine. -
Each web-site in IIS must have a unique "address", which is a combination of:
- The IP address it listens to;
- The port it listens to - normally 80 for HTTP and 443 for HTTPS;
- (For HTTP sites only) The Host Header name;
Assuming you are just setting up standard HTTP sites, you can host multiple sites on the same machine by changing one of these three parts. Since you will probably be using a single IP address, and you don't want to change the port, this leaves the Host Header name. Set this to the domain part of your site's URL - for example,
www.site1.com. Assuming the DNS forwww.site1.comis pointing to your server, you will then be able to openhttp://www.site1.comin your browser and see the pages for Site 1. If one site serves multiple URLs, you can add other entries by clicking the "Advanced" button in the properties of the site. NB: If someone requests a URL which is pointing to your server, but the domain is not set up as a Host Header name, the request will be passed to the default site, which has no Host Header name set. The simplest way to deal with this is to create an "Under Construction" page as the only page in your default site. FTP does not have the Host Header name, so if you need to host multiple FTP sites, you will either need to change the port, or configure multiple IP addresses on your machine.Wow! You're a treasure trove of IIS information, Richard! Thanks! I'll give that a try. Not knowing what to do with the header name box, I just left it blank... In the event that a company wants to set up multiple sites on an intranet, I assume then that the DNS entries would only have to be on the local DNS server, not on the public DNS system. That seems to be what Zhoujun is trying to accomplish. "When in danger, fear, or doubt, run in circles, scream and shout!" - Lorelei and Lapis Lazuli Long
-
Wow! You're a treasure trove of IIS information, Richard! Thanks! I'll give that a try. Not knowing what to do with the header name box, I just left it blank... In the event that a company wants to set up multiple sites on an intranet, I assume then that the DNS entries would only have to be on the local DNS server, not on the public DNS system. That seems to be what Zhoujun is trying to accomplish. "When in danger, fear, or doubt, run in circles, scream and shout!" - Lorelei and Lapis Lazuli Long
Roger Wright wrote: In the event that a company wants to set up multiple sites on an intranet, I assume then that the DNS entries would only have to be on the local DNS server, not on the public DNS system. Yep. You can even add entries to the "Hosts" file [C:\WinNT\System32\drivers\etc\hosts] to change the settings on a single machine, which is very handy if you need to test a site on your server before transferring the DNS. :)
