New Server problem with AD

  • Thread starter Thread starter John H
  • Start date Start date
J

John H

Just adding a new server to domain and when using the AD
wizard while adding server as 'Additional domain
controller for existing domain' get the following error
message after it has found domain 'The operation failed
because : Failed to find a suitabled domain controller for
the domain. The specified domain either does not exist or
could not be contacted.'
Everything else is fine, server is seen by DC and can see
DC and everyone else.

Please help.
 
John,

Is the new server pointing to the internal DNS Server ( probably one of the
existing DCs )? This would be in the TCP/IP settings. If it is not ( or,
worse, pointing to the ISP's DNS Server ) go ahead and add it / change it.

Does this help you?

Cary
 
| John,
|
| Is the new server pointing to the internal DNS Server ( probably one of
the
| existing DCs )? This would be in the TCP/IP settings. If it is not ( or,
| worse, pointing to the ISP's DNS Server ) go ahead and add it / change it.
|
| Does this help you?
|
| Cary
|
| | > Just adding a new server to domain and when using the AD
| > wizard while adding server as 'Additional domain
| > controller for existing domain' get the following error
| > message after it has found domain 'The operation failed
| > because : Failed to find a suitabled domain controller for
| > the domain. The specified domain either does not exist or
| > could not be contacted.'
| > Everything else is fine, server is seen by DC and can see
| > DC and everyone else.
| >
| > Please help.
|
|
|

To follow up with Cary, you need to make sure both DC's are only pointing
to the internal DNS server. They should never point to the ISP's DNS
server. The ISP's DNS needs to be added as a forwarder. Once they are both
pointing to the internal DNS server, make sure the first DC is registering
its SRV record. You will find this in DNS under the forward lookup zone.
Expand the domain and under it will be an _MCDSC folder. In there you will
find the SRV records for all DC's in the domain. This is what the newly
promoted DC will be looking for in order to locate another DC to replicate
with.

Chad A. Lacy
Windows 2000 Directory Services

==================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
-----Original Message-----
| John,
|
| Is the new server pointing to the internal DNS Server ( probably one of
the
| existing DCs )? This would be in the TCP/IP settings. If it is not ( or,
| worse, pointing to the ISP's DNS Server ) go ahead and add it / change it.
|
| Does this help you?
|
| Cary
|
| | > Just adding a new server to domain and when using the AD
| > wizard while adding server as 'Additional domain
| > controller for existing domain' get the following error
| > message after it has found domain 'The operation failed
| > because : Failed to find a suitabled domain controller for
| > the domain. The specified domain either does not exist or
| > could not be contacted.'
| > Everything else is fine, server is seen by DC and can see
| > DC and everyone else.
| >
| > Please help.
|
|
|

To follow up with Cary, you need to make sure both DC's are only pointing
to the internal DNS server. They should never point to the ISP's DNS
server. The ISP's DNS needs to be added as a forwarder. Once they are both
pointing to the internal DNS server, make sure the first DC is registering
its SRV record. You will find this in DNS under the forward lookup zone.
Expand the domain and under it will be an _MCDSC folder. In there you will
find the SRV records for all DC's in the domain. This is what the newly
promoted DC will be looking for in order to locate another DC to replicate
with.

Chad A. Lacy
Windows 2000 Directory Services

==================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================
This posting is provided "AS IS" with no warranties, and confers no rights.

.
Click to expand...

Chad

Thanks for the help.
The new DC was pointing at the internal DNS but the old DC
was pointing to the ISP DNS in networking and forwarders,
once I changed it as you suggested it worked like a charm.

Thanks again

John Headley
 
Back
Top