IIS ¦ Hosts question

[tsp1lrk]

Hello,

Is it possible, running the

http://WWW service

to not have your workstation act as a host? We are contemplating the decision to disable the

http://WWW service

on our Win2K installs; but if we do keep it enabled, is there a way to do this?

Registry Key?
Different Port?

Any information appreciated,
Lisa
UPS

 

[itguru]

Hi!

Yes stop the web site from Management console. iis_guru@yahoo.com

 

[tsp1lrk]

Thanks,

I'll see if this what our dept. is looking for...

Lisa

 

[tsp1lrk]

Well, stopping the web site will not allow the developer to work locally on the PC... this will not work. What about rights? Can we change the rights? Here's the scenario:

http://WWW enabled

to the point the developer can do his/her job. But, I don’t want anyone to be able to point their browser at that workstation address and get a web page.

 

[SheldonC]

In IIS you can determine which IPs can contact the server. If you go into IIS and select the properties of your

http://WWW site,

you should be able to go to the tab on the far right (I believe) and "Grant" or "Deny" access to that particular site. Select "Deny all eccept for," then add your the workstation IP (if static) or I think the loopback will work too (127.0.0.1). Tell me if this is what you're looking for, or if it works or not. I'm doing this off the top of my head so it might not be accurate.

 

[tsp1lrk]

I think this is what we are lookin for... I will forward this info on... one question; in Windows 2000, that area under directory security for IP address deny/grant is greyed out... any reason for that?

Lisa

 

[tsp1lrk]

Just found out that that area is dimmed out on a workstation... we need to do this from a workstation, not a server. Help!!!!

 

[SheldonC]

Which 2000 are you using? Server, Advanced Server, Proffessional? From the Server editions, you should be able to specify which IPs to deny. You sure that you are using the IP protocol on your network right?

 

[tsp1lrk]

Yes it is IP based, it is workstation, not server that's why we can't do it... that I know. I think we have to just tighten NTFS security on the

http://wwwroot

directory.