• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 334
  • Last Modified:

Domain connection failure

following advise of today after a major power failure in the office.  Win7 clients stopped being able to connect to NAS drive and folder shares.  Suggestion was to reconnect the clients to the domain.  Have tried one client and it fails on the Network stage.  One trying from the Control panel this error is reported.  Anyone know of a solution?

******

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "cs.loca":

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.cs.loca

Common causes of this error include the following:

- The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:
0
TMS
Asked:
TMS
  • 9
1 Solution
 
Life1430Sr EngineerCommented:
Please check you DNS settings and make sure below best practices are correctly defined in your env


Best practices for DNS client settings on DC and domain members.
http://abhijitw.wordpress.com/2012/03/03/best-practices-for-dns-client-settings-on-domain-controller/
0
 
TMSAuthor Commented:
Sarang, The DNS looks fine.  I have noticed another issue after restarting the server and that is the RPC shows running in services but if I open Active Directory it say it is not and I can't open Active directory.  Outlook clients can't connect to exchange but my iphone does.
Seems something a little more fundimental is wrong.
0
 
TMSAuthor Commented:
One other thing.  I noticed that when using my account to log into one client it denied me with the trust error on the domain. When I used another admin account it logged in.  I'm wondering if some credentials have been corrupted?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
Brian PiercePhotographerCommented:
stop and restart the NETLOGON service, then check to see if the SRV records have been created.
0
 
TMSAuthor Commented:
Are you saying svr records will be created by the netlogon service?  It's restarting now.  It didn't let me the first time but second try and it is stopping and starting all the other services.
0
 
TMSAuthor Commented:
Ok, all the svr records in DNS were time stamped an hour ago, probably when I restarted the server before
0
 
TMSAuthor Commented:
I have also noticed there are "?" Next to default domain and share point web services.  The sbs company web doesn't work and when I try to log onto the server via Remote Desktop or owa I get a certificate warning.
0
 
TMSAuthor Commented:
Sorry when I mentioned the rpc service I was not looking at exchange which I meant to.  Anyway for some reason that doesn't start automatically now.  I sense I'm heading to a new installation at some point but I agree the domain join issue can't be caused by many things.
0
 
TMSAuthor Commented:
Running dcdiag the enterprise test says error 1355 global catalog server could not be located.
0
 
TMSAuthor Commented:
This problem was as a result of the Sysvol subfolders not mounting during startup.  The NTDFS service did not produce the Do Not Delete folder so the NETLOGIN could not create the subfolders.  I copied over the sysvol folders from the RODC and the server started to report as a Catalogue Server.
0
 
TMSAuthor Commented:
Reason I accepted my own solution is because I go it working but not fixed.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 9
Tackle projects and never again get stuck behind a technical roadblock.
Join Now