Help Center

Follow

Computer Not Found

Description

The computer name could not be found in DNS.

Possible Causes

The computer name may be misspelled or there is a problem with DNS.

DHCP updates to DNS can also cause this problem.

Recommended Fix

Ensure that the computer name can be resolved by using nslookup or ping.

It may be necessary to use the computer's fully qualified domain name or IP Address.

 

 

Was this article helpful?
2 out of 2 found this helpful
Have more questions? Submit a request

27 Comments

  • 0

    This is a weird issue. I can ping the pc by name from any pc including the one pdq is installed on. Yet it won't scan it saying computer name could not be found. I don't get it.

  • 0

    Are you able to ping using the full domain name of the computer?  PDQ Inventory uses the fully-qualified domain name and quite often the NetBIOS name will resolve while the FQDN does not.

  • 0

    When I ping it automatically appends the fqdn. So when I ping pc1 the ping shows "pc1.mydomain.com [ip]". Restarting the pc seemed to make pdq finally recognize it on the network.

  • 0

    Ping uses a slightly different name resolution method when it's called with the FQDN then when it's called with the NetBIOS name. PDQ Inventory uses .NET Framework name resolution which is close to ping's FQDN method, but not identical.  Because of these quirks the results can be different between the different tools, which is usually a bit confusing.  

    What most likely happened is that the when the computer's network interface came back on it got re-registered with DNS which allowed PDQ Inventory to resolve the name.

  • 0

    I have about 5 computers with this issue today. I've successfully pinged them by FQDN from the pc hosting PDQ. Yet pdq can't find the computers. As the day has passed some of those computers have finally been recognized.

  • 0

    When you see it again, try a couple of things:

    1.  Do an nslookup on the FQDN.  We've occasionally seen nslookup and ping resolve the name differently.

    2.  Restart the dnscache service.  This seems to crop up as a problem for name resolution fairly often, something in the cache gets messed up and flushing the cache with ipconfig /flushdns doesn't always fix it.

    Let me know if either of those help.  Name resolution is an ongoing problem that we're always doing research on.

  • 0

    If you have PDQ Inventory, running in Pro mode, you can create a custom tool to restart your DNS Client (dnscache service). See this post about minimizing the steps necessary. 

    http://support.adminarsenal.com/entries/20486111-calling-sysinternals-tools-from-within-pdq-inventory

    The heart of problem, however, still lies with DNS. This is just a work-a-round (albeit a necessary one depending on the health of your DNS environment)

  • 0

    When I do nslookup with fqdn it appends the domain to the end of it so that doesn't work very well. Example: pc1.mydomain.com is then appended the following: pc1.mydomain.com.mydomain.com. Obviously that will give me a bogus ip. So I'm not sure what you mean by doing an nslookup with fqdn? Typing the pc name by itself in nslookup automatically appends the domain to it.

    I'll try restarting the dns client service next time. As several minutes, hours & 2 days have passed, 7 out of 8 computers that pdq couldn't deploy to are now deploying. As far as I can tell the last one is turned off. Wake is not working on it so I have to check to see if WOL is turned on or not.

  • 0

    If you're getting your domain appended to the end of the nslookup search it means that DNS cannot find the FQDN.  Nslookup will first try the name you give it, and if it fails it will append your domain and try again.  You can force nslookup to only use the name you give it by ending it with a dot, so for example "nslookup pc1.mydomain.com." will only try that name and none other.  If you're not getting a result with that syntax it means that your DNS isn't resolving the computer name.

    Your system must be resolving the name another way (such as NetBIOS or WINS) and that method is taking a while before it resolves the computer's FQDN. It sounds like you need to look into your DNS configuration to make sure it's working correctly.

  • 0

    Adding the "." at the end makes sure it doesn't append the domain name again. Althoughit could be a dns issue, I think it's more of the option in the NIC under DNS tab that allows you to append DNS suffixes, which I do have checked. Hence, typing only the pc name automatically has the domain name appended. Same thing for adding the domain name to the pc name, then it automatically appends the domain name.

  • 0

    The search domains in the NIC options are only used if the name can't be found.  Nslookup will first query DNS using the name that you type in, and only when it can't find the name will it append the domain.  When DNS is working correctly nslookup will be able to find the computer's FQDN on the first try and then won't append the domain.

  • 0

    Appending the DNS suffix can be configured at the Connection (NIC level) but it usually configured via DHCP or Group Policy. Incidentally if your console machine can resolve a FQDN (e.g. sebastian.childdomain.parentdomain.com) in a separate domain but it can't resolve just the computername then DNS Suffix search order is a common culprit.

    To set the DNS Suffix search order from a GPO go to you Group Policy Management Editor and open your GPO. Edit the "DNS Suffix Search List" policy under Computer Configuration/Policies/Administrative Templates/Network/DNS Client.

  • 0

    I found a good answer to this. i was having these issues with my network I just took over with more than half the computers saying name not found. I deleted all the PTR records forward and reverse, ensured that dynamic updating of PTR records was enabled, then re-added all the computers to the domain through network ID, rebooted them all and PDQ everything works fine now. NOTE: I had to wait for the PTR record to show up in the DNS before PDQ would install and scan them correctly.

  • 0

    I found that I got the "Computer name could not be found" for A048737, but it worked for a048737.  I have never known DNS to be case sensitive before.  Am I missing something?

  • 0

    That is odd, it shouldn't be case sensitive.  Do you see a difference if you run NSLOOKUP on the two names?

    nslookup A048737

    nslookup a048737

  • 0

    This is what I get:

    C:\Users\WayneAndersen>nslookup A048737

    Server:  d7gxvls1.bps

    Address:  10.3.14.34

    Name:    A048737.BPS

    Address:  10.3.15.52
    C:\Users\WayneAndersen>nslookup a048737

    Server:  d7gxvls1.bps

    Address:  10.3.14.34

    Name:    a048737.BPS

    Address:  10.3.15.52

  • 0

    Which application did you see this error in and where did you see it?  It's probably an issue with a different type of name resolution.

  • 0

    The problem shows up in the free version of PDQ Inventory 1.1 (release 3)

  • 0

    PDQ Inventory uses the Fully Qualified Domain Name of the computer, which may have something to do with the difference.  Try the nslookup again with the full names:

    nslookup A048737.domain.com

    nslookup a048737.domain.com

  • 0

    You might also check if you have a correct domain suffix which is often changed when using VPN client sw. Check for "Primary Dns Suffix" in cmd > ipconfig /all

  • 0

    Thanks for replying guys.  Sorry about taking so long to reply.  I must have some kind of a flakey DNS issue going on.  When PDQ Inventory throws the error, I usually find that ping will not resolve either.  This happens even though nslookup usually is still working and the ping may have been working just a few minutes ago.  I'm at the point now where I don't know whether to hope the issue will go away or to hope that it breaks good so I can find the problem.

    Thanks again.  Wayne

     

  • 0

    I was having this same issue with two clients. The two clients were originally in a AD container that did not have any GPOs applied. I moved the computers to a container that had GPOs applied and one computer became instantly online and the error cleared. The other computer had a bogus DNS entry (IPV6) and did not have a reverse DNS entry. I cleared the bogus IPV6 entry, restarted computer and the computer also became online and the error cleared.

  • 0

    I had completely forgotten about this thread until I got the message from Terrrence's posting.

    I think our issue has been resolved.  I finally got Microsoft tech support involved in late July. They determined that it was because we had a single item domain name structure (node.BPS).  They worked me through the process of moving to a 2 entry domain name structure (node.BPS.net).  This was a fairly painful process but in the end if fixed our problem and several other irritating problems we had been having for years.

  • 0

    Those kinds of problems are what I was thinking of when I put "You bang your head for hours on a strange problem before accidentally figuring out, days later, that it was DNS" to the  System Admin Drinking Game.

  • 0

    Now that I think about this issue and other issues we have had with our network, PDQ Inventory has identified previous unknown/unforeseen/unnoticed  issues by reporting various errors of clients.

    I know you PDQ guys don't advertise this, but PDQ Inventory is really an unofficial AD/network troubleshooting tool.

    I know the errors are listed on the forum and can be manually connected to when on an Internet connected network to the online help but providing these errors and their various troubleshooting steps in the Help section (if it is not already) or in a single file can save an administrator many man-hours from troubleshooting and headaches.

  • 0

    We've had a couple of requests the last few days to include these error documentation pages in the offline help file.  It's now on our road map get that done.

  • 0

    Trouble with PDQ Deploy across multiple sites.  See my comment, it may help.

    Hi everyone.  I help support five auto dealerships across town.  I have been able to deploy to computers at whichever dealership I am, or that I remote into because our stores are interconnected.  However I have been unable to use PDQ deploy to deploy across the stores if I am not actually using a computer physically located there.  My manager assisted me in finding a solution which I hope will prove helpful to some here.

    At his suggestion I added the computers' IP address and computer name (host name) to the host file on my computer.  After that PDQ Deploy instantly was able to find the targets.

Article is closed for comments.
Powered by Zendesk