Unable to ping netbios name of remote pc - I can ping its IP address - WHY?

Why can't I ping the netbios name of a pc that is not part of my local domain?  It is a workgroup remote pc that is connected via a WAN link.  It is pointed to my local DNS server and that doesn't seem to help.

What am I missing?

patrickmillerAsked:
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.

herbusCommented:
You'll need a host record (A record,.. same thing) on your DNS server.  By saying it's pointed to your local DNS server, it sounds like the remote pc has your internal DNS server set as a primary or secondary DNS server, yeah? But DNS won't dynamically add the remote pc if it isn't a member of the domain.

Do you have DNS admin rights?  Check for, and add if needs be, the host (A) record...

Should do the trick!
0

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
bcmeyer1983Commented:
any WINS server settings specified? or lmhost files?
0
Rob WilliamsCommented:
To elaborate on the above. NetBIOS broadcasts are not routable. A WAN link would involve routers. You will need to use WINS, LMHosts, or DNS to resolve, as already suggested.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

patrickmillerAuthor Commented:
I added it to the DNS server as a Host "A" and it added the domain name to the end.   LP1262.domain.local
After a few minutes I was able to ping the name LP1262 and it finally started pinging it.   I was able to add it to the domain with netdom but....   after it rebooted I was unable to ping or access it.   The pc was definitely on the domain because the user could login and surf.   He could even ping the DNS/AD server but I could no longer ping the pc or the address.  So I removed the Host file and I am waiting to see if the DNS server ever finds it.  
0
herbusCommented:
Was it set to use a static ip address or might it have picked up a different IP with DHCP?

If you've got a user out there, can you step them through confirming the IP on the box again?
0
Rob WilliamsCommented:
Also, might you have any group policies that were applied once the machine joined the domain, such as enabling the Windows firewall ?
0
herbusCommented:
Good thinking RobWill
0
patrickmillerAuthor Commented:
I still can ping it even though it is on and running?   What gives?
0
herbusCommented:
Sorry patrick, I guess you mean you can't ping it?  ...the pc is on and running or the firewall is?  You've confirmed the IP address and that it can ping your servers, but you can't ping it?
0
patrickmillerAuthor Commented:
Static IP   I will check on the firewall
0
Rob WilliamsCommented:
Thanks patrickmiller.
Cheers !
--Rob
0
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
Windows Networking

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.