On the VPN'd computer, you have an issue with name resolution. You MAY be able to attach with a fully qualified name, if you can do normal DNS resolution, and that DNS server has registered the names of the Windows resources you want to see. (for instance, you may be able to connect to server1.mydomain.com, but not to just server1). Verify the ipconfig /all output on a workstation on the network segment with the server, and the remote server - are the same DNS servers in use, and is there a WINS server on the network?
Even though you have NetBIOS over VPN enabled, do you have the correct WINS entries on the PC? If all else fails, WINS will broadcast out for name resolution, but since you're on a VPN that broadcast will stop once it hits a L3 device. Also, to connect to the shared directories there needs to be a name to ip mapping (either via WINS or DNS) that your PC can reference; if you can't resolve a name (try pinging the name to see if it comes back with an ip) it won't connect to it.
Hello, This article will describe how to configure PPTP VPN on the new
RV340/345 routers from the Small Business series. RV340/345
Configuration The first step is to enable the PPTP Server: Go to VPN ->
PPTP Server Change PPTP Server: from Off to On Selec...
Article ID:5748 Use TheGreenBow VPN Client to Connect with RV34x Series
Router Introduction A Virtual Private Network (VPN) connection allows
users to access, send, and receive data to and from a private network by
means of going through a public or share...
Article ID:5728 Configure a Teleworker VPN Client on the RV34x Series
Router Objective The Teleworker VPN Client feature minimizes the
configuration requirements at remote locations by allowing the device to
work as a Cisco VPN hardware client. When the T...