callico
asked on
Windows 2003 DC logon problem
Hello Everyone:
Here is the scenario:
I used to have 1 domain controller running Windows 2000 in my Windows Network. The web server, running IIS and windows 2000, was using domain users to control the anonymous access to every configured virtual website (i.e. MyDomain\IUSR_site1; MyDomain\IUSR_site1). Everything was working fine until I decided to add a secondary domain controller.
I decided this second domain controller to run Windows 2003. Installing and promoting this new server to domain controller went real smoothly.
The problem started 2 days after promoting the new server. I happen to had to restart the web server to apply new updates from Microsoft. Suddenly all my web sites started to display the “500 Internal Server Error”. The problem was easy to identify: the web server was unable to authenticate the IIS anonymous users in the domain. Errors messages like this were written to the Web Server Event Viewer:
The server was unable to logon the Windows NT account 'MyDomain\IUSR_site1' due to the following error: The specified procedure could not be found. The data is the error code.
After trying different things with no success I decided to restart the Windows 2003 DC and 2 seconds after clicking the restart button everything started working and continued OK when the Window 2003 DC was back online. Now every time I have to restart the Web Server, or even the IIS service, I’m forced to restart the Windows 2003 DC too in order to get the web sites working again.
Any ideas of what might be causing this problem?
Here is the scenario:
I used to have 1 domain controller running Windows 2000 in my Windows Network. The web server, running IIS and windows 2000, was using domain users to control the anonymous access to every configured virtual website (i.e. MyDomain\IUSR_site1; MyDomain\IUSR_site1). Everything was working fine until I decided to add a secondary domain controller.
I decided this second domain controller to run Windows 2003. Installing and promoting this new server to domain controller went real smoothly.
The problem started 2 days after promoting the new server. I happen to had to restart the web server to apply new updates from Microsoft. Suddenly all my web sites started to display the “500 Internal Server Error”. The problem was easy to identify: the web server was unable to authenticate the IIS anonymous users in the domain. Errors messages like this were written to the Web Server Event Viewer:
The server was unable to logon the Windows NT account 'MyDomain\IUSR_site1' due to the following error: The specified procedure could not be found. The data is the error code.
After trying different things with no success I decided to restart the Windows 2003 DC and 2 seconds after clicking the restart button everything started working and continued OK when the Window 2003 DC was back online. Now every time I have to restart the Web Server, or even the IIS service, I’m forced to restart the Windows 2003 DC too in order to get the web sites working again.
Any ideas of what might be causing this problem?
ASKER
Thanks for your answer.
The problem is that the server running IIS 5 is not a DC.
I've found an article from somebody with exactly the same problem:
http://www.derkeiler.com/Newsgroups/microsoft.public.inetserver.iis.security/2003-08/1037.html
...
The authentication works properly when the content is static, a directory listing or a .htm file, but fails if I link to an asp page. Could it have something to do with how the asp
authenticates? Specifically, I'm trying to get this working with the Certificate Authority webpages.
...
Not a valid solution so far....
The problem is that the server running IIS 5 is not a DC.
I've found an article from somebody with exactly the same problem:
http://www.derkeiler.com/Newsgroups/microsoft.public.inetserver.iis.security/2003-08/1037.html
...
The authentication works properly when the content is static, a directory listing or a .htm file, but fails if I link to an asp page. Could it have something to do with how the asp
authenticates? Specifically, I'm trying to get this working with the Certificate Authority webpages.
...
Not a valid solution so far....
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
All 5 FSMO Server roles have been transfered to the Windows 2000 DC.
I'm going to wait for a better time to stop and restart the IIS service and see if it works.
Quick question: Any idea why it wasn't working for the Windows 2003 server ?
I'm going to wait for a better time to stop and restart the IIS service and see if it works.
Quick question: Any idea why it wasn't working for the Windows 2003 server ?
ASKER
After moving all roles to the Windows 2000 DC the IIS is working the way it should even if it's restarted.
This is a good workaround but I'm still wondering why it was failing when the Windows 2003 was playing the FSMO roles.
Thanks a lot for for help.
This is a good workaround but I'm still wondering why it was failing when the Windows 2003 was playing the FSMO roles.
Thanks a lot for for help.
It's actually NOT a good idea to load all of the FSMO on one computer. Here's some light reading for you on ideal FSMO placement:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;223346
The link below explains why you are having difficulty login on to resources when your GC is down. To avoid this from happening (i.e. high-availability), you might want to consider having both DC to be your GC. Here's some more reading for you:
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q216/9/70.ASP&NoWebContent=1
- Info
http://support.microsoft.com/default.aspx?scid=kb;EN-US;223346
The link below explains why you are having difficulty login on to resources when your GC is down. To avoid this from happening (i.e. high-availability), you might want to consider having both DC to be your GC. Here's some more reading for you:
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q216/9/70.ASP&NoWebContent=1
- Info
ASKER
NONE of my servers were down and this is exactly the problem and the original question:
Why the webserver running IIS 5 under windows 2000 was unable to negotiate logon users with the Windows 2003 DC ?
Why the webserver running IIS 5 under windows 2000 was unable to negotiate logon users with the Windows 2003 DC ?
http://support.microsoft.com/default.aspx?scid=kb;EN-US;223346
If you move the Global Catalog server to the DC that is hosting the IIS, you shouldn't have any problems.
- Info