Question

Can't ping PCs by name

Asked by: photograffiti

I've ran into this issue randomly and decided this time to figure out what's going on. It doesn't always happen but sometimes it does.
I have a home network that has a Windows 2003 server that is acting as the DC, DNS, DHCP, etc. My laptop is a Windows XP Pro machine and it is picking up the proper DNS server (the W2K3 server) via DHCP. If I open up a Command Prompt and try to ping any of my other machines via the Netbios name or even the FQDN name, it will fail. However, if I do an nslookup it will resolve no problem. If I ping via IP address this works too. At first I was not able to ping the DC either but after a while it just started working. Now I can ping the W2K3 machine via it's Netbios name but noone else.
Any reason why I can resolve the name via nslookup but via ping it will not resolve?

This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.

Subscribe now for full access to Experts Exchange and get

Instant Access to this Solution

  • Plus...
  • 30 Day FREE access, no risk, no obligation
  • Collaborate with the world's top tech experts
  • Unlimited access to our exclusive solution database
  • Never be left without tech help again

Subscribe Now

Asked On
2005-08-25 at 21:54:24ID21540845
Tags

ping

,

name

Topics

Miscellaneous Networking

,

TCP/IP

,

Domain Name Service (DNS)

Participating Experts
3
Points
500
Comments
26

Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.

  • "The time we save is the biggest benefit of Experts Exchange to Warner Bros. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange." Mike Kapnisakis, Warner Bros.
  • "Our team likes having a resource that is more secure than just using Google and most experts using this service really know their stuff. It's nice to look here first versus using Google." Dayna Sellner, Lockheed Martin
  • "Anytime that I've been stumped with a problem, 9 out of 10 times Experts Exchange has either the accepted solution or an open discussion of the potential solution to the problem." Kenny Red, eBay Inc.

See what Experts Exchange can do for you.

Got a question?

We've got the answer.

Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.

Screenshot of Experts Exchange Knowledgebase

Need individual assistance?

Our experts are ready to help.

If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.

Screenshot of Experts Exchange Knowledgebase

Want to learn from the best?

Read articles from industry experts.

Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.

Screenshot of an Article

Working on a long term project?

Store your work and research.

Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.

Screenshot of Experts Exchange Knowledgebase

Access the answers to your technology questions today.

Subscribe Now

30-day free trial. Register in 60 seconds.

What Makes Experts Exchange Unique?

Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Trusted by the world's most respected brands.

image of each brand's logo

Faithfully serving IT professionals since 1996.

Experts Exchange Logo

Try it out and discover for yourself.

Subscribe Now

30-day free trial. Register in 60 seconds.

Related Solutions

  1. ping to fqdn fails, when nslookup for the fqdn is successf…
    Somehow all the applications fail to translate fqdn (or netbios) name to ip address. Looks like none of the applications attempt to lookup hosts file or do nslookup. ping localhost - failed [with error "could not find host localhost"] ping 127.0.0.1 - successful ...
  2. can ping by FQDN, but not by netbios name
    I can ping a child domain server by FQDN, but not by it's regular old netbios type name. On the DNS server it pings either... on all other servers/workstations it requires the FQDN. What gives?
  3. Ping to get NetBios name
    If I ping an NetBios name I get the IP, is it possible to do this in reverse? So I ping an IP and it gives me the name of the pc. For example if I use the command 'ping laura' I get the IP 192.168.1.5 however if I want to find the PC name at 192.168.1.5 how do I do this? Tony
  4. No Nslookup
    Ok I think this is an easy fix. If I want to do an nslookup on an IP address in my domain I get a Non-existent domain. >nslookup 10.1.10.3 Server: domain.DNS.com Address: 10.1.10.98 *** domain.dns.com can't find 10.1.10.3: Non-existent domain however if i ping 10.1.10....
  5. Cannot Ping FQDN
    I have a Kubuntu Desktop fresh install i cannot ping a FQDN on my local network. EX: my local network is mydomain.local PC is called mypc.mydomain.local I can ping mypc and i get back my IP and FQDN in the ping output. I can ping my IP and get the FQDN of my IP I CANNOT ...
  6. cannot join domain using fqdn, only netbios name ?
    If I try ot join a winxp pc to a domain using the fqdn imageproc.imageproc.com, it fails. If I try to join using netbios name imageproc, it works fine ? Is this correct behaviour ?

