Mapping network drive through OpenVPN Tomato Router

[deleted]

I have a Netgear Tomato router OpenVPN server, with Push LAN to clients, TUN and UDP in basic settings.

Client connects fine to OpenVPN server router, shows VPN subnet IP, and the RDP connects to server using normal internal LAN and port.

But the client cannot map network drives from the file server and no network browse results. Tried \\server\files on the remote VPN client with no luck.

Local computers on LAN see shared network drives no prob.

Is there another server or client config command to allow OpenVPN clients to see shared folders/mapped drives on the LAN behind the OpenVPN server router?

Is it a TAP/TUN problem, network bridging issue, another custom config?

Thank You

[deleted]

All Computers are Win 10
Tomato Firmware 1.28.0000 -3.5-140 K26ARM USB AIO-64K

TinCanTech

Paul6 wrote Tried \\server\files on the remote VPN client with no luck.

Try

net use x: \\ip.add.re.ss\share_name

[deleted]

I replaced ip.add.re.ss with my server LAN IP address
Then replaced share_name with server\files, and just files

I got "System error 67 has occurred. The network name cannot be found"

Somehow RDP can find the server using internal LAN and port, but Win 10 cannot find network folders behind OpenVPN router. bizzare.

I am going to try this, but I only really want the file server network folders to be found and mapped.

https://openvpn.net/community-resources/expanding-the-scope-of-the-vpn-to-include-additional-machines-on-either-the-client-or-server-subnet/

TinCanTech

Microsoft do not care what you want

Microsoft only care about what (((they))) want...

[deleted]

SOLVED USING TAP - ( but is this really the root cause, or even a good solution? )

Here is what i did

1. I changed Interface setting to TAP in the Tomato Router basic OpenVPN setting
2. The router menu then changed to show and extra option "Bridge TAP LAN Br01 default" and I left this alone
3.The "Push LAN to clients" in advanced settings disappeared by itself
4. Router menu option "client address pool - DHCP" ticked.
5. Removed # route 192.xxx.x.x 255.255.255.0 vpn_gateway 3 from client config, as it was causing an error message in the log. The client OpenVPN log status now shows "extracted DHCP router address:192.xxx.x.x" I think the router DHCP is doing this now.

Checking with CMD Net Use reveals status ok on all mapped drives, and have full access as if client was on internal LAN. ( In fact, these were created while in the LAN, so no need to created again over VPN )

But it would be nice to fix the blank Assigned IP in Win 10 pop up bubble and the open VPN icon?
Previously with TUN, notification popped up with a VPN subnet address, ie 10.8.0.1
To check what the actual IP actually was, I went in to the router device list, and now saw the VPN client was leased an internal network IP address.

Nearly there now, just need help to make the Assigned IP: 192.xxx.x.x visible for client

Thank You