running a service account and looked at soem other options. I guess I was
trying to perhaps do to much with what I had. Sharepoint is on the same
server and runs ok (But I understand that). I totally understand now why
public sites are best left away from the DC.
Thank you for the log options as well. Regards,
"David Wang [Msft]" <someone@online.microsoft.com> wrote in message
news:uqAnsIn$EHA.2540@TK2MSFTNGP09.phx.gbl...
> Actually, your issue is probably very different than the other user's.
> Your
> machine is a DC, his was not. That is a big difference when it comes to
> IIS
> (and many programs, for that matter).
>
> First uncheck IE's "Show Friendly HTTP Errors" option and report the
> actual
> error response (and status codes). Also, report the web log entry for the
> failed request -- if it was a connection-level issue, it will be in
> %windir%\System32\LogFiles\HTTPERR\*.log , while if a request failed to
> execute, it will be in %windir%\System32\LogFiles\W3SVC#\*.log . Without
> detailed failure logs, it is hard to troubleshoot the actual issue.
>
> In general, running IIS6 on a DC does not work because of various
> restrictions a DC places on the machine, different user privileges, and we
> really could not make it work on more than a couple of basic scenarios by
> default and in general, it requires a lot of tweaking of settings
> everywhere. It is simply not recommended, on top of the general advice of
> not running external-facing servers on the DC -- one compromise from
> external source via any mechanism, and your entire domain is
> compromised --
> and a DC is designed to be accessed by other machines so it is harder to
> lock down without breaking functionality.
>
> It is important to note the order of installation -- did you install IIS
> before or after the machine ran DCPROMO to become a DC.
>
> --
> //David
> IIS
>
http://blogs.msdn.com/David.Wang > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> //
> "Ivan Brebner" <ibrebner@premiumretail.com.au> wrote in message
> news:eSGamJi$EHA.1408@TK2MSFTNGP10.phx.gbl...
> Hi there,
>
> Well I dont have too much to add other than the fact that I have near the
> very same issues you are having.
>
> I have a 2003 Server that is the DC that runs a public website on IIS 6.0
> ... well it supossed to. Anon account is by default IUSR_Servername and I
> have altered the password. I have reflected this in IISAdmin so that it
> would work. It seems that the IUSR Account is the issue under a domain and
> this has trouble impersonating as it seems that the account needs to align
> with the computer rathen than the Domain. I have been looking down my nose
> at this one all day and still no go. I have been viewing my site from the
> outside (it find the public DN and says site found, then times out after
> about 60 secs or so).
>
> Hope this helps at least in describing errors.
>
> Any help would be appreciated.
>
>
> Ivan Brebner
>
> "willie thompson" <wullsy@yahoo.com> wrote in message
> news:41e7e503$0$114$65c69314@mercury.nildram.net...
>> Hello,
>>
>> I'm having an Anonymous access problem which is driving me round the bend
>> !
>>
>> Basically, I created a website a few years ago, stuck it on a Windows
>> 2000
>> server and made it live on the internet. Everything was fine, and a month
>> or
>> so back I upgraded the server to Windows 2003 standard, using the upgrade
>> option to upgrade the server. The website still works just fine.
>>
>> Now, we've decided to create a new website from scratch. That's been done
>> and it works fine internally. I created a new virtual directory using the
>> exactly the same settings/login credentials as before, just pointed it to
>> a
>> different directory. Externally, I get this error :
>>
>> Unauthorized: Access is denied due to invalid credentials.
>>
>> I've no idea why! If I use Basic Authentication, I get a login box from
>> outside the network, and when I enter the same user name, domain and
>> password I was using for Anonymous Access, it works ! Naturally, I don't
>> want a user name and password to appear for random visitors to my
>> website.
>>
>> Just a bit more background:
>>
>> - the webserver is a member of a domain
>> - the user name and password I'm using is on the same domain
>> - NTFS permissions are the same on the one that works and the one that
>> doesn't
>> - the old website still works just fine
>>
>> I've done a fair bit of googling with no luck.
>>
>> anyone any ideas ??
>>
>>
>>
>
>
>