Attempting to join a new MS 2008 Server to domain - ultimately to replacd pdc.
Present PDC is a Windows 2000 Server.
1. When attempting to join MS 2008 to domain, get the following message:
"an attempt to resolve DNS name of the DC in the domain being joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain."
2. Ipconfig shows MS 2008 to be in same address pool as server.
3. I have configured the system both dynamically and with a static IP with preferred DNS address pointing to the MS 2000 server (192.168.7.30).
4. I believe the problem is in the DNS setup on MS 2000 server but not sure how to resolve.
Please note the following:
DNS Forward Look Zone
Domain is Office.com
Start of authority abs1.absusa.net, admin.absusa.net
Name server abs1.absusa.net
MS 2000 Server full computer name is abs1.absusa.net
Domain is Office1.com
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Not yet, I planned to to that next after joining the server to the domain.
My intention is join the server, then copy data to the new server and test applications. Once this is completed and OK, then I plan to run adprep.
Do I have to run adprep first to join the system to my domain? Is this my problem?
Another comment to make clear of what I am trying to accomplish.
1. I want to join the new MS 2008 server to the domain as a member server for the purpose of copying files and testing applications.
2. When the testing is finished, then I plan to run adprep and dcpromo to make the new MS 2008 server the pdc.
3. My problem at this time is that I cannot join the MS 2008 server to the domain (please note original question and information).
Is the IP allocated to the server via DHCP or is it set with a static IP?
run ipconfig /all | more on the windows 2008 or get detail information for the local area connection.
Items of interest are the DNS/name server records reflected there in. Is it displaying the 192.168.7.30 IP or is it displaying an ISP providers DNS server? This is likely the cause for the DNS error you are receiving.
The other item on which wantabe2 handled, you must use the adprep to update the win2k AD Schema to include the win2k8 additions.
Once you fix the DNS issue, you will get the warning the AD needs to be updated for the addition of the win2k8 system.
It is not possible to have a computer name as abs1.absusa.net while at the same time having the AD domain name as office1.com.
The computer name under the properties of my computer should reflect the AD domain on which it is located i.e. abs1.office1.com. your external DNS for absusa.net and host abs1.absusa.com can point to the same IP.
The majority of your problem is that you are using a public suffix .com for your AD domain name which often causes problem. MS suggested AD convention is to use .private .local for AD.
I have used both a static IP and dynamic, and in both instances the correct addresses were in the IP, subnet and gateway. At the moment, I have reset the IP to static, which is as follows:
IP 192.168.7.35
Sub 255.255.255.0
GW 192.168.7.1
DNS 192.168.7.30
I have not run adprep yet, because it is my intention to bring the new MS 2008 server into the domain as a member server first. I have a lot of copying and application testing that I want to do first. However, if it is possible to run adprep to solve this problem and still keep the old server as the pdc for a time, I am willing to give that a try. I just need assurance that running adprep will not affect the pdc role of the old server until I am ready to complete the move.
I understand what you are saying about the names, and not being the one that set up this 2000 server, I really have no explanation of why the server and domain are named the way they are. In any case the situation is thus, the old server computer name is abs1.absusa.net and the domain is office1.com. Again, it doesn't make sense to me that they were named this way, but the domain has been in use for nearly 10 years. In fact, I added an new workstation to the domain about two weeks ago - everything went normally.
The adprep just ads the necessary schema entries to the AD and might be required to add the win2k8 as a member server. Like any changes to any OS/AD make sure to have a backup performed prior to making any alterations.
Could you check as another posted, Mikealcl, the DNS record to see whether it is really using office1.com or absusa.net as the AD domain name. Look within the office1.com forward zone for the _msdcs records.
Do you have an office1.com forward zone that has _ldap, _msdcs entries?
When you login into any of the system, what is the displayed domain? office1 or absusa? Check the sites and trusts interface to make sure you do not have a trust setup to absusa or office1 and that might be the issue.
The only DNS entries are shown below. There is no _idap_msdcs entry. I suspect this is because this is Server 2000 and ..._msdcs was added with MS Server 2003, although I am not certain. However, I did delete the domain and recreated it and the same listing that is shown below were created. Again, when I joined an XP workstaiton last week, I used Office1 as the domain. Also, please note that when I attempt to join the MS Server 2008 and put in the domain name Office1, the system responds asking for credentials of login name and password for Office1. It then attempts the join and then returns the error message shown in my first post. The error message says to be sure the system (MS 2008 server) is configured to reach the DNS server. Based on this, it seems that the problem is with the 2008 server configuration, but I am not an expert.
DNS Forward Look Zone
Domain is Office.com
Start of authority abs1.absusa.net, admin.absusa.net
Name server abs1.absusa.net
Hi!
_msdcs was not added in W2K3. SRV resource records were first used to locate domain controllers in Windows 2000.
You should configure your forward lookup zone to accept dynamic updates and the register proper A and SRV records.
To register domain controller's A record run "ipconfig /registerdns" from command prompt.
To register SRV records in DNS either restart Netlogon in Services snap-in (services.msc) or go to command prompt run these two commands:
"net stop netlogon"
"net start netlogon"
Now go to W2K8 server's command prompt and run the following commands:
"ipconfig /flushdns" <-- this will clear W2K8 server's client resolver cache
"nslookup abs1.absusa.net" <-- it should return W2K server's IP
"ping IP" <-- where IP is returned from nslookup
If name resolves to correct IP and you can access your server, you should be able to access DC to join computer to domain.
HTH
Toni
I just ran the commands as you instructed - ipconfig /registerdns, net stop netlogon and net start netlogon. I then went to new server and ran ipconfig /flushdns. When I ran nslookup abs1.absusa.net, the system returned the IP of 192.168.7.30. I ran ping on the IP and received 4 replies.
I then went to the system to join it to the domain. Again, it recognized the domain, asked for the logon name and password which I suppled, then gave the same error message as before.
It's missing the SRV records.
Create the following Forward Lookup Zone. Make it a Primary then Active Directory Integrated.
_msdcs.adsusa.net
A problem I see is this: your AD namespace is absusa.net but you say your domain (or server's DNS suffix?) is office1.com. I'm really not sure what you're attempting to do, but the AD Namespace should not at all be confused with a registered internet domain name.
You need to clarify all that and let us know.
Netman66, I refer you to my past posts. As stated there, the computer name of the server is abs1.absusa.net and the domain name is office1.com. I don't know why it was done that way 8 years ago, but it has been in place that long and workstations have been joined to the domain without problem over those years, including one just two weeks ago.
this is result of ipconfig /all
C:\WINNT\Profiles\Administ
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : abs1
Primary DNS Suffix . . . . . . . : absusa.net
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : absusa.net
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : absusa.net
Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet Adapt
er (10/100)
Physical Address. . . . . . . . . : 00-04-AC-96-E3-1F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.7.30
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.7.1
DNS Servers . . . . . . . . . . . : 192.168.7.30
Primary WINS Server . . . . . . . : 192.168.7.30
C:\WINNT\Profiles\Administ
Create a new Forward Lookup Zone called:
_msdcs.absuas.net
Make it a Primary Zone. When asked, make it Active Directory Integrated and accept Secure Dynamic Updates only.
Once this is done, restart the Netlogon service on the server. Post the results of the DNS zones now.
You also should check the Properties of the ABS1 in the DNS snap-in to determine and make sure that the service is listening (servicing) the Internal NIC.
Let us know.
The asker of course. He posted that he deleted a zone and recreated it.
mdwhiteside,
could you open the Active directories user and computers? What is the domain listed there?
Second open the active directory sites and trusts and see whether you have any trust relationship there.
Is this setup a migration from an NT domain?
Could you also post the systeminfo run on any existing member server? The item of interest is the Domain: entry.
I created a new forward lookup zone according to your directions, stopped and restarted netlogon, then tried to join the server to the domain again - same error. I noticed, however, that you said to create the forward zone as _msdcs.absusa.net, but the domain name is office1.com. So I decided to create a new forward zone of _msdcs.office1.com. Again still had the same error when trying to join the domain. I wonder if the fact that I now have two entries of _msdcs.xxx is an issue. I've decided to not add/change until I hear from you again.
As requested, I went to Active Directory and the domain name listed there is office1.com. There are not any trusts set up in Domains and Trusts.
The DNS now looks like this:
DNS
ABS1
Forward Lookup Zones
_msdcs.absusa.net
_msdcs.office1.com
Office 1.com _msdcs
_msdcs SOA [8], abs1.absusa.net, administrator.office1.com
NS abs1.absusa.net
NS abs1.office1.com
A 192.168.7.30
having three _msdcs.someotherdomain.com
It seems you have access to a system remotely, please run systeminfo /s \\[memberserver_name] | more
What is the domain listed on the line starting with Domain:?
The other issue you might have is what is the forest/domain level of the existing AD?
Mixed, 2000?
Unfortunately, you keep posting the same information focused on the DNS rather than addressing the matter to clearly identify the AD domain name.
how about you try joining the windows 2008 server into the absusa.net domain and see whether you have a different response/error.
In your initial post, you have both office.com and office1.com and absusa.net absusa.net all three domains are existing public domains.
The system info you requested is listed below. I've tried to be clear about the domain name and will try one more time.
The domain name is office1.com - not office1.net, not absusa.net.
www.absusa.net is a domain name for the company's website.
the server computer name is abs1.absusa.net - I don't know why, but someone did it this way long ago.
The AD domain name is office1.com
The DNS domain name is office1.com
If I try to join the 2008 server to any other domain name other than Office1, I get an invalid response.
When I try to join the 2008 to Office1, the system responds by asking for the account name and password to join the system to the domain office1.
I supply the login administrator and password, I get an hour glass, then the error.
Item Value
OS Name Microsoft Windows 2000 Server
Version 5.0.2195 Service Pack 4 Build 2195
OS Manufacturer Microsoft Corporation
System Name ABS1
System Manufacturer IBM
System Model 865512Y
System Type X86-based PC
Processor x86 Family 6 Model 7 Stepping 3 GenuineIntel ~499 Mhz
Processor x86 Family 6 Model 7 Stepping 3 GenuineIntel ~499 Mhz
BIOS Version IBM BIOS Ver PKKT11.0
Windows Directory C:\WINNT
System Directory C:\WINNT\system32
Boot Device \Device\Harddisk0\Partitio
Locale United States
User Name OFFICE1\administrator
Time Zone Central Daylight Time
Total Physical Memory 1,048,096 KB
Available Physical Memory 333,512 KB
Total Virtual Memory 3,568,720 KB
Available Virtual Memory 2,182,228 KB
Page File Space 2,520,624 KB
Page File D:\pagefile.sys
What is the domain and forest operational level?
try this, go into the active directory users and computers and in the computer add the windows 2008 computer account (new computer account from the tasks).
Then try again to see whether you will get a message that an account by this name already exists and whether you want to use it or create a new one.
When was the last time you added any members to the AD?
I am not sure what to suggest.
Try when joining the domain to only specify office1 and see how much further you'll get.
You seem to have a space in your domain name "office 1.com" rather than office1.com.
This is based on the data you posted for what the domain has in your prior two comments.
Make sure that the IPv6 protocol under the network connection on the win2k8 is not checked. See if that helps.
Business Accounts
Answer for Membership
by: wantabe2Posted on 2009-10-23 at 12:09:00ID: 25647359
Did you prepare your domain for the new Win 2008 domain contoller with forest prep?
http://technet.microsoft.c
http://technet.microsoft.c