Yes i think that too. That is an error in group policy and now i know why i have got it.
I have uninstalled DNS & DHCP which were installed in active directory. By doing that i have crashed active directory. After server restart i did last night i had no domain controller any more.
I will probably reinstall OS all over again and it seams like only permanent soultion.
I havent had the chance yet to check the event logs yet...my userenv 1000 may have gone away now!
Anyway, yes, DNS is fully integrated into AD, remove DNS, and you will crash AD. However, I would think that you can reinstall DNS, or just do a repair, to fix it?
I think theres AD repair tools out there too, but I wouldnt know which to use.
Well it crashed my domain controller. I could reinstall it if it was not only domain controller i have (no backup one). And i will try that tonight. But if not weekued is for setup and fine tunning of the server.
I had problems with stability all the time. Internet connection to local ISP was droping all the time. I have used internet connection sharing with local DNS & DHCP installed. It seams that this option is not functioning well, so i will try to use ISP DNS adresses and fixed IP's for network. No local DNS and no local DHCP.
I had the same problem with my single domain controller, always dropping internet, needing reboots, etc...
Try this, use fixed IP addresses on your network, and quit using DHCP, but keep running DNS, cause you have to for AD anyway. This cleared up lots of issues we were having!
It seems that if you run DNS, DHCP, and ICS all on the same server at the same time, you get "issues"
Basically, Ive left ICS running, and DNS, and turned off DHCP, give that a try and see if it doesnt clear up some problems.
(Im using ICS cause I couldnt figure out how to get NAT to work.)
I have reinstalled the server again during the weekend. This time i have tried a diferent approach. Instead of 2 lan cards, i have connected routed directly to switch alowing network internet connection to function no matter is server running or not (if they use outside DNS). Server is neccecary only as DNS server and i have routed all DNS requests to it.
It took a while to reprogram cisco router and to join all computers on new DC but it works perfectly now.
I have had the 1000 event ID also but i traced the problem back to a bad username or password being used by an application. In one case, my backup program was trying to use a account with a changed password. Once i corrected the password in the backup program, the Event ID 1000 went away.
Just something to think about if you happen to run into the event again.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.