Basic Windows Server 2003 Stuff

[schueymcfee]

I have 4 IP addresses all unassigned so they're running off the default website already set-up by Windows.

This is in C:INETPUB/wwwroot

Now I've set-up a new site in C:INETPUB/wwwroot/site

and I've tried to assign an IP to that location, but all I get is "Bad Request Invalid Host Name"

Have I missed something here?

[BliarOut]

Not really enough info to go on as yet. It sounds a bit like a dns problem, what is giving you the error, IIS manager?

[schueymcfee]

You'll have to bear with me I'm afraid - numpty alert!

I get the error when trying to access the IP from the internet

I haven't done anything with DNS, I got the server with a fresh install of IIS, it had default website already set-up and 4 IPs all unassigned.

Tried to assign one to a new web-site I set up in IIS and it doesn't work!

That's all I can tell you!

[schueymcfee]

Okay I think I've sussed it, although its asking for username and password.

I think all permission are okay

[malman]

So if I get you right.

You have been into the IIS management console and added a website then in the properties instead of "all unasigned" you have changed it to the ip address you want but when you try to access the website from the internet you don't get the page. Correct?


If you fire up a browser on the server itself and enter

http://xxx.xxx.xxx.xxx

with the IP you have set does IE get the page?

[schueymcfee]

It does now, I've moved the location to D:home/site

Now instead of getting an error I get asked for username and password

[BliarOut]

schueymcfee said:

It does now, I've moved the location to D:home/site Now instead of getting an error I get asked for username and password

Ignore my last post if you saw it. That is a step in the right direction. Sounds like you need to allow anonymous access to the site now.

[schueymcfee]

It is, its allowed for IUSR but still refuses to let me in.

[schueymcfee]

It's saying that my ACL??? is not configured properly

[BliarOut]

Bit of a cop out, but the answer is in here.

http://support.microsoft.com/search/d

That link will take you to all the MS support documents on resolving IIS ACL issues. Just a bit busy to run throuh it all at the mo.

[jamieboy]

schueymcfee said:

It is, its allowed for IUSR but still refuses to let me in.

Remember that as well as the Directory Security tab in IIS Manager, you also need to check the permissions on the files themselves, i.e. check that your IUSR_xxx user has at least 'read' to d:\home\site and its contents.

[BliarOut]

Doh, the link didn't come out....

Go to http://support.microsoft.com and put

IIS ACL

in the box marked "Search the Knowledge Base" That should help, but if it doesn't, post back.

[schueymcfee]

Okay, I moved the site back to C:INETPUB/wwwroot and it worked fine

No permission problem or bad request.

Start on a new IP and I have the same problem, is there some kind of delay in the IPs being assigned to a destination?

[BliarOut]

The 4 IP's needs a bit more explanation. Why not leave it on the default and listen on all IP addresses? I'm sure there is a reason, but it helps to clarify what you're up to.

[schueymcfee]

Basically I need 4 different sites to run on 4 seperate IP addresses on the same server for SEO.

Now my logic would've thought that all I needed to do was to create a new site in IIS and assign an IP address to it. That doesn't seem to work.

[schueymcfee]

I think I've got it.

When I tried to set-up a new site it wouldn't let me set it to port 80, so I selected port 81, which now I know wouldn't work , anyway I managed to change it back to port 80 in the properties without it kicking up a fuss and all is okay now.

Thanks everyone for their help.

[malman]

schueymcfee said:

I think I've got it. When I tried to set-up a new site it wouldn't let me set it to port 80, so I selected port 81, which now I know wouldn't work , anyway I managed to change it back to port 80 in the properties without it kicking up a fuss and all is okay now. Thanks everyone for their help.

Give it a reboot and check the event viewer to make sure all the web instances bind without error to port 80 just in case.

BTW
In IIS you don't always need different IPs for sites. If you are running multiple http sites you can use host headers on the same IP on port 80. There are other reasons why you may want to run different IPs for plain http though.

https requires different IPs but thats on port 443.