The parts of IIS6 that run and execute your website/pages do not have
privileges to change IIS configuration.
Thus, if this is not a behavior of SPS, then someone/something else with
administrative privileges on your server is making the change, and it is not
IIS...
Right now, it sounds like you may have something else running on your
systems that is auto-configuring this property. With Windows Server 2003
SP1, you get metabase auditing which can help track down when and who
changed the particular metabase property.
--
//David
IIS
http://blogs.msdn.com/David.Wang This posting is provided "AS IS" with no warranties, and confers no rights.
//
[quoted text, click to view] "Cnsrvative" <Cnsrvative@discussions.microsoft.com> wrote in message
news:590F75BB-D2D8-414D-9EB8-CDBBA6931A9D@microsoft.com...
Have been hunting down this ghost for 2 months now - any feedback is
appreciated...
We have a Server 2003 Std Box, running IIS 6.0 (all updates installed - NOT
2003 SP1). It hosts Sharepoint portal server, and our Project server and
only allows access to clients on our LAN.
In IIS, (Computer Management|Servuices and Applications|Internet Inford
mation Services|Web SIties|Properties|Directory Security|Ip Address and
domain name Restrictions|Edit) we have NOT configured any IP addresses or
domains in this box, and have by default GRANTED ACCESS to all computers.
Occasionally, and at random, this box will become populated with IP
addresses on our LAN - thus denying them access. They can be client IP's,
other member server IP's, even Domain Controller IP's and they appear
totally
at random and are NOT always the same IP addresses.
Have posted this in the SPS newsgroup and no one had ever heard of
SHarepoint behaving like this. Wondering if anyone has seen IIS dynamically
update this information, or if they have seen another program interfere with
IIS in this way.
Thanks in advance for any insight!