Solved

Windows 2003 DC logon problem

Posted on 2004-03-22
7
1,085 Views
Last Modified: 2010-04-19
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?
0
Comment
Question by:callico
  • 4
  • 3
7 Comments
 
LVL 11

Expert Comment

by:infotrader
ID: 10655544
I had the same problem.  I think the problem can be related to the placement of the FSMO:

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
0
 

Author Comment

by:callico
ID: 10658930
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....
0
 
LVL 11

Accepted Solution

by:
infotrader earned 500 total points
ID: 10658958
Ok...  same concept, different machine.

If you move the Global Catalog server role to a different DC, you shouldn't have any problems.

- Info
0
Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

 

Author Comment

by:callico
ID: 10661494
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 ?
0
 

Author Comment

by:callico
ID: 10664099
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.
0
 
LVL 11

Expert Comment

by:infotrader
ID: 10664449
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
0
 

Author Comment

by:callico
ID: 10667977
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 ?
0

Featured Post

Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Organizations create, modify, and maintain huge amounts of data to help their businesses earn money and generally function.  Typically every network user within an organization has a bit of disk space to store in process items and personal files.   …
by Batuhan Cetin In this article I will be guiding through the process of removing a failed DC metadata from Active Directory (hereafter, AD) using the ntdsutil tool in a Windows Server 2003 environment. These steps are not necessary in a Win…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
A company’s greatest vulnerability is their email. CEO fraud, ransomware and spear phishing attacks are the no1 threat to a company’s security. Cybercrime is responsible for the largest loss of money to companies today with losses projected to r…

914 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now