Solved

NS lookup cannot find domain controller SBS2003

Posted on 2008-10-03
20
489 Views
Last Modified: 2012-08-13
I have a Server SBS 2003.  It was newly installed around January of this year.  Recently, the server stopped showing up in the "My Network Places".  So, I did nslookup, but it says that it cannot find the server name for 192.168.1.100.  I uninstalled and reinstalled DNS.  Made sure that there was a forwarder zone and a Reverse lookup zone.  Made sure that DHCP was working as a service and that it updates DNS.  
Other part of message is **Can't find server name for address 192.168.1.100 : Non-existent domain
Default server: unknown
Address: 192.168.1.100.
0
Comment
Question by:zotfarms
[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
  • 12
  • 6
  • 2
20 Comments
 
LVL 31

Expert Comment

by:Henrik Johansson
ID: 22639022
For nslookup error: Make sure the PTR record for 192.168.1.100 is created in reverse lookup zone.
0
 

Author Comment

by:zotfarms
ID: 22639049
It is not There, how do you make it show up?
0
 

Author Comment

by:zotfarms
ID: 22639053
Now also, I have workstations that will not logon because they say that the domain is not available.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
LVL 31

Expert Comment

by:Henrik Johansson
ID: 22639099
As I understood the questoin the forward lookup zone for domain.com and reverse lookup zone for 192.168.x.y has already been created. Is this true?
0
 
LVL 3

Expert Comment

by:DraconianSoul
ID: 22639104
Just out of morbid curiosity... the SBS server is in fact set with 192.168.1.100?  Make sure your workstation is set to use the SBS server's IP in DNS.  Try 'ping -a 192.168.1.100' and see if that replies with the resolved hostname and 4 pings.  Did anyone install a firewall or new antivirus scanner on the SBS server?
0
 

Author Comment

by:zotfarms
ID: 22639148
Yes, it is set for 192.168.1.100.  I do have the workstation DNS setting for 192.168.1.100.  I updated the antivirus on the server, but after this problem occurred, I totally uninstalled the AV.  On the workstation in question, I also put the server's ip address and FQDN with ip address in the host file.
0
 

Author Comment

by:zotfarms
ID: 22639153
This server is also running Exchange.  I don't know if that is a factor.
0
 

Author Comment

by:zotfarms
ID: 22639159
I have disabled the firewall service on the server as well.
0
 
LVL 3

Expert Comment

by:DraconianSoul
ID: 22639180
Is the workstation and server on the same subnet? IE, is there a firewall or router between the two computers?

Also, what about the ping?  The -a switch resolves and displays the hostname.  If we get four good replies we know we can communicate with the server.  I'm assuming you're running nslookup on the workstation with no additional switches?  Does nslookup behave properly on the server itself?
0
 

Author Comment

by:zotfarms
ID: 22639353
I can ping.  I added the prt entry on the reverse lookup, so now when I do nslookup on the server, it now says that it is working fine.  I have not tried nslookup on the workstations.  They are all on the same subnet, the server is acting as DHCP and DNS.
0
 

Author Comment

by:zotfarms
ID: 22639360
I noticed in the DNS Forwarders on the zone, the 4 folders : dc, domains, gc, and pdc are missing.
0
 
LVL 3

Expert Comment

by:DraconianSoul
ID: 22639371
In DNS settings of the server, is "Register this connection's addresses in DNS" checked?
0
 

Author Comment

by:zotfarms
ID: 22639392
where do I find that setting?
0
 
LVL 3

Expert Comment

by:DraconianSoul
ID: 22639402
In the control panel open Network Connections or on the desktop right clickn on My Network Places and choose properties.  Right click on the network adapter and choose properties.  Select TCP/IP and click properties.  Click advanced.  Select the DNS tab.  In that window at the bottom is a check box labeled Register this connection's addresses in DNS.
0
 

Author Comment

by:zotfarms
ID: 22639414
ok selected, register this connection's address in dns
0
 
LVL 3

Expert Comment

by:DraconianSoul
ID: 22639436
So it was cleared?  This would cause most of your problems.  A domain controller needs to update the DNS server with its records (such as the ones you noticed were missing) as well as its A and PTR records.  If this is cleared it will prevent the DC from updating any and all DNS records.
0
 

Author Comment

by:zotfarms
ID: 22639444
it was cleared.  Also the option below it something about a suffix.
0
 

Author Comment

by:zotfarms
ID: 22639447
I've populated the Register this connection's addresses in DNS option now.
0
 
LVL 3

Accepted Solution

by:
DraconianSoul earned 500 total points
ID: 22639450
I'm pretty sure you can ignroe the entry about the suffix, i've always seen it unchecked.

OK, now you might have to restart the netlogon service to refresh the DNS records.  Drop to a command line and run these three commands.
net stop netlogon
net start netlogon
ipconfig /registerdns
0
 

Author Closing Comment

by:zotfarms
ID: 31502958
The register this connection on dns was exactly right.  Thanks so much!!!!
0

Featured Post

Major Incident Management Communications

Major incidents and IT service outages cost companies millions. Often the solution to minimizing damage is automated communication. Find out more in our Major Incident Management Communications infographic.

Question has a verified solution.

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

Last week, our Skyport webinar on “How to secure your Active Directory” (https://www.experts-exchange.com/videos/5810/Webinar-Is-Your-Active-Directory-as-Secure-as-You-Think.html?cid=Gene_Skyport) provided 218 attendees with a step-by-step guide for…
Active Directory security has been a hot topic of late, and for good reason. With 90% of the world’s organization using this system to manage access to all parts of their IT infrastructure, knowing how to protect against threats and keep vulnerabil…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

751 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