Try changing the amount of virtual memory. Windows may have set it to a low value due to the low hard drive space. I have seen agonizingly slow startups (and broken startups) if there is not enough virtual memory.
Main Topics
Browse All TopicsHi,
We have a VERY old machine that is a domain controller and also runs a couple of not so critical sites. This machine was not updated for years. Yesterday we found it has 1MB space left!! and event log errors stating this. We deleted some old site files and temp files. We made 230MB space and rebooted. Now it is stuck at boot screen saying applying security policy. We can get in via Safe mode. It now takes about 2 hours to go past this screen and login. Since this is a domain controller, all our other servers are experiencing problems. We are seeing errors like "Windows cannot determine the computer name. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted. " and "The browser service was unable to retrieve a list of servers from the browser master \\DC-THE_DOMAIN on the network" DC-THE_DOMAIN is the domain name.
The domain is Windows 2000 server sp3
Can anyone suggest what to do?
Many thanks in advance
H
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
We have one other domain controller.
What do you mean shutting this DC. Do you mean turn it off? Will the other DC start servicing the network? When the bad DC was stuck in rebooting screen other servers were reporting errors so I guess the other DC wasn't jumping into action in its place.
>>rebuilding it or repairing it or replacing it and there are a number of options for accomplishing each of these steps.
Could you give me these options (not necessarily in detail for now) and which you would select if you were us and why.
Thanks
I would imagine that because the DC was partially up clients were trying to use it, if it is shutdown then the other domain controller would take over (unless your domain is completely shafted).
With regards to options for repairing a good place to start would be applying SP4 and all outstanding critical and security hot-fixes (ultimately both DC's need to be at the same patch revision).
With regards to rebuilding you would need to move all the data to another location, transfer the FSMO roles, DCPROMO the server back to a member, move any other network services (DNS, WINS, DHCP etc.) and then re-install the O/S (patched to latest revisions), DCPROMO the server to be a DC and re-enable required network services.
Replacement would be similar but using new tin for the re-install.
There is quite a bit more to this but the above should give you some idea of how to proceed.
Cheers,
Jason
Thanks for that Jason.
Since I don't know much about networks (guy who does know a bit is on holiday), is it possible that some of our servers are members of the bad DC and others members of the good DC and that because of this shutting down the bad DC will not help those servers that were relying on it? Is there a way for me to see what machines on our network are members of what domain? I have administrator access.
In terms of rebuilding/replacing, I think replacing might be a better option because then we can buy a server that has lots of space, memory and put the latest OS + batches+SPs
What is FSMO roles?
Ta
H
Are you saying that you have two domains and one domain controller per domain?
I would agree that replacing is better if you have the budget.
FSMO roles:
http://support.microsoft.c
>>Are you saying that you have two domains and one domain controller per domain?
I am starting to think that we have 2 domains with 2 different domain controllers - I am not certain though. If I go to my networks on my PC, it lists all our personal PC's, our Exchange server, all our database servers and domain controller for the (good) domain that our personal PCs are member of. The bad DC has all web servers as members. Having said that, I can connect, from my PC, to all web servers via explorer accessing shared folders. I.e \\webserver1\c$\temp I can also Remote Desktop Connect to all the web servers using my personal account (not admin) which is on the good domain, so I don't know how that works. The 2 domains are somehow accessible to each other. Ignore anything obvious that I say pls, as I don't know much about this topic.
We have no choice but to budget for a decent DC as we have clients relying on our services and a bad DC as it looks now can be headache, so yes, replace is probably the route we will take.
I am checking out the FSMO now
Ta
H
You can determine wheter or not the domain controllers are in the same domain. Open up Active Directory Users and Computers on the good DC and browse to the Domain Controllers OU. If there is only one DC in there then you have two domains and should not shut the other DC down. If you have both DC's in there then shutting the DC down is an option.
When budgetting for new hardware considering buying two domain controllers to give you fault tolerance.
OK. On the good DC, AD shows 2 DC listed, itself and our Exchange server (which I thought was not a DC), so we have 3 DCs. The bad DC cannot be seen here. I guess then shutting the bad DC is not going to help here.
Agreed to consider buying 2 DCs but how do you achieve fault tolerance? Is it automatic or something that needs setting up like Windows failover clustering?
TheCapedPlodder,
I would like to open a new question that deals with how to setup a new DC from scratch (install OS, patches, SPs, then setup and connect to network). It is a big responsability as it will affect all our network if I get it wrong so I am playing safe and get advice from those who did it before. Is this an area you can help me with?
For this question, I would like to keep it open till next Monday when the person to make the decision as to which direction to proceed will be back, just in case I need more clarification. Other than that this question is pretty much answered
Cheers
H
Thanks J,
We are deciding on Monday how to proceed. I will come back on Monday to let you know what is happening. There is some office politics going on at the moment so a decision cannot be reached today.
Your help is really appreciated. Speak to you on Monday. In the meantime have a great weekend. Don't party too hard :-)
H
FTR, I had this issue: Terminal Server TS1, domain controller and Exchange/file server SBS1. One user (out of several tens), just after changing his password. Symtomps: subsequent logins to TS1 went seemingly OK, but logged 1055 from Userenv and 1010 from MsGina (see also www.eventid.net). After logging in, the user could not access any resources on SBS1, be that Exchange or files/folders. The user just got auth question, no passwords were accepted.
The fix was opening the password applet from Control panel ("Stored User Names and Passwords" or the likes) and removing an entry for SBS1, and re-login OK.
Business Accounts
Answer for Membership
by: TheCapedPlodderPosted on 2008-04-09 at 03:26:41ID: 21313337
How many other domain controllers do you have?
I'd suggest shutting this DC down so the other DC's can get on with servicing clients.
That will get over your initial problem and you can then focus on bringing this server back into service either by rebuilding it or repairing it or replacing it and there are a number of options for accomplishing each of these steps.