Free Tech Articles

  1. WARNING: 5 Reasons why you should NEVER fix a computer for free.
    It is in our nature to love the puzzle. We are obsessed. The lot of us. We love puzzles. We love the challenge. We thrive on finding the answer. We hate disarray. It bothers us deep in our soul. W...
  2. SCCM OSD Basic troubleshooting
    SCCM 2007 OSD is a fantastic way to deploy operating systems, however, like most things SCCM issues can sometimes be difficult to resolve due to the sheer volume of logs to sift through and the dispe...
  3. Migrate Small Business Server 2003 to Exchange 2010 and Windows 2008 R2
    This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Windows 2008 R2 with Exchange 2010. For this migration to work you will need the fo...
  4. Create a Win7 Gadget
    This article shows you how to create a simple "Gadget" -- a sort of mini-application supported by Windows 7 and Vista. Gadgets can be dropped anywhere on the desktop to provide instant information, ...
  5. Outlook continually prompting for username and password
    There have been a lot of questions recently regarding Outlook prompting for a username and password whilst using Exchange 2007. There are a few reasons why this would happen and I will try to cover t...
  6. Backup Exchange 2010 Information Store using Windows Backup
    There seems to be quite a lot of confusion around the ability to backup Exchange 2010 using the built in Windows Backup feature. This stems from the omission of this feature prior to Exchange 2007 s...

Cloud Class Webinars

  1. Avoiding Bugs in Microsoft Access
    Alison Balter takes and in-depth look at avoiding bugs in Access. In this webinar you will learn about using the immediate window to debug your applications, invoking the debugger, using breakpoints to troubleshoot, stepping through code, setting the next statement to execute, ...
  2. Top 10 Best New Features in Visio 2010
    Scott Helmers gives live demonstrations of the top 10 new features in Visio 2010. This webinar will teach you how to create compelling diagrams by adding shapes to the page with a single click, linking the shapes in a diagram to data in Excel (or SQL Server, or SharePoint), ...
  3. IT Consultant Business Secrets Revealed
    Michael Munger, Experts Exchange tech pro and IT consultant, pulls back the curtain on his very successful businesses and answers question on every IT consultant and business owner should know about. He shares secrets on what he did to solve the 5 most common problems in IT, ...
  4. Disaster Recovery and Business Continuity
    Quest CTO, Mike Billon, gives an overview of the steps involved in building a dunamic disaster recovery plan. Through case studies and an examination of software/hardware tooles for monitoring and testing, you'll gain a better understandin of where you are, where you want ...
  5. Organize Your Visio Diagrams with Containers and Lists
    Scott Helmers uses cross functional flowcharts, wireframe diagrams, data graphic legends and seating charts to teach you: how to ustilize all three new structured diagram components in Visio 2010, the best practices for organizeing shapes in previous version of Visio, how to organize ...
  6. How to Us Objects, Properties, Events and Methods in Microsoft Access
    Alison Dalter gives an in-depbth look at objects, properties, events and methods in Microsoft Access. In this webinar you will learn about using the object browser, referring to objects, working with properties and methods, working with object variables, understanding the ...

Join the Community

Give a Little. Get a Lot.

Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.

Join the Community

Answers

 

by: photograffitiPosted on 2005-08-25 at 22:04:50ID: 14758617

Well, my default DNS settings were 'Append primary and connection specific DNS suffixes'. Apparently that wasn't enough. I added the check mark beneath that which read 'Append parent suffixes of the primary DNS suffix' and that fixed the problem.
I still don't see why I had to add that second portion. Actually, I don't even quite understand what it means. Plus, I was pinging via FQDN so did I even need any of this?
Still want to find out why.

 

by: kbbcnetPosted on 2005-08-26 at 00:02:22ID: 14758940

<<I still don't see why I had to add that second portion.
<<
PC1; GM; Pup;    <-- netbios name   <-- requires Wins/lmhosts
Ping GM

