Domain controller for the domain XXX could not be contacted

  • Thread starter Thread starter Scott
  • Start date Start date
S

Scott

Guest
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?
 
Re: Domain controller for the domain XXX could not be contacted

I forgot to mention that I can ping the PDC from PC1 and can even remote to
the PDC using Remote Desktop Connection.


"Scott" <sbailey@mileslumber.com> wrote in message
news:eeMKmXswIHA.516@TK2MSFTNGP04.phx.gbl...
>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?
>
 
Re: Domain controller for the domain XXX could not be contacted

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?
>
 
Re: Domain controller for the domain XXX could not be contacted

All ip and DNS info were setup.

"Dave Patrick" <DSPatrick@nospam.gmail.com> wrote in message
news:e3scQ8swIHA.524@TK2MSFTNGP05.phx.gbl...
> 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?
>>
>
 
Re: Domain controller for the domain XXX could not be contacted

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@nospam.gmail.com> wrote in message
> news:e3scQ8swIHA.524@TK2MSFTNGP05.phx.gbl...
> > 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?
> >>
> >
>
>
>
 
Back
Top