DNS Error

Discussion in 'Server Networking' started by Andrew Johnson, Mar 30, 2005.

  1. Hi,

    I am trying to configure my server with Active Directory and DNS enabled.
    Everything appears to be working, except trying to contact the server using
    \\servername, and related takes such as logging onto the domain from other

    Using a prompt from a client, I can acess the machine using the IP address,
    but not using \\servername.

    Help appreciated! Guess its something simple I missed.

    Andrew Johnson, Mar 30, 2005
    1. Advertisements

  2. Single-word Names are "netbois names" and are handled by WINS,..or by DNS if
    the DNS Suffixes are used.

    Try using the FQDN \\servername.mydomain.tld
    Phillip Windell, Mar 30, 2005
    1. Advertisements

  3. It would probably help if you specified the exact errors you are receiving.
    The most common source of AD/DNS errors are;

    1. Clients must be configured to exclusively use the server for DNS.

    2. The server must be configured to exclusively use itself for DNS.

    3. The subdomains - eg. _msdcs - must exist - check the DNS console on the
    server. If the subdomains do not exist, try running: 'net stop netlogon'
    followed by 'net start netlogon.'

    Doug Sherman
    Doug Sherman [MVP], Mar 30, 2005
  4. FQDN (\\adjserver.johnson.local I presume) doesn't work either.

    Error is 'the network path could not be found'.



    Andrew Johnson, Mar 30, 2005
  5. Hi,

    Thanks for your reply. (2) is done. (1) doesn't work; but I have had it
    established before without doing this! What happened was I installed VPN,
    couldn't get it to work, uninstalled VPN which didn't work, then uninstalled
    DNS, reinstaleld DNS - and it now doesn't work

    (3) - the subdomains do exist.

    When I try to connect, it just say that server can't be found.


    Andrew Johnson, Mar 30, 2005
  6. Correction....!

    (1) does solve the problem, but doing that stops the internet connection
    working (which is provided through a separate router-modem). The internet
    connection DOES work on the server itself!!

    Many thanks!!
    Andrew Johnson, Mar 30, 2005
  7. Very sorry *blushing*...

    The internet connection *does* work; but attempts to use MSN Messenger do
    Andrew Johnson, Mar 30, 2005
  8. I think the ultimate issue is telling the router to direct any traffic for
    adjserver to the relevant IP for the server, but I'm not sure how to do


    Andrew Johnson, Mar 30, 2005
  9. One thing that will help in troubleshooting DNS issues is to bear in mind
    that failed DNS queries will be cached. As a result, you can make a
    configuration change which actually solves the problem, but clients continue
    to get DNS failures because they check their local cache first. You can
    clear the cache on the client and/or server without rebooting by running
    ipconfig /flushdns. Of course, I have never personally forgotten to do

    As to MSN Messenger - dunno - could be a router/firewall issue.

    Doug Sherman
    Doug Sherman [MVP], Mar 30, 2005
  10. Impossible to say. I have no information about. If you have any other info
    to posts, go ahead, but I am leaving for the day and will be back tomorrow.

    Doug's a good guy,..he will take care of you...


    Phillip Windell [MCP, MVP, CCNA]

    Phillip Windell, Mar 30, 2005
  11. Ok. Cheers!


    Andrew Johnson, Mar 30, 2005
  12. Something really isn't working right. It now isn't working again (no
    settings have changed since last night!!); don't know if this is
    relevant...I can do nsnlookup on clients, and get it showing the
    servername.domain and the correct IP address.

    Does this suggest an Active Directory problem?

    Thanks for all help,

    Andrew Johnson, Mar 31, 2005
  13. MSN thing was irrelvant...seemed like a general error, sorry.

    The ipconfig thing doesn't see to make a difference.

    I have now, by changing the DNS on the clients, reached the point at which I
    can log on to the domain, but I still cannot access \\servername through
    Explorer (though I can still access the machine using the IP Address). Any

    Thanks as always,

    Andrew Johnson, Mar 31, 2005
  14. Hmmm. Now we're back to Phil's original take. It sounds like DNS is
    working, but there is a NetBIOS issue. An unlikely but possible explanation
    would be creating a different NetBIOS name on the server during AD
    installation - this can happen automatically if you have an unusually long
    name for the server. Open a command prompt and type:

    nbtstat -n ENTER

    Is servername listed? If it is not or you get an error, check your Local
    Area Connection TCP/IP properties and make sure that NetBIOS over TCP/IP is
    enabled on the WINS tab in Advanced properties.

    Doug Sherman
    Doug Sherman [MVP], Mar 31, 2005
  15. It wasn't listed and that option wasn't enabled. I think you may very well
    have solved my problem! Thank you so very much for your time and help!!!

    As ever,

    Andrew Johnson, Apr 1, 2005
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.