"Drew" <Drew@discussions.microsoft.com> wrote in message
news:A86D09A8-B31E-4C78-9519-6C47D9A5C5E5@microsoft.com...
> The websites work fine on port 80. When I terminal into the web servers,
> I
> don't get this error so the only troubleshooting to do is to find out why
> I
> can't remotely administer IIS. I don't want the webmasters remote
> desktoping
> into the servers.
>
> Drew
>
>
> "David Wang [Msft]" wrote:
>
>> Sounds like on the problematic machines you have something else listening
>> on
>> port 80 and preventing IIS from binding to "All IP address" on it.
>>
>> In general, you want to troubleshoot the server using log files from the
>> server. You don't want to rely on remotely gathered details, such as
>> MMC's
>> ability to show files or browser's error response to troubleshoot,
>> because
>> they are not guaranteed to be correct, from a security point of view.
>>
>> --
>> //David
>> IIS
>> http://blogs.msdn.com/David.Wang
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> //
>>
>> "Drew" <Drew@discussions.microsoft.com> wrote in message
>> news:FB744CCF-A16F-40C8-8F01-EAE85C4390B2@microsoft.com...
>> >I have installed IIS manager on a central machine and made an MMC with
>> >IIS
>> > for several web servers. It connects and shows me everything including
>> > websites. On some servers, when I click on a website it says "This
>> > site
>> > cannot be started because another site running on this computer is
>> > already
>> > using the IP address......" The website is running the All Unassigned
>> > setting with a host header.
>> >
>> > Also, the MMC shows that the website has no files.
>> > I can go to the properties of a site and see everything just fine.
>> >
>> > I can connect to certain servers and see everything just fine. Makes
>> > me
>> > think there is a security setting somewhere stopping me from getting
>> > full
>> > functionality.
>> > Anyone know how I can stop this error and see the website files?
>>
>>
>>