Problem solve Get help with specific problems with your technologies, process and projects.

Why does device reboot or 'blue screen' when Win2k systems attempts to logon to NT4 domain?

My company currently has a Windows NT4 domain environment with a very restrictive system policy. Many members of our IT staff have Windows 2000 Professional desktops along with a sparse number of Windows 2000 servers. When a Windows 2000 system attempts to logon to the NT4 domain, the device will either reboot or 'blue screen' with a stop code of c0000021a and then reboot. What is causing this and how can I fix it?

I'm betting that you have a system policy that changes the permissions on the %systemroot% folders to prevent ordinary users from making changes to the system files. It's possible that one of these files is required by a user in Windows 2000 and that is causing the c0000021a bug check.

Look over your configuration files, logon scripts and system policies to see if you are making any permission changes. If nothing looks out of whack, the next step is to create a group that is exempt from system policies and logon scripts and see if it has the same problem. If so, then you might have deeper issues.

Just as a thought, do you have a Default User profile in your Netlogon share? Some shops use this to provide a standard initial profile to new users on their desktops. There might be a setting in this default profile that is causing the W2K machines to cough up furballs.

Dig Deeper on Windows Server storage management

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.