Cannot connect to LAN computer via VPN

[shazman]

I am having a VPN issue where by, I am able to connect via VPN but only able to access the dashboard of the Zentayl server and also Windows Explorer. I need to access computers and services on the LAN but I cannot connect not even using the IP addresses of the computers that I wish to connect to. The LAN network is configured in Advertised Network automatically.

Zentyal Server version 2.0.23
In windows explorer I see all the machines listed on the LAN but when I click on the one I need access to or any other than the server I get Windows cannot access \\computername error code 0x80070035
Any help will be greatly appreciated.
Thanks

[christian]

May I suggest you check DNS: are you sure, while using VPN, that DNS you rely on contains IP for machines you want to connect to?

[shazman]

Thanks for you fast response,
I have been tinkering with DNS trying to get it work but so far no luck...
More Info
The LAN network is 192.168.0.0 and the VPN issues 192.168.160.0 getting from 192.168.160.0 to 192.168.0.0 is where I am having the issue is seems. Now what DNS change exactly should I make? on the server or my remote pc? or both or something else? I cannot ping the 192.168.0.0 network which is in the advertised networks as mentioned. My understanding is that I should be able to connect via the IP without having to use DNS.. unless I need more understanding 
Thanks a mill
 

[christian]

indeed DNS is not required if you only access IP addresses but when it comes to connect to Windows using UNC, this might be required.
in such case, you will have to add your "internal" DNS to your client connecting remotely.

I'm a bit confused with

The LAN network is 192.168.0.0 and the VPN issues 192.168.160.0 getting from 192.168.160.0 to 192.168.0.0 is where I am having the issue is seems

192.168.160.0 is the VPN network, connecting you to Zentyal server.
Advertising 192.168.0.0 means that remote client, once connected through VPN, knows that route to 192.168.0.0 is through VPN network.

Is your Zentyal server the default route for internal machines? If not, they don't know route to 192.168.160.0

[shazman]

Correct Zentyal is configure as the default gateway

[shazman]

Thanks so far... I will continue tomorrow, any other suggestions will be greatly appreciated.

[shazman]

Hi folks, does anyone have any advice?
I noticed in the OpenVPN Daemons section on the dashboard the "Client" sub section the service is disabled. Does this mean I missed something?
Thanks again

[jsalamero]

Which version of Windows are you using? This is unlikely to be a server issue but a client side thing.

[shazman]

Windows 7 Ultimate 64

[shazman]

Any more advice... ?

I did some updates and no luck. I am thinking of updating to 2.2

Thanks

[BrunovonTroba]

Create 2 objects and 1 rule in firewall:
1: object "LAN" with member "LAN_IP", in field IP address 192.168.0.0/24 (all LAN subnet members with IP 192.168.0.1-254)
2: object "VPN" With member "VPN_IP", in field IP address 192.168.160.0/24 (all vpn subnet members with IP 192.168.160.1-254)
3: firewall rule in FIREWALL -> Packet filtration -> Rules for internal networks -> add new: allow source object VPN target object LAN service ANY