Can't rejoin computer to domain - AD Domain Controller could not be contacted

Bryan Glernon

Hi -
I have AD and DNS running on Win2k3 R2. There was a vista laptop
in the domain, and the laptop user changed the setup to a workgroup
when he was offsite. Now I can't get the laptop back into the domain.
I have tried removing the DNS and the Computer account records and
re-adding them manually as well as trying to join without the records
present. Running dcdiag and dcdiag /testNS on the server shows no
errors (other than some missing messages in the event log test.) I go
through the wizard on the laptop to change the network ID and join the
domain, give a valid domain admin name, and get a dialog saying that
an account for the computer could not be found and asking me for the
domain. I provide it (it's the same as the user domain) and then I get
the following error:

An Active Directory Domain Controller for the domain a.b.c could not
be contacted.

Ensure that the domain name is typed correctly.

If the name is correct, click Details for troubleshooting information.

Clicking Details gives:

+++++++++++

DNS was successfully queried for the service location (SRV) resource
record used to locate an Active Directory Domain Controller for domain
a.b.c:

The query was for the SRV record for
_ldap._tcp.dc._msdcs.a.b.c

The following AD DCs were identified by the query:

hera.a.b.c

Common causes of this error include:

- Host (A) records that map the name of the AD DCs to its IP addresses
are missing or contain incorrect addresses.

- Active Directory Domain Controllers registered in DNS are not
connected to the network or are not running.

For information about correcting this problem, click Help.

++++++++++++

I've verified that the host records are there, the IP's are correct,
and I can ping by both name and IP from the laptop. Nothing
interesting in any event logs.

I'm out of ideas. Any help will be appreciated.

Thanks,
Bryan

DanJ

Hi,

Have you tied this down to being a problem with only this machine? Have you
tried joining another machine to the domain? possibly with a different O/S
(WinXP).

This may be worth while before going any further.

Thanks
DanJ

MCSE 2003/2000

"Bryan Glernon" wrote:

> Hi -
> I have AD and DNS running on Win2k3 R2. There was a vista laptop
> in the domain, and the laptop user changed the setup to a workgroup
> when he was offsite. Now I can't get the laptop back into the domain.
> I have tried removing the DNS and the Computer account records and
> re-adding them manually as well as trying to join without the records
> present. Running dcdiag and dcdiag /testNS on the server shows no
> errors (other than some missing messages in the event log test.) I go
> through the wizard on the laptop to change the network ID and join the
> domain, give a valid domain admin name, and get a dialog saying that
> an account for the computer could not be found and asking me for the
> domain. I provide it (it's the same as the user domain) and then I get
> the following error:
>
> An Active Directory Domain Controller for the domain a.b.c could not
> be contacted.
>
> Ensure that the domain name is typed correctly.
>
> If the name is correct, click Details for troubleshooting information.
>
> Clicking Details gives:
>
> +++++++++++
>
> DNS was successfully queried for the service location (SRV) resource
> record used to locate an Active Directory Domain Controller for domain
> a.b.c:
>
> The query was for the SRV record for
> _ldap._tcp.dc._msdcs.a.b.c
>
> The following AD DCs were identified by the query:
>
> hera.a.b.c
>
> Common causes of this error include:
>
> - Host (A) records that map the name of the AD DCs to its IP addresses
> are missing or contain incorrect addresses.
>
> - Active Directory Domain Controllers registered in DNS are not
> connected to the network or are not running.
>
> For information about correcting this problem, click Help.
>
> ++++++++++++
>
> I've verified that the host records are there, the IP's are correct,
> and I can ping by both name and IP from the laptop. Nothing
> interesting in any event logs.
>
> I'm out of ideas. Any help will be appreciated.
>
> Thanks,
> Bryan
>

DanJ

Hi,

Have you tied this down to being a problem with only this machine? Have you
tried joining another machine to the domain? possibly with a different O/S
(WinXP).

This may be worth while before going any further.

Thanks
DanJ

MCSE 2003/2000

"Bryan Glernon" wrote:

> Hi -
> I have AD and DNS running on Win2k3 R2. There was a vista laptop
> in the domain, and the laptop user changed the setup to a workgroup
> when he was offsite. Now I can't get the laptop back into the domain.
> I have tried removing the DNS and the Computer account records and
> re-adding them manually as well as trying to join without the records
> present. Running dcdiag and dcdiag /testNS on the server shows no
> errors (other than some missing messages in the event log test.) I go
> through the wizard on the laptop to change the network ID and join the
> domain, give a valid domain admin name, and get a dialog saying that
> an account for the computer could not be found and asking me for the
> domain. I provide it (it's the same as the user domain) and then I get
> the following error:
>
> An Active Directory Domain Controller for the domain a.b.c could not
> be contacted.
>
> Ensure that the domain name is typed correctly.
>
> If the name is correct, click Details for troubleshooting information.
>
> Clicking Details gives:
>
> +++++++++++
>
> DNS was successfully queried for the service location (SRV) resource
> record used to locate an Active Directory Domain Controller for domain
> a.b.c:
>
> The query was for the SRV record for
> _ldap._tcp.dc._msdcs.a.b.c
>
> The following AD DCs were identified by the query:
>
> hera.a.b.c
>
> Common causes of this error include:
>
> - Host (A) records that map the name of the AD DCs to its IP addresses
> are missing or contain incorrect addresses.
>
> - Active Directory Domain Controllers registered in DNS are not
> connected to the network or are not running.
>
> For information about correcting this problem, click Help.
>
> ++++++++++++
>
> I've verified that the host records are there, the IP's are correct,
> and I can ping by both name and IP from the laptop. Nothing
> interesting in any event logs.
>
> I'm out of ideas. Any help will be appreciated.
>
> Thanks,
> Bryan
>

Herb Martin

"Bryan Glernon" <bryan@newsgroups.nospam> wrote in message
news:0v52a3d4egce5rflq6bjkr919ur2icvjur@4ax.com...
> Hi -
> I have AD and DNS running on Win2k3 R2. There was a vista laptop
> in the domain, and the laptop user changed the setup to a workgroup
> when he was offsite. Now I can't get the laptop back into the domain.
> I have tried removing the DNS and the Computer account records and
> re-adding them manually as well as trying to join without the records
> present. Running dcdiag and dcdiag /testNS on the server shows no
> errors (other than some missing messages in the event log test.) I go
> through the wizard on the laptop to change the network ID and join the
> domain, give a valid domain admin name, and get a dialog saying that
> an account for the computer could not be found and asking me for the
> domain. I provide it (it's the same as the user domain) and then I get
> the following error:
>
> An Active Directory Domain Controller for the domain a.b.c could not
> be contacted.
>
> Ensure that the domain name is typed correctly.
>
> If the name is correct, click Details for troubleshooting information.
>
> Clicking Details gives:

Check DNS on the client, and RESET the Computer Account on the domain.
(Right click in ADUC.)

Herb Martin

"Bryan Glernon" <bryan@newsgroups.nospam> wrote in message
news:0v52a3d4egce5rflq6bjkr919ur2icvjur@4ax.com...
> Hi -
> I have AD and DNS running on Win2k3 R2. There was a vista laptop
> in the domain, and the laptop user changed the setup to a workgroup
> when he was offsite. Now I can't get the laptop back into the domain.
> I have tried removing the DNS and the Computer account records and
> re-adding them manually as well as trying to join without the records
> present. Running dcdiag and dcdiag /testNS on the server shows no
> errors (other than some missing messages in the event log test.) I go
> through the wizard on the laptop to change the network ID and join the
> domain, give a valid domain admin name, and get a dialog saying that
> an account for the computer could not be found and asking me for the
> domain. I provide it (it's the same as the user domain) and then I get
> the following error:
>
> An Active Directory Domain Controller for the domain a.b.c could not
> be contacted.
>
> Ensure that the domain name is typed correctly.
>
> If the name is correct, click Details for troubleshooting information.
>
> Clicking Details gives:

Check DNS on the client, and RESET the Computer Account on the domain.
(Right click in ADUC.)

ckpilling

Hi Bryan,

From your problem description the next thing I'd try is changing the PC name
of the laptop and going through the domain wizard again.

How was laptop originally joined to the domain?

If that doesn't work the next thing I'd try is running newsid on the laptop.

Is there any Vista/3rd party firewall on the laptop blocking the traffic?

Plese let me know if any of the above works

Regards

Chris

"Herb Martin" wrote:

>
> "Bryan Glernon" <bryan@newsgroups.nospam> wrote in message
> news:0v52a3d4egce5rflq6bjkr919ur2icvjur@4ax.com...
> > Hi -
> > I have AD and DNS running on Win2k3 R2. There was a vista laptop
> > in the domain, and the laptop user changed the setup to a workgroup
> > when he was offsite. Now I can't get the laptop back into the domain.
> > I have tried removing the DNS and the Computer account records and
> > re-adding them manually as well as trying to join without the records
> > present. Running dcdiag and dcdiag /testNS on the server shows no
> > errors (other than some missing messages in the event log test.) I go
> > through the wizard on the laptop to change the network ID and join the
> > domain, give a valid domain admin name, and get a dialog saying that
> > an account for the computer could not be found and asking me for the
> > domain. I provide it (it's the same as the user domain) and then I get
> > the following error:
> >
> > An Active Directory Domain Controller for the domain a.b.c could not
> > be contacted.
> >
> > Ensure that the domain name is typed correctly.
> >
> > If the name is correct, click Details for troubleshooting information.
> >
> > Clicking Details gives:
>
> Check DNS on the client, and RESET the Computer Account on the domain.
> (Right click in ADUC.)
>
>
>

ckpilling

Hi Bryan,

From your problem description the next thing I'd try is changing the PC name
of the laptop and going through the domain wizard again.

How was laptop originally joined to the domain?

If that doesn't work the next thing I'd try is running newsid on the laptop.

Is there any Vista/3rd party firewall on the laptop blocking the traffic?

Plese let me know if any of the above works

Regards

Chris

"Herb Martin" wrote:

>
> "Bryan Glernon" <bryan@newsgroups.nospam> wrote in message
> news:0v52a3d4egce5rflq6bjkr919ur2icvjur@4ax.com...
> > Hi -
> > I have AD and DNS running on Win2k3 R2. There was a vista laptop
> > in the domain, and the laptop user changed the setup to a workgroup
> > when he was offsite. Now I can't get the laptop back into the domain.
> > I have tried removing the DNS and the Computer account records and
> > re-adding them manually as well as trying to join without the records
> > present. Running dcdiag and dcdiag /testNS on the server shows no
> > errors (other than some missing messages in the event log test.) I go
> > through the wizard on the laptop to change the network ID and join the
> > domain, give a valid domain admin name, and get a dialog saying that
> > an account for the computer could not be found and asking me for the
> > domain. I provide it (it's the same as the user domain) and then I get
> > the following error:
> >
> > An Active Directory Domain Controller for the domain a.b.c could not
> > be contacted.
> >
> > Ensure that the domain name is typed correctly.
> >
> > If the name is correct, click Details for troubleshooting information.
> >
> > Clicking Details gives:
>
> Check DNS on the client, and RESET the Computer Account on the domain.
> (Right click in ADUC.)
>
>
>