[OpenVPN home] [Date Prev] [Date Index] [Date Next]
[OpenVPN mailing lists] [Thread Prev] [Thread Index] [Thread Next]
Web openvpn.net

Re: [Openvpn-users] OpenVPN 2.0 - Cannot connect to machines on LAN

  • Subject: Re: [Openvpn-users] OpenVPN 2.0 - Cannot connect to machines on LAN
  • From: toby <toby711@xxxxxxxxx>
  • Date: Thu, 29 Nov 2007 09:37:40 -0600

Got it! I had push "dhcp-option WINS" instead of push "dhcp-option WINS"
I can now access via \\samba and \\
To recap, the solution was:
applying route from VPN server to samba server on samba server
enabling port forwarding on VPN server
correcting WINS entry in server.conf
What file do i edit in /etc/ that allows port forwarding on boot? I'm using RHEL4
On Nov 29, 2007 9:23 AM, Rob MacGregor <rob.macgregor@xxxxxxxxx> wrote:
On Nov 29, 2007 3:12 PM, toby <toby711@xxxxxxxxx> wrote:
> Okay, i have included route -n output from vpn server and server B (samba
> server) after doing:
> route add -net netmask gw (on server B)
> echo "1" > /proc/sys/net/ipv4/ip_forward (on VPN server/server B)

You only need the second on the VPN server, but you need to ensure
that both are part of the startup of the relevant system.
> I can now ping from VPN client ( to server B but I am unable to
> connect via \\samba from VPN client.

As Jan has just said, WINS resolution will only work if you've
configured the VPN DHCP server to hand out details of the WINS server.
 Does mapping by IP and/or DNS name work?

                Please keep list traffic on the list.

Rob MacGregor
     Whoever fights monsters should see to it that in the process he
       doesn't become a monster.                  Friedrich Nietzsche

SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
Openvpn-users mailing list