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.
MIT-TechsAsked:
Who is Participating?
 
chakkoConnect With a Mentor Commented:
in the WINs manager can you see the entries for the workstations in there.  Are they registering automatically with WINs?
0
 
chakkoCommented:
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.
0
 
MIT-TechsAuthor Commented:
WINS is configured on the server, but still unable to ping or connect to anything by name.
0
Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

 
chakkoCommented:
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.
0
 
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.
0
 
MIT-TechsAuthor Commented:
How do I get to the WINS manager in server 2008 r2?
0
 
chakkoCommented:
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.
0
 
chakkoCommented:
in the DHCP service you may need to specify the WINS server as a scope option
0
 
chakkoCommented:
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.
0
 
arnoldCommented:
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.
0
 
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!
0
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.

All Courses

From novice to tech pro — start learning today.