Workstation having trouble pinging certain devices by name

I have one user's workstation that from time to time has trouble connecting via Remote Desktop to some (not all) of our Windows Server by name.  I tested connectivity using ping.  From his workstation, I could ping these servers by IP address.  I could not ping the servers by their DNS server name.  Out of the 5 servers I tested, the workstation only had trouble pinging 2 of them by name, so it is not like DNS was completely dysfunctional.  He is pointing to our Active Directory Domain Controller as his primary DNS and then has a secondary DNS to our Internet providers DNS server in case our DC ever goes down.  This same config is in place on all of our workstations as far as I know.  Both times that this has happened (several weeks apart), I can run an ipconfig /flushdns and everything is back to normal.  The workstation is Windows 7 Pro 64-bit.  Any ideas?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Probably a latency issue... DC is not responding fast enough & the name is not resolving at the ISP.

I would try troubleshooting the slow response from  the DC (bad cable, or switch port) as the probable culprit!
Rob WilliamsCommented:
>>"has a secondary DNS to our Internet providers DNS server in case our DC ever goes down"
Most common error in configuring DNS.
ONLY point to your internal DNS server/s.  Yes when they are not available internet access fails.
Having the ISP, or a router, as the alternate results in slow logons and failed name resolution issues.
sswlewnixAuthor Commented:
Both of these are helpful.  I do have some additional information that your responses reminded me of -

1 - The only workstation that I know of that this is happening on is behind a local 4 port mini-switch/hub in the users office that is also providing network access for a printer and a Verizon Wireless Network Extender.  So, this could create the latency issue described by n2fc.  Long term I am going to look into getting extra cat 5 pulls to this office to eliminate the mini-switch.

2 - We have the ISP DNS as secondary on most (if not all of our workstations), and we don't seem to be having issues except on this one.  I see the point that we need to move away from this, so we will also work toward that.

As a short term fix, I while searching on Google, I saw some references to disabling negative DNS caching on the workstation.  Have you all had any experience with that and would you recommend it as a band aid until the cabling is done?

Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

Rob WilliamsCommented:
Regarding the secondary DNS, try removing the secondary then run  ipconfig /flushdns   see if there is an improvement.
There are literally thousands of questions on Experts exchange where slow logons and failed internal DNS requests were resolved by doing so.
The problem is often the secondary is contacted rather than the primary, despite what should happen.  When this happens of course your ISP cannot resolve the name of the PC or server and you get a failure or delay until the primary is tried.

As mentioned #1 DNS mistake:
"10 DNS errors that will kill your network"
Rob WilliamsCommented:
Sorry I missed the other parts of the problem.

Disabling negative DNS  addresses the symptoms not the problem.  Why are the DNS requests failing.

Latency issues:  Easy enough to try another switch, but I spent 4 years as a network infrastructure troubleshooter and cabling is the number one cause.  Unlike a phone connection that works or doesn't, a working network connection that was poorly terminated, or a cable that was stretched, kinked, or in close proximity to EMI can reduce performance by 90%.  Do you only have DNS issues or is network performance poor in general?

Again the secondary DNS is not a suggestion but factually a wrong configuration in a domain environment.
sswlewnixAuthor Commented:
We have no noticeable problems with network performance.  The only thing I have noticed is this one workstation's inability to connect by name to a couple of our terminal servers and only a couple of times in the past 3 months.  Most of our users connect to these same terminal servers daily and never report issues to us.  The DC does not have any references to external ISP DNS servers (I am using root hints for Internet DNS resolution).   On the workstation that has the issue,  an ipconfig /flushdns resolves the problem immediately every time.  I agree that disabling negative DNS caching doesn't fix the problem.  So, I am not going to do that yet.  I am mainly looking for ideas of problems that would just involve a single PC having issues rather than an overall network issue.  Although they may end up being one and the same.
Rob WilliamsCommented:
Why a single PC I have no idea but if ipconfig /flushdns  solves the problem it is definitely due to failed DNS.

Why are you not willing to try removing secondary for a while?

>>"The DC does not have any references to external ISP DNS servers (I am using root hints for Internet DNS resolution)"
That is fine.  Some people like forwarders, some root hints, I personally believe both work well.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sswlewnixAuthor Commented:
I will remove the secondary DNS on this one PC and see what happens.  Since it is kind of intermittent, it might take a while to see if it makes a difference.  

Thanks for the help!
Rob WilliamsCommented:
It would be interesting to see if you find an improvement.
Thanks sswlewnix.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Internet Protocols

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.