Page 1 of 1

Openvpn and Amazon EC2 with Windows 2008

Posted: Fri Oct 08, 2010 1:58 pm
by nadin
I was wondering if anyone has had problems running open vpn on windows 2008 Amazon ebs/ami image.

I have a vpn server running on a windows 2003 ec2 instance as well as two other 2003 instances that are connecting as clients. I also have several Windows 7 machines all connecting to the vpn server.

However the issue I have been having is with a windows 2008 ami/ebs instance. The client will connect, however I am not able to ping any of the other clients on the vpn (which I can from other machines). I am able to only ping (4-5 pings) while the initial connection is being established. Then all the pings time out (to and from the server). I have tried to use the various ip-win32 options as well.

Anyone have any idea as to what is going on?

I have tried openvpn 2.1.1,2.1rc22 and 2.2

I posted here as well with no help.
http://www.pubbs.net/201001/openvpn/109 ... lient.html

Re: Openvpn and Amazon EC2 with Windows 2008

Posted: Fri Oct 08, 2010 5:27 pm
by krzee
**Post your configs from client and server, without comments. you can strip comments in linux/bsd with something like this:
grep -vE '^#|^;|^$' server.conf

Re: Openvpn and Amazon EC2 with Windows 2008

Posted: Tue Oct 12, 2010 3:56 am
by nadin
Server.config

Code: Select all

port 1194
proto udp
dev tun
ca xx.crt
cert xxx.crt
key xxx.key  
dh dh1024.pem
server 10.8.0.0 255.255.255.0
ifconfig-pool-persist ipp.txt
client-config-dir ccd
client-to-client
keepalive 10 30
tls-auth xxxx.key 0 
comp-lzo
persist-key
persist-tun
status openvpn-status.log
verb 2
client config

Code: Select all

client
dev tun
proto udp
remote XXXXX 1194
resolv-retry infinite
nobind
persist-key
persist-tun
ca xx.crt
cert xxx.crt
key xxx.key
ns-cert-type server
tls-auth xxxx 1
comp-lzo
verb 3
;ip-win32 netsh 

Re: Openvpn and Amazon EC2 with Windows 2008

Posted: Wed Oct 13, 2010 9:13 pm
by krzee
Please post logs from client and server at verb 5
the client should be from start to dropped connection
the server should be from first packet of client to dropped connection

more is better than less