2008 R2 server cannot reach domain sysvol folder

I'm seeing a couple of my 2008 servers having a SYSVOL problem on the domain.  Could be stemming from an old DC that was removed and replaced.  Trying to fix it so it can reach SYSVOL and update policies.  I can see an old SRV record among the good records, showing the old DC server, and wondering if this is the culprit.  But here is what a GPRESULT yields:

Group Policy Infrastructure failed due to the error listed below.

Logon Failure: The target account name is incorrect.

Note: Due to the GP Core failure, none of the other Group Policy components processed their policy. Consequently, status information for the other components is not available.

How do I troubleshoot this one?
Damian GardnerIT AdminAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Will SzymkowskiSenior Solution ArchitectCommented:
Run the following commands...
repadmin /replsum
repadmin /showrepl
repadmin /bridgeheads
dcdiag /v
netdom query fsmo
netdom query dc
nslookup ForestDnsZones.domain.com
nslookup DomainDnsZones.domain.com

Also I would also check to make sure that the metadata has been cleaned up accordingly.

http://support.microsoft.com/en-us/kb/216498

I would also make sure that you go through all of the sub folder under the _msdcs.domain.com folder and make sure that if there are any SRV records that were from old domain controllers you can simply delete these.

Will.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Damian GardnerIT AdminAuthor Commented:
ok - thanks for that.  I did check the SRV records and found the last one of about 8 records is the old DC that should be removed.  I couldn't find the command to remove it, however.
Peter HutchisonSenior Network Systems SpecialistCommented:
You can use the Dnscmd /recorddelete to delete records from the DNS server or you can use the DNS console from the administrative tools if the RSAT tools are installed.

https://technet.microsoft.com/en-us/library/cc756116%28v=ws.10%29.aspx#BKMK_15
Are You Protected from Q3's Internet Threats?

Every quarter, WatchGuard's Threat Lab releases a security report that analyzes the top threat trends impacting companies around the world. For Q3, we saw that 6.8% of the top 100K websites use insecure SSL protocols. Read the full report to start protecting your business today!

Will SzymkowskiSenior Solution ArchitectCommented:
Do it from the DNS console. Right click the record and select delete.

If you have found 8 records just in the _msdcs.domain.com alone this could create a lot of issues for this.

Once you have deleted them you might also want to restart the NetLogon service as well.

Will.
Damian GardnerIT AdminAuthor Commented:
Gents - I had some success this morning after rebooting the server last night (after installing the RSAT tool).  I believe all I did so far was to use the IPCONFIG /registerdns command. After rebooting, the server was able to reach the SYSVOL folder.  But the SRV record for the old server is still though, so I will try your suggestion to use the DNS console to remove it.  will let you know.

thanks
Damian GardnerIT AdminAuthor Commented:
Would I need to run the DNS consoles from the local machine?  if so, it's failing to start.  dnscmd looks like it works though. theres more syntax to know for that though...
Damian GardnerIT AdminAuthor Commented:
Will - thanks for your help.  I was able to use some of your commands and also used the DNS console to remove the bad SRV records. All is ok now.  thank you!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.