pc1.domainName   <-- FQDN    <-- requires DNS
Ping GM.domainName
ping Pup.domainName

Think of a Domain as an inverted Tree.
http://en.wikipedia.org/wiki/FQDN
---------------------

If you earlier windows versions than win2k/xp PCs -- you will need to add a WINS Server &/or configure a LMHosts file.

Verify DHCP scope option 44 (WINS/NetBIOS name server) points to the WINS server and scope option 6 shows the address of your DNS server. When you don't define these options, you almost guarantee problems with client browsing.

 

by: aplonaPosted on 2005-08-26 at 08:33:48ID: 14761850

Are these machines you are trying to ping xp sp2.  If the firewall is enabled then it won't let you ping by name.  You have to make an exception for file and printer sharing.  Try disabling the firewall first and ping it by name.

 

by: photograffitiPosted on 2005-08-26 at 08:53:14ID: 14762013

kbbcnet,

If I ping via the Netbios name I don't necessarily need a WINS server since I've got it configured to append the DNS suffix to finish out the FQDN. That's the whole point of DNS suffixes, isn't it? So in your example if the Netbios name is  Pup, then it should automatically append .domainname when I ping it. Which it does do now.

aplona,

It is not the firewall. The pings are already working now that I modified the DNS settings in the TCP/IP Advance tab. Please read my second post.

My question, as it is right now, is why do I have to check that second option even when I'm already pinging via the FQDN.

 

by: kbbcnetPosted on 2005-08-26 at 12:24:53ID: 14764084

<<That's the whole point of DNS suffixes, isn't it?
<<
Yes, suffixes will allow you to ping DNS names without the suffix of your domain.

<<My question, as it is right now, is why do I have to check that second option even <<when I'm already pinging via the FQDN.

However, if you have a parent domain then with out the second selection or approriate DNS setup -- it would fail.   Also, creates problems mapping drives to parent domain resouces.

Example.
Local Domain - all success pings.
ping pup.mynet.parentnet
ping pup.mynet
ping pup  

Parent Domain.
Ping kit.parentnet <-- works
Ping kit  <--- fails

Hope this makes sense :)

 

by: photograffitiPosted on 2005-08-26 at 12:52:44ID: 14764301

That makes sense. However, I only have mydomain.com. So I'm pinging DC it fails. If I ping DC.mydomain.com and it still fails. But if I do 'nslookup DC' it resolves.
Weird.

 

by: kbbcnetPosted on 2005-08-26 at 13:02:45ID: 14764384

When you setup DNS -- did you sit as root or to foward out to the ISP DNS?

Nslookup will depend somewhat on the server queried & authoritive for the domain.

Is the W2k3 DNS server resolving mydomain.com?

Is this a registered domain name?

 

by: photograffitiPosted on 2005-08-26 at 15:03:15ID: 14765605

The DNS server is my DC in my W2K3 domain. The domain name is a valid domain-name but the NS record still points to a public DNS server, not mine. My server is only for internal use. I do have a forwarder setup on my DNS server for anything outside of my domain. And yes, the server is resolving anything related to mydomain.com.

 

by: kbbcnetPosted on 2005-08-26 at 15:59:14ID: 14765919

On your PCs TCP/IP Settings or in the DHCP Server --
is the local DNS server set as Primary & the internet DNS setup as seondary?

In the DNS MMC -
Do you show 'A' records in the forward lookup zone

Do you have a reverse lookup zone populated with the necessary PTR records.

 

by: photograffitiPosted on 2005-08-26 at 16:26:57ID: 14766048

The local DNS server is primary and the secondary is 4.2.2.2, the same IP as the forwarder set up on my DNS server. As for A and PTR records, they are both there under Forward and Reverse Lookup Zones, respectively.
As I mentioned, the nslookup is successful. It's the ping that doesn't work. Really weird.

 

by: kbbcnetPosted on 2005-08-26 at 16:54:11ID: 14766116

<<As I mentioned, the nslookup is successful. It's the ping that doesn't work. Really
<< weird.
<<
Agreed - wierd ':-/

i keep thinking i must have missed something simple.

 

