- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
VPN tunnel connected but cannot map
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
VPN tunnel connected but cannot map
I am using VPNClientPro_v6.12.001 and have Windows 10 on my home computer. The VPN tunnel is open to my server at work (Windows Server 2008 R2)and is sending and receiving. I cannot map the Public folder on my desktop. My laptop is connected via tunnel to the server so issue is I cannot create a new connection. The existing mapping to http://192.168.x.xx/public will not work as a new connection but established connection works.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: VPN tunnel connected but cannot map
This is a Netgear ReadyNAS forum, so you are posting in the wrong place. ProSafe issues should be posted in Business Solutions
Please repost there
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: VPN tunnel connected but cannot map
Hi Matt32258,
Welcome to the community!
Could you tell us if you can RDP the PC where the public folder is shared? Perhaps another PC on the other network where the tunnel is located to isolate if the problem is with the VPN connection or the PC you're trying to access.
Kind regards,
BrianL
NETGEAR Community Team
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: VPN tunnel connected but cannot map
What do you mean by "laptop is connected via tunnel to the server"?
Are you using the Netgear VPN client for this connection?
Is the Netegar VPN Client IPSec tunnel terminating on a Netgear router, another brand of router, or directly on the server?