Solved

DNS Error  - Cannot joing a Windows 7 workstation to a SBS2003 Server

Posted on 2010-11-17
11
857 Views
Last Modified: 2012-05-10
When trying to add a Win 7 professional workstation to the domain controller I receive the following error message:

An attempt to resolve the DNS name of a domain controller in the domain has failed.  Please verify that this client is configured to reach a DNS server that can resolve DNS name in the target domain.

When I do an nslookup I get the following message.  richtwpserver.richlandtwp can't find ... server failed.  

The event log states it cannot find the SOA record.  I  deleted the old SOA record and created a new one.  When creating the new one the .local was left off.

I have reviewed tech docs until I can't read any more.  Nothing seems to work.  I  tried to run diag.exe /fix.  It must not be installed on the server.  Can I download it.

DHCP is running on the router.  It seemed that DHCP and DNS work with each other so I was going to change it to the server and I recieved an error message.  

None of the system are appearing in the forward zone record.  System have been running slow and losing the connection to the SQL server.  I am starting to believe that it is all stemming from this problem.

Thank you for your help.
Bonne001
0
Comment
Question by:Bonne001
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
11 Comments
 
LVL 5

Expert Comment

by:frostsystems
ID: 34159719
1) If more than one NIC exists on the Win7 machine, disable all other NICs except for 1 LAN adapter.

2) Assign a static DNS address on this NIC. The DNS server should be that of your SBS2003's IP.

3) Retry to join the domain.
0
 
LVL 3

Expert Comment

by:blaslett
ID: 34159805
Assign the client PC a valid IP address for the network domain. ie if your network is 192.168.1.0-255.255.255.0 then select and unused IP in the 192.168.1.1-192.168.1.254 range.

Set the DNS IP to that of the SBS2003 server.

Gateway IP can also be that of the server.

IMO, DHCP server function should always reside on the DC, once you have this issue resolved I would transfer the DHCP role from the router to the server.
0
 

Author Comment

by:Bonne001
ID: 34159832
Add the IP# 192.168.1.29 DC 192.168.1.5 Gatway 192.168.1.1

Still does not work.  We have done this on XP systems and they work.
0
Three Reasons Why Backup is Strategic

Backup is strategic to your business because your data is strategic to your business. Without backup, your business will fail. This white paper explains why it is vital for you to design and immediately execute a backup strategy to protect 100 percent of your data.

 
LVL 15

Expert Comment

by:JBond2010
ID: 34159880
Flush the DNS cache on the Windows 7 PC. Go to the command prompt and type ipconfig /flushdns and press enter and then type ipconfig /registerdns and press enter.

Check the ip settings on the PC and make sure that the ip schema is a valid ip schema and that the PC's DNS address is pointing to your SBS2003 Server. Try to rejoin the PC to the domain.

Check in DNS to see if there is any stale records.
0
 
LVL 77

Expert Comment

by:Rob Williams
ID: 34159920
DNS is your primary issue, and in an SBS domain you should have DHCP running on the server not the router. But when adding Win7 machines you should review all the necessary steps:
Deploying Win 7 in your SBS 2003 network:
http://cid-c756c44362cd94ad.skydrive.live.com/self.aspx/Windows7Stuff/HOW%20TO%20DEPLOY%20WINDOWS%207%20IN%20YOUR%20SBS%202003%20NETWORK.docx
0
 

Author Comment

by:Bonne001
ID: 34159998
Thank you JBond2010 I had tried flusing the DNS and registering it before but thought it never hurts to try again.  Didn't work.  

This is what I get when I do an IPconfig after flushing and registering the DNS
I have attached the screen shot.


The funny thing is the DC is picking the system up under computers.

I will read RobWill article and get back to you.
C:\Users\marge>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : marge-PC
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet
   Physical Address. . . . . . . . . : F0-4D-A2-2F-09-46
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.1.29(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1
   DNS Servers . . . . . . . . . . . : 192.168.1.5
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{352C646A-96BA-4415-9588-440524FF5048}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft 6to4 Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:2058:124d:3f57:fee2(Pref
erred)
   Link-local IPv6 Address . . . . . : fe80::2058:124d:3f57:fee2%15(Preferred)
   Default Gateway . . . . . . . . . : ::
   NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Users\marge>

Open in new window

0
 
LVL 77

Expert Comment

by:Rob Williams
ID: 34160047
If not using the SBS as the DHCP server you should also add your DNS suffix to the advanced TCP/IP properties under DNS / "use this DNS suffix for this connection"
0
 

Author Comment

by:Bonne001
ID: 34165735
Thank you all for your help.  I had to call Microsoft to get this resolved quickly.  The problem was a corrupt DNS.  The xxx.local was actually resolving to an outside IPAddress?  It baffeled the MS Agent also.  I didn't uncover that yesterday when I did a nslookup it said it could not find the server; the same with ping!

Thank you again for your quick reply.

0
 
LVL 77

Expert Comment

by:Rob Williams
ID: 34166315
Glad to hear to were able to 'resolve'.
Thanks for updating.
Did they explain how it might have wound up resolving to an external IP? Would be good information to have.
0
 

Accepted Solution

by:
Bonne001 earned 0 total points
ID: 34166751
I'll ask during my follow-up with them and post it.  Good question!
0
 

Author Closing Comment

by:Bonne001
ID: 34426422
Called Microsoft and had them help me rebuild the
DNS.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If you get continual lockouts after changing your Active Directory password, there are several possible reasons.  Two of the most common are using other devices to access your email and stored passwords in the credential manager of windows.
By default the complete memory dump option is disabled in windows . If we want to enable the complete memory dump for a diagnostic purpose, we have a solution for it. here we are using the registry method to enable this.
Windows 8 comes with a dramatically different user interface known as Metro. Notably missing from the new interface is a Start button and Start Menu. Many users do not like it, much preferring the interface of earlier versions — Windows 7, Windows X…
The viewer will learn how to successfully download and install the SARDU utility on Windows 7, without downloading adware.

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question