by: photograffitiPosted on 2005-08-26 at 17:31:47ID: 14766257

As of right now I can ping my DC but not another PC. Here is a screen shot of my setup.

http://images9.fotki.com/v171/photos/1/132936/1076386/EEQuestion-vi.jpg

 

by: photograffitiPosted on 2005-08-26 at 17:36:38ID: 14766267

Crap, the picture shows me pinging by Netbios name only and it failed. I just tried it via FQDN and it works. But I swear it didn't earlier. However, currently if fails even by Netbios name which it shouldn't if it is appending DNS suffixes properly. Which I guess it isn't. But why not, the names are resolving via DNS properly.

 

by: kbbcnetPosted on 2005-08-26 at 19:50:29ID: 14766558

<<Which I guess it isn't. But why not, the names are resolving via DNS properly.>>
*Usually DNS works fine with only these two default settings set & the other blank!
/ *DNS Server addresses in order of use    <-- Local Domain DNS, then ISP DNS
/ *Register this conneciton's addresses in DNS
---------------------------------

You have a very unusual setup, especially if you do not have a parent domain.
*Instead, try these settings -

/ *DNS Server addresses in order of use    <-- Local Domain DNS, then ISP DNS
/ Uncheck --> Append Primary ......
/ Check --> Append these DNS suffixes in order  
/ Add your domain suffix & any ISP suffixes that you may use
/ DNS suffix for this connection        <-- Leave Blank
/ *Register this conneciton's addresses in DNS                              
/ Use this connection's DNS suffix           <-- Leave Blank

This should resolve your problem :)

 

by: photograffitiPosted on 2005-08-26 at 20:05:00ID: 14766590

I made the changes you suggested, which was moving from Append Primary to Append suffixes in the order I added. And to also leave a couple of the sections blank.
However, I still have the same issue. I even added a new A record for my wireless AP called ap. If I try to ping ap.mydomain.com or just plain ap, it will fail. However if I do nslookup ap, it will show the IP address and the FQDN of ap.mydomain.com.

 

by: kbbcnetPosted on 2005-08-26 at 20:13:32ID: 14766607

In your w2k3 server event logs you should see some DNS errors & the like.

Have you checked?

Computer Mgmt MMC/system tools/event viewer/system|
Look for errors - DNS, DCHP, TCPIP, etc.

 

by: kbbcnetPosted on 2005-08-26 at 20:17:08ID: 14766616

Troubleshooting DNS
http://www.microsoft.com/technet/itsolutions/cits/mo/winsrvmg/dnspog/dnspog5.mspx
 Overview
 Problem #1: DNS Name Resolution Failure
 Problem #2: DNS Client Receives Name Not Found Error
 Problem #3: DNS Server Provides Stale Information
 Problem #4: DNS Server Not Responding to Clients
 Problem #5: Clients Not Providing Dynamic Updates
 Problem #6: Server Not Providing Dynamic Updates
 Problem #7: Zone Delegation Failures
 Problem #8: Zone Transfer Failures

 

by: kbbcnetPosted on 2005-08-26 at 20:20:10ID: 14766623

One other thought -- In DCHP the client DNS is configure per the DCHP Server settings.

Have you check the DCHP setting for DNS?

 

by: photograffitiPosted on 2005-08-26 at 20:21:26ID: 14766625

Event Viewer does not show any errors under system for DNS. The last errors were for IAS because I was trying to set up WPA with Radius authentication with Certificates. DNS server logs only show the DNS server as started.
Well, as I writing this I opened up a DOS prompt and started pinging again. Now I can ping ap and it will auto-resolve to ap.mydomain.com and ping successfully.
Maybe it just some time for things to work after I made the change. Who knows? I will test periodically to see if it keeps working. Like I said before, it's been intermittent.
I will monitor for a day or so and close it out. Thanks for you help.

 

by: kbbcnetPosted on 2005-08-26 at 20:23:25ID: 14766628

It may be a good idea to verify the etc\Hosts files info -- nothing weird.

The Hosts files by default will have only one entry --
#
127.0.0.1      localhost

 

