I have recently set up a Windows Server 2008 R2 with Routing and Remote Access for VPN access to our internal network from a remote location. I am able to connect with domain credentials, and group policy updates just fine.
One thing I can't quite figure out is the "network neighborhood" view is not showing internal network computers over VPN. But the share will work if I type in the UNC path i.e. \\10.1.10.200, or \\desktop-1. I have tried possible solutions such as:
- Making sure my domain controller is the primary PDC emulator.
- Enabling broadcast name resolution is checked within IPv4 settings.
- Enabling Computer Browser service.
What could be causing this? I can use nslookup and resolve all the names of vpn client machines, so what gives?
Best Answer
Network browsing across VPNs has always been problematic in my experience. If I were you I'd use a WINS server to get browsing to work (in an even remotely reliable manner). Other methods may well work, but deploying WINS is pretty straightforward and easy and, in my experience, has done the job.