Solved

DNS Fatal error

Posted on 2006-11-16
7
892 Views
Last Modified: 2008-08-25
Please tell me what this means.


    Adapter : Local Area Connection

        Netcard queries test . . . : Passed

        Host Name. . . . . . . . . : hsserver
        IP Address . . . . . . . . : 192.168.0.105
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . : 192.168.0.1
        Dns Servers. . . . . . . . : 192.168.0.1


        AutoConfiguration results. . . . . . : Passed

        Default gateway test . . . : Passed

        NetBT name test. . . . . . : Passed
            No names have been found.

        WINS service test. . . . . : Skipped
            There are no WINS servers configured for this interface.


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
    List of NetBt transports currently configured:
        NetBT_Tcpip_{2FEB5929-AB27-4700-99FD-EE62B4D736F1}
    1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed
    [WARNING] You don't have a single interface with the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names defined.


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Failed
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'hsserver.homestyles.local.'. [RCODE_SERVER_FAILURE]
            The name 'hsserver.homestyles.local.' may not be registered in DNS.
    [FATAL] Could not open file C:\WINDOWS\system32\config\netlogon.dns for reading.
    [FATAL] No DNS servers have the DNS records for this DC registered.


Redir and Browser test . . . . . . : Failed
    List of NetBt transports currently bound to the Redir
        NetBT_Tcpip_{2FEB5929-AB27-4700-99FD-EE62B4D736F1}
    The redir is bound to 1 NetBt transport.

    List of NetBt transports currently bound to the browser
        NetBT_Tcpip_{2FEB5929-AB27-4700-99FD-EE62B4D736F1}
    The browser is bound to 1 NetBt transport.
    [FATAL] Cannot send mailslot message to 'HOMESTYLES*' via browser. [ERROR_INVALID_FUNCTION]


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Passed


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Failed
    [FATAL] Cannot lookup package Kerberos.
    The error occurred was: (null)


LDAP test. . . . . . . . . . . . . : Passed


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
    No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

    Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully
0
Comment
Question by:Matt Pessolano
[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
  • 3
  • 3
7 Comments
 
LVL 33

Accepted Solution

by:
NJComputerNetworks earned 500 total points
ID: 17958679
What is this machine:  Dns Servers. . . . . . . . : 192.168.0.1

192.168.0.1  is this a Windows DNS server?  I am guessing that this is actually your router...  If this is true, you need to make sure that every machine in your Windows domain is using the Windows 2003 DNS (and not pointing to a router for DNS resolution)

All machines in the domain must use the Windows DC/DNs server for DNS resolution.  The Windows DC/DNs server should then forward requests to the router or external DNS server to get resolution on the internet.
0
 
LVL 1

Author Comment

by:Matt Pessolano
ID: 17958752
192.168.0.1 is the ISP router.  ok i will make that happen and repost when I do.  What is that fatal error though.
0
 
LVL 33

Expert Comment

by:NJComputerNetworks
ID: 17958850
you will have tons of problems if you can't talk to the domain with DNS... fix this and you will be good to go...


In the DNS console, right click your server name and choose properties from the drop down box.  now click the Forwarders tab and enter the 192.168.0.1 address here...  this will allow you to resolve to the internet.
0
How Blockchain Is Impacting Every Industry

Blockchain expert Alex Tapscott talks to Acronis VP Frank Jablonski about this revolutionary technology and how it's making inroads into other industries and facets of everyday life.

 
LVL 1

Author Comment

by:Matt Pessolano
ID: 17958948
i can get to the internet no problem and I already have the forwarder configured.  my clients cant talk to the server thats the problem
0
 
LVL 33

Expert Comment

by:NJComputerNetworks
ID: 17959050
Check the event viewer on the server...  The DNs services might have been messed up because your were pointing to the router.  

Set the server to point to itself in TCP/IP (for DNs)  (never put the router IP in for your clients TCP/IP properties).  Then reboot the server... when it comes back online, it should create the DNS records for the domain.  Once this happens, the clients should be able to find information about your domain in DNS ...and connectivity/resolution should start working.
0
 
LVL 1

Author Comment

by:Matt Pessolano
ID: 17959109
ok i will try that first thing tomorrow morning.  Sorry I am not at the site right now..thanks
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Ready to improve network connectivity? Watch this webinar to learn how SD-WANs and a one-click instant connect tool can boost provisions, deployment, and management of your cloud connection.

Question has a verified solution.

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

ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
In this video you will find out how to export Office 365 mailboxes using the built in eDiscovery tool. Bear in mind that although this method might be useful in some cases, using PST files as Office 365 backup is troublesome in a long run (more on t…
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…

623 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