DNS does not resolve correctly via VPN

Our customers use VPN to RDP into their respective workstations on occasion to work. We recently discovered that we can't ping or RDP to computer names; however the FQDN for workstations does work.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

2 options I think will solve this.

Setup WINs
Or make sure that there is a DNS suffix configured in the TCP/IP v4 settings on the users computer.  This will be on the Advanced area at the DNS tab.

Add your domain suffix.  Then when they need to access by name it will use the suffix to form a FQDN for dns resolution.
MIT-TechsAuthor Commented:
WINS is configured on the server, but still unable to ping or connect to anything by name.
what type of VPN are you using.  the VPN client may not be using WINs or may not be able to use the WINs through the tunnel.  

The DNS suffix should make it work if that is possible to configure.
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

in the WINs manager can you see the entries for the workstations in there.  Are they registering automatically with WINs?

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
MIT-TechsAuthor Commented:
Windows PPTP VPN.

It worked for almost a year. We recently decommissioned a domain controller that was the DHCP/DNS server. The new DHCP/DNS server is Server 2008 and everything seems to be configured correct.

DNS is AD integrated BTW and the DHCP is authorized in AD as well.
MIT-TechsAuthor Commented:
How do I get to the WINS manager in server 2008 r2?
It should be located in the Administrative Tools area

You should also be able to load the mmc console and then add the snapin for it.
in the DHCP service you may need to specify the WINS server as a scope option
Also, check in your Routing and Remote Access, Server Properties on the IP tab

look for a checkbox for Broadcast Name resolution and verify it is enabled.
As part of the pptp configuration on the client, make sure that the LAN dns servers are listed as well as add as other experts pointed out the LAN ad domain into the list.
MIT-TechsAuthor Commented:
I checked the WINS manager and found the service was not working. I removed and re-added the service. All seems to be working now. Thank you for your help!
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

From novice to tech pro — start learning today.