Multiple sites on one IP

[lwinstead]

Hi everyone,

This has been driving me nuts all day:
(I understand how to basically make a new DNS entry in order to have multiple DNS "names" point to the same IP addy, and then from there create a new IIS "Site" using this host name.)

I'm trying to add a new site on our Win2k server running IIS 5.0. Its a new IIS setup, so nothing to migrate. I see the default site, default admin site, etc. I understand that the default web site's home directory is 'c:\inetpub\

http://wwwroot'.

I also understand that, by default, when punching up this computer name in a webbrowser, I'll get the default.htm page displayed (provided I have one, which I do). That's all well and clear.

But here's my problem: When I create a new "site" using the aforementioned host name, and point the Home Directory to a DIFFERENT folder on the computer (in fact, a different volume on the same server), I can't get the "default.htm" page to display! This "Home Directory" contains nothing but the "default.htm" file, and there's no virtual directories created for this "site". The strange thing is that when I recreate this new site and point the "Home Directory" to a folder within "C:\inetpub\", it works like a charm. Also, if I explicitly enter "

http://<alternative

server name>/default.htm&quot; then the &quot;default.htm&quot; gets displayed. (Keep in mind I'm using a host header name) So what is it about this new site that doesn't want to default to the &quot;default.htm&quot; file unless specified? I thought it was supposed to automatically search for a &quot;default.htm&quot; file??

ARRRGGGHHH.

The whole point to this is to create an in-house Intranet for exclusively internal use. The server is behind a firewall, and isn't reachable from the outside.

Can someone help me figure out how to create a second site on a server with the &quot;Default&quot; site already running? I'm in serious need of some help here... <<<<[flux]>>>>

 

[SWD]

sounds like default.htm is not one of your allowed start files. Add it to the list and all should be good. Look at the 'documents' tab for this.

Also make sure your folder permissions are correct when setting up webspace other than inetpub. Roger Villeneuve

http://www.swd.ca

 

[lwinstead]

Thanks for replying, Roger.

The default.htm document is, indeed, setup, as per the default setup of a new &quot;site&quot;. Secondly, file permissions are wide open; &quot;everyone&quot; has FULL control over the webspace, so I can't see how permissions would be out of whack, unless I'm missing something more.

Any more ideas? <<<<[flux]>>>>

 

[lwinstead]

Wait wait wait...

I decided to play around more, so I created a folder in the webspace called &quot;

http://wwwroot&quot;

and set the &quot;Home Directory&quot; to that new folder and voila! Everything works correctly. So why would it need a subfolder in the webspace in order to correctly utilitize the Default.htm file? WTF?

(The webspace, incidentally, is a separate volume mounted in a different volume on the server... would that have anything to do with it??) <<<<[flux]>>>>

 

[sparky0904]

Could u not add extra ip's to your server then have each DNS entry point to a different IP.

You can then create a totaly seperate Web site with its own directory and just point the IP at it. Mark Taylor
Technical Manager
NHS

 

[lwinstead]

Mark,

Sure, I could have done that. But instead of going the easy route, I wanted to play with host header names. ... I suppose in a way, either adding an extra IP or just creating a new DNS name... either way is playing with the same thing, eh?

In any case, Mark, yes, I could have. I just chose not to.

(And I'm still wondering if/why I needed a subfolder in order to properly activate the &quot;default.htm&quot; file...) <<<<[flux]>>>>

 

[Workmen]

Hi lwinstead,

I ran into this problem awhile back. After setting your home directory on your new website and exiting properties. Right click the website name and go to &quot;all tasks&quot; selection. Select &quot;permissions wizard&quot;, click &quot;next&quot; and choose &quot;Select new security settings from template&quot; and click &quot;next&quot;. Select &quot;Public web site&quot; and click &quot;next&quot;. Select &quot;Replace all directory and file permissions (recommended)&quot; and click &quot;next&quot;. You will now see the changes that will be made. Click &quot;next&quot; and your site will be viewable.

Your problem was caused by ACLs not being set.