Question : Why do I need to run gpupdate /force after rebooting domain controller

I have a domain controller running windows server 2003 sp2.  After a reboot network shares are unavailable and I can't access active directory.  Event id 1030 and 1052 are logged in the application log.  Event id 4000 is logged in the dns events.  If I run gpupdate /force it resolves my issues.  Any idea why this is happening?

Answer : Why do I need to run gpupdate /force after rebooting domain controller

Event 1030 is a very generic event and indicates you can't find Group policies. this could be a problem with Netbios, FRS, or DNs Event 1052 indicates another machine on the network has the same Netbios name as your server.

FRS is having problems. Event ID 13508, says it can't find the servers to replicate to. Event 13509, says your server found its replicaton partner and is ready to replicate to it.

Event 4000 DNS means the server can't open AD.

Your saying GPupdate /force resolves your issues.

I am beginning to think you have a group policy to disable Windows firewall, and when you GPupdate, windows fiewall disables itself. I think windows firewall is running on your server upon bootup. Or you have a client with the same name as your server and on the same domain.

So, go to the command prompt of any computer or server and type:
NBTStat -a xxx.xxx.xxx.xxx

Where xxx.xxx.xxx.xxx is the IP of your server. That should resolve to netbios names of your servers IP. The one Netbios name that is NOT your server should be given another IP, and your server's IP should NOT be within the DHCP scope or address pool unless and exception has been made for that IP.

Put it all together and it looks like you have a problem with netbios and DNS protocols.

Random Solutions  
 
programming4us programming4us