Cannot access clients connected to the network via OpenVPN



  • Hi all, i just got OpenVPN Up and running, I'd like to start off by applauding what a fantastic piece of software this is.

    So, my issue today is that when clients are connecting to the VPN They are able to access shares on the network and everything with absolutely no problem. However, The situation does arise where i will be required to have access to shares on these client computers as well as remote desktop and the like.

    The basic rundown of it is

    Client A Connects to the VPN. Client A Can Access Shares, Internal Websites, Remote Desktop of servers, And all that

    But if I try and connect To Client A while he's on the VPN…....for example by going to \CLIENT-A\C$ Or remote desktoping CLIENT-A

    NO DICE!

    It has been tested and I can connect to CLIENT-A If their actually on the local network physically.....

    I Can Ping CLIENT-A Both From the VPN and when they are Physically on the network.

    I have disabled windows firewall while they are connected to the VPN to try and make a connection with no avail. In my Server configuration I have enabled the "Enable NetBIOS over TCP/IP" Option as well as "Inter-client communication" and none of it helped at all. My firewall rules are in place to allow anything from open vpn to anything both inbound and outbound (yes im sure they are correct) so now that i've hit the inevitable road block..........Does anyone have any ideas?



  • Have you tried the connection by hostname and by the clients VPN IP to find out if the problem is the NetBIOS?

    Consider that Windows handles access from other network very restrictedly. As I remember, deactivating Windows firewall doesn't ever help.
    To make the VPN network reliable in Windows I did a trick on my VPN server: I push the default route to the clients, but with a high metric, so it doesn't override the clients default route. So if windows has configured a gateway for an network interface it handles the connection as reliable.



  • Have you tried the connection by hostname and by the clients VPN IP to find out if the problem is the NetBIOS?

    Yes I have, and the connection will not  work via ip either.

    I did a trick on my VPN server: I push the default route to the clients, but with a high metric, so it doesn't override the clients default route. So if windows has configured a gateway for an network interface it handles the connection as reliable.

    Can you be so kind as to provide an example of how you went about doing that?

    Thanks.



  • @networknut:

    Have you tried the connection by hostname and by the clients VPN IP to find out if the problem is the NetBIOS?

    Yes I have

    So it doesn't work in both ways?

    @networknut:

    I did a trick on my VPN server: I push the default route to the clients, but with a high metric, so it doesn't override the clients default route. So if windows has configured a gateway for an network interface it handles the connection as reliable.

    Can you be so kind as to provide an example of how you went about doing that?

    In the server advanced configuration section > custom options field I entered

    push "route-metric 512";push "route 0.0.0.0 0.0.0.0"
    

    However, the metric option entered here is also applied for any route, which are pushed to the clients, but no matter since there is no other route for this destination on the client with lower metric. So the route option could as well be set by entering "0.0.0.0/0" in the Locale Network(s) field above.


Log in to reply