Question about Computers & Internet

2 Answers

I am attempting to join a 2008 server as a member in a 2003 domain. I keep getting the following error: An attemt to solve the DNS of a DC has failed. Please verify that this client is configured to reach a DNS server that can resolve DNS name in Target Domain. It ask for my user name and password but will not join.

Posted by on

  • 2 more comments 
  • George Maeweather May 07, 2010

    I need to join a 2008 standard server to a 2003 standard server domain

  • George Maeweather May 07, 2010

    I agree with what you are saying and I give it a try could also send me another solution I can try just in case it is not the problem.

  • George Maeweather May 07, 2010

    I will try it today. I have to go in in about an hour or so, you said, you had another solution also. Could you send it to be and I van have it just in case the other one doesn't work I can try it at the same time.

  • George Maeweather May 09, 2010

    Hello Mark,



    I tried both of your solutions and neither worked. What about the 2008 standard server.

×

Ad

2 Answers

  • Level 3:

    An expert who has achieved level 3 by getting 1000 points

    All-Star:

    An expert that got 10 achievements.

    MVP:

    An expert that got 5 achievements.

    Vice President:

    An expert whose answer got voted for 100 times.

  • Master
  • 728 Answers

Hi,

There can be many things that can create that error, the one that is the most common is that your network adapter is not assigned to that DNS. Here's what you do to override that. Go to your network connections, and right click on the Local Area Connection icon and choose Properties. From there, you will click on the TCP IP in the list of items and click the properties button. From inside the properties , it can go either two ways, It's set to get an IP address automatically, or it's been assigned all the IP and DNS configurations. If it's set to automatic, then change it to assign these numbers. You will need to locate all these numbers, which I'll walk you through.

First, click on your Start then run button, and enter cmd and hit enter. Or get to the Command prompt anyway you know how. Once you get a black box with a command prompt type in "ipconfig /all" (without the parentheses) it will list for you what the machines IP address is, it's Subnet Mask, Default Gateway, and your DNS Servers. Write them down.

Now go to your Windows 2008 server, and do the same thing with the ipconfig, and compare to make sure that the numbers on the DNS Servers are the same.
If not, there is your problem. Go back to the desktop, and continue to fill in the number that you previously wrote, and fill the IP address of that machine, the Subnet Mask will usually fill in automatically, but if not enter it, then the default gateway. In the DNS section, enter the DNS that match's with the Servers DNS number. Click on Ok, and give it another try to connect to the server.

Let me know if this didn't work, and I'll walk you through another solution that it could be.

Good Luck, And let me know.

Thanks
Mark

Posted on May 07, 2010

  • Mark Taylor
    Mark Taylor May 07, 2010

    Hi,



    Ok, the second solution is more of a research to help determine what the DNS is pointing to and clearing the DNS from the Workstation. Here are the steps:



    1) Click Start, Run, Enter cmd and get to the command prompt.

    2) Use the command ipconfig /displaydns to view the DNS resolver cache. It will display all the DNS for that machine. If you don't see the same number that the server has, then your dns might just be corrupted. You can flush the dns out, and start with a new file.

    3) To flush the dns enter ipconfig /flushdns. Then run the ipconfig /displaydns to make sure it's flushed.

    4) If you set the DNS numbers up from the first solution, then your network adapter or Local Area connection will set the new DNS up to those numbers.



    This should get you into connecting to the server.



    If not, let me know, then we will have to look at the Server 2008 for certain issues that could be stopping the connection. But, I think you should be ok. Please let me know.



    Thanks Mark

  • Mark Taylor
    Mark Taylor May 09, 2010

    Do me a favor and run the cmd prompt ipconfig /all and post it here, for the workstation and the server, so I can see what that the DNS is registering.



    Thanks

    Mark

×

Ad
  • Level 3:

    An expert who has achieved level 3 by getting 1000 points

    Superstar:

    An expert that got 20 achievements.

    All-Star:

    An expert that got 10 achievements.

    MVP:

    An expert that got 5 achievements.

  • Master
  • 2,427 Answers

Thats cause the 2008 server and 2003 cannot handshake,,, microsoft changed the protocol in windows vista / win 7 / 20008,,,,,

read this article it will explain what i am saying

http://chicagotech.net/netforums/viewtopic.php?t=5075