by: photograffitiPosted on 2005-08-26 at 20:27:51ID: 14766635

Yeah, hosts file is clear. I checked that first. As for DHCP, the client is getting all the right settings from the DHCP server. I only have a few things configured in the DHCP scope. The router, the DNS servers (two of them), and the DNS domain name.

 

by: kbbcnetPosted on 2005-08-26 at 20:51:37ID: 14766663

<<Maybe it just some time for things to work after I made the change.>>
Yes, propagation can take some time.

And as you said "intermittent" complicates the issue.
----------------------------------------

/ Run netstat -ano;   netstat -abnov  <-- look for some foreign process &/or executible.
/ Run nbtstat -n;  <-- Get Unique name for host file below.
/ Run nbtstat -c; -r;  <-- look for IPs in cache & resolution.

If you continue to have the intermittent issue -- Let's test by adding hosts to the Hosts file & see if the problem continues.
C:\WINDOWS\system32\drivers\etc\hosts|
#
127.0.0.1      localhost
10.10.10.2    Pc host name
10.10.10.3    Pc2 host name    <-- etc.

 

by: calvinetterPosted on 2005-08-27 at 15:45:39ID: 14769292

>Maybe it just some time for things to work after I made the change.
If you're already aware of this, please disregard, but on W2k/XP, these are the default DNS cache timeouts:
DNS lookup successful - 1 day
DNS lookup failed - 5 minutes

>The domain name is a valid domain-name but the NS record still points to a public DNS server, not mine. My server is only for internal use
Could you clarify? Seeing your screenshot, I'm curious if the domain name "___group.com" is a 'real', registered DNS domain name.  Having a local Active Directory domain name the same as a "real, outside" DNS domain can cause local DNS resolution problems, but probably you already knew this?

If you already have forwarding setup on your DC, I highly recommend setting your workstation(s) to *only* point to your local DC for all DNS resolution (you'll want to also change the DHCP settings).  Also, please double-check the TCP/IP properties on your DC: the DC's NIC properties should have a single IP for its DNS entry: itself (either the loopback or it's normal IP).  After making any changes to the DNS config on the DC, it's a good idea to flush the DNS cache on the DC (& any workstation having resolution problems) & restart the DNS service.

cheers

 

by: photograffitiPosted on 2005-08-27 at 20:16:59ID: 14769819

The domain name is a real, registered domain name though I'm the only one that uses it. It is also my AD domain name. I know MS suggets you use .local or .loc for internal domain name but not quite sure why.
My DC does only have a single IP in its own TCP/IP DNS settings and that is itself... not the loopback. I will change my DHCP settings to remove the secondary server.
Thanks.

 

by: photograffitiPosted on 2005-08-28 at 19:14:38ID: 14773556

It's still working today so I guess this solved my problem. I'll keep my fingers crossed. Thanks a lot for your help.

 

by: kbbcnetPosted on 2005-08-28 at 20:45:56ID: 14773811

Ok - good news!  And Nice Job!!! :)   Glad you got your resolve!

20120131-EE-VQP-002

3 Ways to Join

30-Day Free Trial

The Experts

98% positive feedback on 31,087 answers since March 2000. angeliii is a Microsoft Most Valuable Professional for his work with MS SQL Server & Develoment.

He has also proven his knowledge of Visual Basic Programming, PHP Scripting and Oracle Databases.

The Experts

97% positive feedback on 10,752 answers since July 2000. lrmoore has more than 18 years experience in the networking industry.

The six-time Mircosoft MVPs specialties include firewalls, virtual private networking, and network management.

Testimonials

"...and excellent source for support... Kind of like having your very own IT dept." Electriciansnet

Testimonials

"I was apprehensive at signing up at first. However... it has already made my life as an IT administrator much easier." JaCrews

Testimonials

"WOW! You guys have great, active, and knowledgeable people on here." moore50

Business Clients

Business Clients

In the Press

"If you’ve got a question... Experts Exchange can supply an answer.”

In the Press

"...an invaluable aid for both IT professionals and those who require tech support."

In the Press

"where IT professionals provide quick answers on just about any topic"

Business Account Plans

Loading Advertisement...