Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

Troubleshooting
Research
Professional Opinions
Ask a Question
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

troubleshooting Question

Windows 2003 Server: Should it be running DNS (See: diagram)

Avatar of rdivilbiss
rdivilbissFlag for United States of America asked on
Windows Server 2003Active DirectoryMicrosoft Server OS
59 Comments1 Solution1417 ViewsLast Modified:
My Windows 2003 Server is a file and print sharing machine. (OLYMPUS) It also runs MS SQL Server, MySQL, and IIS (primary development machine).

AD and DNS are running. DHCP is not. There is no other DC.

I have a mix of wireless clients (notebooks) and hard wired clients (desktops).

I have several Windows XP Pro machines, a Linux Desktop, a Linux laptop, and a Vista Home laptop.  All XP machines a members of the domain net.sb.local. The Linux computer can file and print share via SAMBA. The Vista laptop can always remember file shares after a restart but has difficulty reconnecting to shared printers, physically attached to the Windows 2003 server.

The wireless router assigns DHCP.

Running C:\>DCdiag /test:dns

returns the following (see code block)

I'm guessing some of the errors may go away if I add an A record and a PTR record for the wireless router.

I'm most concerned about: "Warning: could not confirm the identity of this server in the directory versus the names returned by DNS servers. If there are problems accessing this directory server then you may need to check that this server is correctly registered with DNS."

as the DNS has A, PTR, and NS records for the server.

Suggestions?
Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\OLYMPUS
      Starting test: Connectivity
            *** Warning: could not confirm the identity of this server in
               the directory versus the names returned by DNS servers.
               If there are problems accessing this directory server then
               you may need to check that this server is correctly registered
               with DNS
         ......................... OLYMPUS passed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\OLYMPUS

DNS Tests are running and not hung. Please wait a few minutes...

   Running partition tests on : ForestDnsZones

   Running partition tests on : DomainDnsZones

   Running partition tests on : Schema

   Running partition tests on : Configuration

   Running partition tests on : net

   Running enterprise tests on : net.sb.local
      Starting test: DNS
         Test results for domain controllers:

            DC: olympus.net.sb.local
            Domain: net.sb.local


               TEST: Basic (Basc)
                  Warning: Adapter 00:0B:6A:26:AC:F4 has dynamic IP address (can be a misconfiguration)
                  Warning: adapter [00000001] VIA Rhine II Compatible Fast Ethernet Adapter has invalid DNS server: 192.168.1.1 (<name unavailable>) <--wireless router
                  Error: all DNS servers are invalid
                  Error: The A record for this DC was not found

            TEST: Records registration (RReg)
               Error: Record registrations cannot be found for all the network adapters

         Summary of test results for DNS servers used by the above domain controllers:

            DNS server: 192.168.1.1 (<name unavailable>) <--wireless router
               1 test failure on this DNS server
               Name resolution is not functional. _ldap._tcp.net.sb.local. failed on the DNS server 192.168.1.1

         Summary of DNS test results:

                                            Auth Basc Forw Del  Dyn  RReg Ext
               ________________________________________________________________
            Domain: net.sb.local
               olympus                      PASS FAIL PASS PASS PASS FAIL n/a

         ......................... net.sb.local failed test DNS
ASKER CERTIFIED SOLUTION
Avatar of Adam Brown
Adam BrownFlag of United States of America imageCloud Security Consultant
Commented:
This problem has been solved!
Unlock 1 Answer and 59 Comments.
See Answers