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. \\, 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?

  • Is this a site-to-site VPN or a client-to-site VPN? Nov 10, 2014 at 15:56
  • Client-to-Site ... using VPN client built into Windows 7
    – user248899
    Nov 10, 2014 at 16:21
  • 2
    Do you really need network browsing? It sure seems to me that Microsoft has mostly given up on doing anything with that.
    – Zoredache
    Nov 10, 2014 at 17:32
  • Why do you need to see the computers? I've never understood why people get so hung up on this.
    – joeqwerty
    Nov 10, 2014 at 17:55
  • If they've given up on network browsing, then why include it in the operating system at all? Was more curious than anything as to why the functionality isn't there, even though I can access the computers by typing the paths manually; Seems incomplete to me.
    – user248899
    Nov 10, 2014 at 18:05

2 Answers 2


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.


Try the following sanity checks:

You must log in to answer this question.