basically 2008 doesnt support,, 2003, or XP ,, only vista and higher,, I'm sure you have noticed that win 7 dont have workgroups and domains in its network infastructure any more,, only home groups..

Posted on May 07, 2010

Ad

1 Suggested Answer

6ya6ya
  • 2 Answers

SOURCE: I have freestanding Series 8 dishwasher. Lately during the filling cycle water hammer is occurring. How can this be resolved

Hi,
a 6ya expert can help you resolve that issue over the phone in a minute or two.
Best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
the service is completely free and covers almost anything you can think of.(from cars to computers, handyman, and even drones)
click here to download the app (for users in the US for now) and get all the help you need.
Goodluck!

Posted on Jan 02, 2017

Add Your Answer

Uploading: 0%

my-video-file.mp4

Complete. Click "Add" to insert your video. Add

×

Loading...
Loading...

Related Questions:

Tip

Server 2003 & client configuration


<p><span>Some days before I have done a job on Windows Server 2003 Enterprise edition & Client XP. It is departmental food court. In the office room of the restaurant have a system which will be Server system and main domain. There was another 8 system in every department of food <span> </span>with printer for billing.I</SPAN><br> <p><span>Windows Server 2003 includes a mission critical Windows Server operating system, such as security, reliability, availability, and scalability.</SPAN><br> <p><span>You have to install DNS server for DC without DNS the client computers wouldn't know which one is DC.You can host DNS on a different server than DC.</SPAN><br> <p><span>Before Starting the DC installation process you need to make sure the <span> </SPAN>following points</SPAN><br> <p><span> </SPAN><br> <p><span>1)You have installed Basic windows server 2003 installation</SPAN><br> <p><span>2)Make sure you have assigned a static ip address to your server</SPAN><br> <p><span><span> </SPAN>Now start DC and DNS Setup process</SPAN><span></SPAN><br> <a><span> </SPAN></A> <span><span>Domain Controller</SPAN></SPAN><span></SPAN> <span>Active Directory is a huge topic in itself. While DCPROMO is easy to run, planning of both the physical and the logical structure is the key to a trouble free active directory. </SPAN> <p><span>Domain controllers do not have to be your most powerful machines, however they must be reliable and always available to answer logon requests. </SPAN><br> <a><span>DNS (Domain Name System)</SPAN></A><span><span> </SPAN></SPAN><span>Role</SPAN> <p><span>Once DNS is setup, it runs itself thanks to the new dynamic component hence DDNS. TCP/IP knowledge plus understanding of how DNS works is essential when troubleshooting connectivity problems.</SPAN><br> <p><span>DNS enables client machines to resolve servers IP addresses. Once the client finds the server, Active Directory uses LDAP to locate services like Kerberos, Global Catalog that clients request.</SPAN><br> <a><span>Print Server Role</SPAN></A><span></SPAN> <p><span>In my experience there is a contrast between the software settings which are easy to configure and the hardware which constantly need for attention e.g. paper jam, 'out of toner'. Check list for print server:</SPAN><br> <p><span></SPAN> <br> <p><span>Printer Priority</SPAN><br> <p><span>Network Printers</SPAN><br> <p><span></SPAN><br> <p><b><span>Client Configuration :- </SPAN></B><span>After</SPAN><span><span> Installation of Windows Xp give the IP Add on TCP/IP of IPV4.If you want to manually configure DNS server addresses, click</SPAN></SPAN><span><span> </SPAN></SPAN><b><span>Use the following DNS server addresses</SPAN></b><span><b><span>,</SPAN></B></SPAN><span><span> and then type the preferred DNS server and alternate DNS server IP addresses in the</SPAN></SPAN><span><span> </SPAN></SPAN><b><span>Preferred DNS server</SPAN></b><span><span> </SPAN></SPAN><span><span>and</SPAN></SPAN><span><span> </SPAN></SPAN><b><span>Alternate DNS server</SPAN></b><span><span> </SPAN></SPAN><span><span>boxes. After all job try to ping each other. I'm trying this and it also pinging. Files and data also can be shared through it.</SPAN></SPAN>

on Feb 15, 2011 | Computers & Internet

1 Answer

Thank you for the last one. know i want to set up mu 3laptops on the windows server 2008 r2 standered and use the server as a domain and the laptops as well like a domain.


