Active Directory DNS issue

Sorry for this message to be kind of extensive but it requires some
background on my problem.



We have a customer who has their main office in Orlando, FL, and another
office in Ft. Lauderdale, FL. Both offices have a Win2003 server. The
Orlando office server is the primary domain controller, and the Ft.
Lauderdale office server is another domain controller in the domain.

A few weeks ago the Ft. Lauderdale server crashed. They sent it to us in
Orland and we replaced the necessary hardware and re-loaded it. We then sent
it back down to Ft. Lauderdale. I then remote-desktop into the Ft.
Lauderdale server to install Active Directory and join it to the domain.
It won't seem to join the domain. The error message I get is below. It
appears to be a DNS issue. The domain name is "esciences". Orlando server
name is "serverorl". Ft. Lauderdale server name is "serverftl". Both
servers can ping each other by name as well as IP address. (and yes, the
primary DNS of the Ft. Lauderdale server is the IP address of the Orlando
server).



------- Error Message ---------

The domain name esciences might be a NetBIOS domain name. If this is the
case, verify that the domain name is properly registered with WINS.



If you are certain that the name is not a NetBIOS domain name, then the
following information can help you troubleshoot your DNS configuration.



DNS was successfully queried for the service location (SRV) resource record
used to locate a domain controller for domain esciences:



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



The following domain controllers were identified by the query:



serverftl.esciences

serverorl.esciences



Common causes of this error include:



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



- Domain controllers registered in DNS are not connected to the network or
are not running.

------- End Error Message ---------



I'm thinking that this has something to do with the fact the the serverftl
Server was abruptly removed from the domain but the serverorl domain
controller still has DNS entries for it. Any help would be GREATLY
appreciated.

Any errors of using dcdiag and nslookup? Or posting the result of ipconfig /all here may help.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Mark" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
Sorry for this message to be kind of extensive but it requires some
background on my problem.



We have a customer who has their main office in Orlando, FL, and another
office in Ft. Lauderdale, FL. Both offices have a Win2003 server. The
Orlando office server is the primary domain controller, and the Ft.
Lauderdale office server is another domain controller in the domain.

A few weeks ago the Ft. Lauderdale server crashed. They sent it to us in
Orland and we replaced the necessary hardware and re-loaded it. We then sent
it back down to Ft. Lauderdale. I then remote-desktop into the Ft.
Lauderdale server to install Active Directory and join it to the domain.
It won't seem to join the domain. The error message I get is below. It
appears to be a DNS issue. The domain name is "esciences". Orlando server
name is "serverorl". Ft. Lauderdale server name is "serverftl". Both
servers can ping each other by name as well as IP address. (and yes, the
primary DNS of the Ft. Lauderdale server is the IP address of the Orlando
server).



------- Error Message ---------

The domain name esciences might be a NetBIOS domain name. If this is the
case, verify that the domain name is properly registered with WINS.



If you are certain that the name is not a NetBIOS domain name, then the
following information can help you troubleshoot your DNS configuration.



DNS was successfully queried for the service location (SRV) resource record
used to locate a domain controller for domain esciences:



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



The following domain controllers were identified by the query:



serverftl.esciences

serverorl.esciences



Common causes of this error include:



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



- Domain controllers registered in DNS are not connected to the network or
are not running.

------- End Error Message ---------



I'm thinking that this has something to do with the fact the the serverftl
Server was abruptly removed from the domain but the serverorl domain
controller still has DNS entries for it. Any help would be GREATLY
appreciated.

