Discussion Locked

WWW and intranet on same IIS 5.0 server

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have an exsisting IIS 5 webserver that is up and running perfectly. We would like to host multiple intranet servers on the same box. I've read the documentation and all I see is that I can do this by assigning the same IP address with a different port number (user's will have to type in the numeric address of course).
So the Internet server's internal IP is 10.167.73.21:80. I created the first intranet site at 10.167.73.21:2001 and put out simple HTML files to tell if I correctly connectto the server.
When I type in http://10.167.73.21:2001/ I get a 404 error. The files are there, they have not been renamed and I do believe that I have all the permissions set.
Specs: Windows2000 SP2 running IIS5.0
Internet content root is at D:\wwwroot\
Intranet content root is at D:\intranet\

Help?

9 replies

by cswearingen

BTW, I know I can do this with Host Headers against the same IP address and also by putting multiple NICs in with different IP addresses for each card. I'm trying to get the mentioned approach to work first. We'll just create shortcuts on the client boxes to the intranet anyway. I'd like to know why it doesn't work when the documentation says that it's possible.

by cswearingen

Yep. Default docs are fine. The list shows "index.html, index.htm, default.html, default.htm, default.asp, index.asp'.
Even when I try to specify the exact file (http://10.167.73.21:2001/index.html) I get the 404 error. I also created a subfolder (called 'systems') and put an 'index.html' file in there. Again I get a 404 error.

by rarnold

Open up internet services manager. Right click the site containing the files and choose properties. CLick on the Documents tab. Make sure your default html page is added to the list( ie default.htm, index.asp, or whatever you named it.)

by cswearingen

Someone MUST know what the problem is here? If I put more points on this will someone help me?

PLEASE!

by joseph moore

Saw this old question and it made me think.
Just to ask a really stupid question here, you aren't running any packet filtering, like a firewall, between you and the web server, are you? 'Cause if that is the case, then a firewall could be blocking it. Also, an intelligent switch can do routing also, and it could block the TCP port 2001. You might want to make sure the network infrastructure between you and the web server all support passthrough to port 2001.
Other then that, it sounds like you have the 2 web sites set up right. You can run mulitple web sites on the same IP, just using different port numbers. Sounds like you set the different ports in Internet Services Manager correctly for each web site.
The only other thing I can thinkof is the NTFS security permissions on the D:\Intranet folder. Did you check them, to make sure the IUSR_WEBSERVERMACHINENAME account has access? 'Cause if you locked the Intranet folder down too tightly, and if you denied access to the IUSR account, then people will not be able to browse the web site. The IUSR account has to have at least Read access to the entire web site directory structure (all folders and files) unless you want to set up passthrough authentication, but that is a different matter entirely!

hope this helps

by cswearingen

Know what? I forgot this question was out there still! We found the problem already.
When I first started to set up the intranet site I started to put in a Host Header. Then I noticed (in the documentation) that I would have to put in a DNS entry for the redirection to work. Since our Network Admin was on vacation I went with the different port number approach. I forgot to take out the host header so it was confusing IIS and DNS when trying to resolve the header.
We started over and used Host headers with DNS entries for the redirection. Everything is working like charm now (we actually have three servers running now). Thanks for the input though. It's appreciated more than all of you can know.

This discussion is closed to new replies.