Hey all, first I wanna say hi and thank you for taking the time to read this and give me your advice.
I'm testing with ovpn between two XP machines. The goal was to map a networked drive from one PC to the other at the office. I managed to establish a connection between the two after much trial and error.. But unable to establish or even find the shared folders, I started over attempting a bridged connection. That ended up not working for me, so I went back to my initial configuration. Now the server connects fine, but the other PC refuses to connect - keeps giving me "timeout" and "cannot reach" one after another in the log. I'm using the stable community version of 2.0. Here are the configs:
######
#Server#
######
proto tcp
port 1194
dev tun
dev-node vpn
ca ca.crt
cert rokitto.crt
key rokitto.key # This file should be kept secret
dh dh1024.pem
server 192.168.10.0 255.255.255.0
push "route 192.168.10.109 255.255.255.252"
#^ this I added in an attempt to include the network my shared docs... Not sure if it'll work.
ifconfig-pool-persist ipp.txt
keepalive 10 120
comp-lzo
persist-key
persist-tun
status openvpn-status.log
verb 3
######
#client#
######
client
proto tcp
dev tun
remote 72.129.88.241 1194
resolv-retry infinite
nobind
persist-key
persist-tun
ca ca.crt
cert user.crt
key user.key
;ns-cert-type server
comp-lzo
verb 3
mute 5
previously functional VPN wont connect now
Moderators: TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech
Forum rules
Please visit (and READ) the OpenVPN HowTo http://openvpn.net/howto prior to asking any questions in here!
Please visit (and READ) the OpenVPN HowTo http://openvpn.net/howto prior to asking any questions in here!
-
- OpenVpn Newbie
- Posts: 1
- Joined: Fri Nov 12, 2010 9:25 pm
- krzee
- Forum Team
- Posts: 728
- Joined: Fri Aug 29, 2008 5:42 pm
Re: previously functional VPN wont connect now
Code: Select all
push "route 192.168.10.109 255.255.255.252"
ifconfig-pool-persist ipp.txt
if still needed, post logs with verb 5
as for your problem with netbios resolution...
run a WINS server, or access the share by IP instead of by netbios name