Re: Domain controller for the domain XXX could not be contacted

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Sorry if you have already answered this Scott, but is the DNS of the client
machine you are having problems with pointing at the AD server?

I had a similar problem with AD servers appearing and disappearing, once I
pointed the DNS of the clients to that server all the problems went away.


"Scott" wrote:

All ip and DNS info were setup.

"Dave Patrick" <DSPatrick@xxxxxxxxxxxxxxxx> wrote in message
news:e3scQ8swIHA.524@xxxxxxxxxxxxxxxxxxxxxxx
Try joining again but with static IP and DNS addresses.


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Scott" wrote:
I have a single PDC Win 2003 server with 2 WIN XP PCs connected. I have AD
setup correctly and have been running fine for years. I just reformatted
PC1 this week. I joined myDomain fine and installed by basic apps such as
Office 2003, Acrobat 8 and PhotoShop. However, after having successfully
mapping a couple of drive letter to shares on the PDC, after using the PC1
for about 30 minutes configuring my user profile, I noticed I couldn't
access the mapped drives.

So, I unjoined myDomain and joined WORKGROUP. After rebooting, I tried to
re-join myDomain and received the error "domain controller for the domain
'myDomain' could not be contacted". My PC2 and PC3 have no problems
accessing the PDC and myDomains resources.

I've tried System Restores and even renamed PC1 and tried to join
myDomain, but nothing seems to work. I've been a Sys Admin for 16 years
and never seen such behavior.

Can anyone shed some light as what I can check? I've been over my TCP/IP
settings over and over, but everything looks fine. I even deleted my nic,
reinstalled the nic drivers, but I still get the error.

Any ideas?





.

Relevant Pages

  • Re: Client PCs not showing in DNS
    ... Is the server on a static IP? ... "Scott N" schreef in bericht ... > to my client. ... DNS had my office IP as the servers IP ...
    (microsoft.public.windows.server.sbs)
  • Re: Client Server Setup
    ... The Server should have a domain set up on it. ... "Scott Viney" wrote: ... IE Peer to peer. ... >>> From the systems I have worked with before its been client server setup. ...
    (microsoft.public.windowsxp.general)
  • Re: OWA "Page Not Found"
    ... Jeff ... > client can access ... >>the email server. ...
    (microsoft.public.exchange.admin)
  • Re: Aquiring Email Address
    ... address, and getting it on the client side (which is what you would have to do, not on the server side), would require too much setup. ... Scott ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Relay Access Denied Problem
    ... Now assuming that the friend's address is correct as Scott copied/pasted, the friend's domain "ceriin.net" is no longer a valid domain - it's not a "simple" DNS misconfiguration, the domain simply is not longer valid. ... provide the following diagnostic text to your system administrator. ... Sent by Microsoft Exchange Server 2007 ... Generating server: SDEXCH.magnecraft.com ...
    (microsoft.public.exchange.admin)