Mark wrote:
> Sorry for this message to be kind of extensive but it requires some
> background on my problem.
>
>
>
> We have a customer who has their main office in Orlando, FL, and
> another office in Ft. Lauderdale, FL. Both offices have a Win2003
> server. The Orlando office server is the primary domain controller,
> and the Ft. Lauderdale office server is another domain controller in
> the domain.
>
> A few weeks ago the Ft. Lauderdale server crashed. They sent it to
> us in Orland and we replaced the necessary hardware and re-loaded it.
> We then sent it back down to Ft. Lauderdale. I then remote-desktop
> into the Ft. Lauderdale server to install Active Directory and join
> it to the domain. It won't seem to join the domain. The error
> message I get is below. It appears to be a DNS issue. The domain
> name is "esciences". Orlando server name is "serverorl". Ft.
> Lauderdale server name is "serverftl". Both servers can ping each
> other by name as well as IP address. (and yes, the primary DNS of the
> Ft. Lauderdale server is the IP address of the Orlando server).
>
>
>
> ------- Error Message ---------
>
> The domain name esciences might be a NetBIOS domain name. If this is
> the case, verify that the domain name is properly registered with
> WINS.
>
> If you are certain that the name is not a NetBIOS domain name, then
> the following information can help you troubleshoot your DNS
> configuration.
>
> DNS was successfully queried for the service location (SRV) resource
> record used to locate a domain controller for domain esciences:
>
> The query was for the SRV record for _ldap._tcp.dc._msdcs.esciences
>
> The following domain controllers were identified by the query:
> serverftl.esciences
>
> serverorl.esciences

The issue you are having is caused by using a single-label Active Directory
DNS Domain name. This is going to require registry entries on all Domain
members and Domain Controllers running Win2kSP4, XP, and Win2k3.

300684 - Information About Configuring Windows 2000 for Domains with
Single-Label DNS Names
http://support.microsoft.com/default...300684&sd=RMVP


--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

Kevin is right. And you will also need to do a metadata cleanup to remove
the old server from AD:
http://support.microsoft.com/?kbid=216498

--
Regards,
Andrei Ungureanu
www.eventid.net
Test our new EventReader!
http://www.altairtech.ca/eventreader...lt2.asp?ref=au

"Kevin D. Goodknecht Sr. [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Mark wrote:
>> Sorry for this message to be kind of extensive but it requires some
>> background on my problem.
>>
>>
>>
>> We have a customer who has their main office in Orlando, FL, and
>> another office in Ft. Lauderdale, FL. Both offices have a Win2003
>> server. The Orlando office server is the primary domain controller,
>> and the Ft. Lauderdale office server is another domain controller in
>> the domain.
>>
>> A few weeks ago the Ft. Lauderdale server crashed. They sent it to
>> us in Orland and we replaced the necessary hardware and re-loaded it.
>> We then sent it back down to Ft. Lauderdale. I then remote-desktop
>> into the Ft. Lauderdale server to install Active Directory and join
>> it to the domain. It won't seem to join the domain. The error
>> message I get is below. It appears to be a DNS issue. The domain
>> name is "esciences". Orlando server name is "serverorl". Ft.
>> Lauderdale server name is "serverftl". Both servers can ping each
>> other by name as well as IP address. (and yes, the primary DNS of the
>> Ft. Lauderdale server is the IP address of the Orlando server).
>>
>>
>>
>> ------- Error Message ---------
>>
>> The domain name esciences might be a NetBIOS domain name. If this is
>> the case, verify that the domain name is properly registered with
>> WINS.
>>
>> If you are certain that the name is not a NetBIOS domain name, then
>> the following information can help you troubleshoot your DNS
>> configuration.
>>
>> DNS was successfully queried for the service location (SRV) resource
>> record used to locate a domain controller for domain esciences:
>>
>> The query was for the SRV record for _ldap._tcp.dc._msdcs.esciences
>>
>> The following domain controllers were identified by the query:
>> serverftl.esciences
>>
>> serverorl.esciences
>
> The issue you are having is caused by using a single-label Active
> Directory
> DNS Domain name. This is going to require registry entries on all Domain
> members and Domain Controllers running Win2kSP4, XP, and Win2k3.
>
> 300684 - Information About Configuring Windows 2000 for Domains with
> Single-Label DNS Names
> http://support.microsoft.com/default...300684&sd=RMVP
>
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> http://message.wftx.us/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
> ===================================
>
>

Andrei Ungureanu [MVP] wrote:
> Kevin is right. And you will also need to do a metadata cleanup to
> remove the old server from AD:
> http://support.microsoft.com/?kbid=216498

I totally missed the part that Mark was trying to promote this as a DC, if
that is the case, this would be a perfect time to promote it with a proper
DNS name, set up trust and use ADMT, to migrated all accounts into the newly
named domain. After which time the other DC can be demoted, and repromoted
into the new domain.

--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================