first you need to setup the roles in the server, go to the manage server console, ( can be found as a shortcut in the taskbar or under start menu ) then open the console and go to add roles.

1 - add active directory

2 - in the process it will ask you to install the DNS server role ( do it )

3 - after installing the role in the CMD command prompt type DCPROMO

4 - the DC controller installation and setup will beging ( do not do anything during this proccess )

5 - when asked by DC setup to choose what type of domain functionality level do the following

1 - windows 2003 ( this is for compatibility for windows server running 2003 and XP machines )

2 - Windows Server 2008 ( at this point nothing lower than XP can be added to the DC of course domain functionalities will increase - Only other 2008 server domain controller can be added and cluster migration from server 2003 to 2008 is not supported. )

3 - Windows Server 2008 R2 ( at this point only machines running Vista and 7 can be added to domain - windows xp is no longer supported. All the functionalities of the domain controller are available)

keep in mind once you promote the domain controller to a higher level it can't be brouht to a lower level.

once active directory is installed restart you server and the you should be able to add the clients pc or laptos to the DC example

- right click over my computer icon
- click on properties
- computer name
- change the computer from workgroup to domain
- type your FQDN ( fully qualified domain name) example: mynetwork.local or mysite.com
- apply changes and restart
- your computer will be part of the domain next time system boots up.

Mar 01, 2011 | Computers & Internet

1 Answer

Join Domain


This issue could be caused by a few things in your config. First things to look at is your networking (taken past the point of ensuring the addresses are proper, same subnet and so forth) - can you ping the DC and the DNS? If you can ping can you resolve with an nslookup? Are you using DHCP - is it running? Do you have an active firewall?

The suffix's at the end of your post are troubling - is this a copy and paste of the error message or was it keyed in? Do you have a copy of your DCDiag.txt?

Run some NETDIAG tests such as NETDIAG /d:domain and/or NETDIAG /fix which should provide you with more specific information that will pinpoint the issue (hopefully).

Nov 12, 2009 | Computers & Internet

3 Answers

Getting error while joining any host(winxp or other os) to domain


Hi irudayaraj, you are right,and one more for checking use this http://www.whoisxy.com/ site ,really it is goos and free site.

Feb 15, 2009 | Microsoft Windows Server Standard 2003 for...

2 Answers

Domain creation


Hai,
You go to this site tucktail.In that site U check your desired domain name available r not.And then register the domain name.

Jan 27, 2009 | Microsoft Windows Server Standard 2003 for...

1 Answer

RECOVER FIRST DNS


Is there a running Domain Controller present? If so DNS info is often stored in Active Directory (A.D. Inegrated DNS Zone).  If this is the case you can just connect a server to the network, join the domian (verify DNS settings in TCI/IP config is pointing to Domain Controller) and then installm DNS from Add/Remove windows components.  Zone data should replicate from AD to new DNS server, to verify open DNS console and look for resource records relevent to the domain.

Dec 17, 2008 | Microsoft Windows Server Standard 2003 for...

2 Answers

DNS Deligation


hi,
the above attached a link document is for windows 2000 server not for 2003.


ramana

May 22, 2008 | Microsoft Windows Server Standard 2003 for...

2 Answers

First timer installing a Server network


Well i'm just going to start where i would start. First off, how do your machines on the network get their IP? DHCP?

Is the first listed DNS server the AD server? 192.168.1.1?

Also make sure your using case sensitive domain information when your trying to connect. It is rare but i have had that be my trouble.

I have remote software available and would love to help you fix this hands on if possible. I live for network problems ;)

Sep 29, 2007 | Microsoft Windows Server Standard 2003 for...

2 Answers

Win server 2003 enterprise


You need to ensure your DNS server is the first in the workstation's DNS list.

Does this help?

Sep 27, 2007 | Microsoft Windows Server Standard 2003 for...

Not finding what you are looking for?
Computers & Internet Logo

Related Topics:

38 people viewed this question

Ask a Question

Usually answered in minutes!

Top Computers & Internet Experts

Doctor PC
Doctor PC

Level 3 Expert

7733 Answers

kakima

Level 3 Expert

102366 Answers

David Payne
David Payne

Level 3 Expert

14161 Answers

Are you a Computer and Internet Expert? Answer questions, earn points and help others

Answer questions

Manuals & User Guides

Loading...