Connection Failed

Business solution to host your own OpenVPN server with web management interface and bundled clients.
Locked
randyman
OpenVpn Newbie
Posts: 2
Joined: Wed Jan 18, 2017 7:39 pm

Connection Failed

Post by randyman » Wed Jan 18, 2017 7:57 pm

I setup a new laptop for one of my drivers to connect to my Windows Server 2008 R2 and VMWare. It has worked perfectly for 4 or 5 months. Now when I try to connect using Remote Desktop it fails. I have setup Openvpn as a service and even though I log into 2008 server and download the user windows installer, install it (after uninstall) I can not connect. I know it is something simple and it is probably caused by windows. I am using windows 10 on every machine that is used to connect to the server. Essentially nothing has changed except being able to connect.

I can usually fix it by uninstalling and re-installing but it isn't helping this time. If someone could point me in the right direction I would greatly appreciate it.

Thank you,
Randyman

TinCanTech
OpenVPN Protagonist
Posts: 11137
Joined: Fri Jun 03, 2016 1:17 pm

Re: Connection Failed

Post by TinCanTech » Wed Jan 18, 2017 8:10 pm


randyman
OpenVpn Newbie
Posts: 2
Joined: Wed Jan 18, 2017 7:39 pm

Re: Connection Failed

Post by randyman » Thu Jan 19, 2017 3:15 pm

Thank you TinCanTech. It actually turns out that the Default.rdp saved file must have been corrupt. I deleted it and clicked on Remote Desktop Connection, re-entered my credentials and everything works properly now.

Hope this might help someone else.

Thanks again.

Sorry, I inadvertently posted this answer in the wrong post and can't figure out how to delete it.

Pernicles
OpenVpn Newbie
Posts: 1
Joined: Fri Feb 10, 2017 7:57 pm

Re: Connection Failed

Post by Pernicles » Fri Feb 10, 2017 8:06 pm

Hi. My name is Fernando Pernes and i install pivpn on raspberry pi 3. It install correctly and i have tuunelblick on mac book pro with sierra 10.12.3
I put client vpn correctly and he said that :The apparent public IP address did not change after connecting homepi. It continues to be connected to xx.xxx.xx.xxx.
This may mean that the VPN is not configured correctly, and the log file is:

*Tunnelblick: OS X 10.12.3; Tunnelblick 3.7.0 (build 4790)
2017-02-10 19:47:23 *Tunnelblick: Attempting connection with homepi; Set nameserver = 769; monitoring connection
2017-02-10 19:47:23 *Tunnelblick: openvpnstart start homepi.tblk 1338 769 0 3 0 1065264 -ptADGNWradsgnw 2.3.14-openssl-1.0.2k
2017-02-10 19:47:23 *Tunnelblick: openvpnstart log:
OpenVPN started successfully. Command used to start OpenVPN (one argument per displayed line):

/Applications/Tunnelblick.app/Contents/Resources/openvpn/openvpn-2.3.14-openssl-1.0.2k/openvpn
--daemon
--log
/Library/Application Support/Tunnelblick/Logs/-SLibrary-SApplication Support-STunnelblick-SShared-Shomepi.tblk-SContents-SResources-Sconfig.ovpn.769_0_3_0_1065264.1338.openvpn.log
--cd
/Library/Application Support/Tunnelblick/Shared/homepi.tblk/Contents/Resources
--verb
3
--config
/Library/Application Support/Tunnelblick/Shared/homepi.tblk/Contents/Resources/config.ovpn
--verb
3
--cd
/Library/Application Support/Tunnelblick/Shared/homepi.tblk/Contents/Resources
--management
127.0.0.1
1338
--management-query-passwords
--management-hold
--script-security
2
--up
/Applications/Tunnelblick.app/Contents/Resources/client.up.tunnelblick.sh -9 -d -f -m -w -ptADGNWradsgnw
--down
/Applications/Tunnelblick.app/Contents/Resources/client.down.tunnelblick.sh -9 -d -f -m -w -ptADGNWradsgnw

2017-02-10 19:47:23 *Tunnelblick: openvpnstart starting OpenVPN
2017-02-10 19:47:23 *Tunnelblick: Established communication with OpenVPN
2017-02-10 19:47:23 OpenVPN 2.3.14 x86_64-apple-darwin [SSL (OpenSSL)] [LZO] [PKCS11] [MH] [IPv6] built on Jan 28 2017
2017-02-10 19:47:23 library versions: OpenSSL 1.0.2k 26 Jan 2017, LZO 2.09
2017-02-10 19:47:23 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:1338
2017-02-10 19:47:23 Need hold release from management interface, waiting...
2017-02-10 19:47:23 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:1338
2017-02-10 19:47:23 MANAGEMENT: CMD 'pid'
2017-02-10 19:47:23 MANAGEMENT: CMD 'state on'
2017-02-10 19:47:23 MANAGEMENT: CMD 'state'
2017-02-10 19:47:23 MANAGEMENT: CMD 'bytecount 1'
2017-02-10 19:47:23 MANAGEMENT: CMD 'hold release'
2017-02-10 19:47:23 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2017-02-10 19:47:28 MANAGEMENT: CMD 'password [...]'
2017-02-10 19:47:28 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
2017-02-10 19:47:28 Control Channel Authentication: tls-auth using INLINE static key file
2017-02-10 19:47:28 Outgoing Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
2017-02-10 19:47:28 Incoming Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
2017-02-10 19:47:28 Socket Buffers: R=[196724->196724] S=[9216->9216]
2017-02-10 19:47:28 UDPv4 link local: [undef]
2017-02-10 19:47:28 UDPv4 link remote: [AF_INET]85.247.34.209:1194
2017-02-10 19:47:28 MANAGEMENT: >STATE:1486756048,WAIT,,,
2017-02-10 19:47:28 MANAGEMENT: >STATE:1486756048,AUTH,,,
2017-02-10 19:47:28 TLS: Initial packet from [AF_INET]85.247.34.209:1194, sid=002dae96 b125b270
2017-02-10 19:47:29 VERIFY OK: depth=1, CN=ChangeMe
2017-02-10 19:47:29 Validating certificate key usage
2017-02-10 19:47:29 ++ Certificate has key usage 00a0, expects 00a0
2017-02-10 19:47:29 VERIFY KU OK
2017-02-10 19:47:29 Validating certificate extended key usage
2017-02-10 19:47:29 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
2017-02-10 19:47:29 VERIFY EKU OK
2017-02-10 19:47:29 VERIFY X509NAME OK: CN=server
2017-02-10 19:47:29 VERIFY OK: depth=0, CN=server
2017-02-10 19:47:29 Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
2017-02-10 19:47:29 Data Channel Encrypt: Using 256 bit message hash 'SHA256' for HMAC authentication
2017-02-10 19:47:29 Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
2017-02-10 19:47:29 Data Channel Decrypt: Using 256 bit message hash 'SHA256' for HMAC authentication
2017-02-10 19:47:29 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
2017-02-10 19:47:29 [server] Peer Connection Initiated with [AF_INET]85.247.34.209:1194
2017-02-10 19:47:30 MANAGEMENT: >STATE:1486756050,GET_CONFIG,,,
2017-02-10 19:47:31 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
2017-02-10 19:47:31 PUSH: Received control message: 'PUSH_REPLY,route 10.8.0.1 255.255.255.255,route 10.8.0.0 255.255.255.0,route 192.168.1.0 255.255.255.0,dhcp-option DNS 8.8.8.8,dhcp-option DNS 8.8.4.4,redirect-gateway def1,route-gateway 10.8.0.1,topology subnet,ping 10,ping-restart 120,ifconfig 10.8.0.3 255.255.255.0'
2017-02-10 19:47:31 OPTIONS IMPORT: timers and/or timeouts modified
2017-02-10 19:47:31 OPTIONS IMPORT: --ifconfig/up options modified
2017-02-10 19:47:31 OPTIONS IMPORT: route options modified
2017-02-10 19:47:31 OPTIONS IMPORT: route-related options modified
2017-02-10 19:47:31 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
2017-02-10 19:47:31 Opening utun (connect(AF_SYS_CONTROL)): Resource busy
2017-02-10 19:47:31 Opened utun device utun1
2017-02-10 19:47:31 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
2017-02-10 19:47:31 MANAGEMENT: >STATE:1486756051,ASSIGN_IP,,10.8.0.3,
2017-02-10 19:47:31 /sbin/ifconfig utun1 delete
ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address
2017-02-10 19:47:31 NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure
2017-02-10 19:47:31 /sbin/ifconfig utun1 10.8.0.3 10.8.0.3 netmask 255.255.255.0 mtu 1500 up
2017-02-10 19:47:31 /sbin/route add -net 10.8.0.0 10.8.0.3 255.255.255.0
add net 10.8.0.0: gateway 10.8.0.3
2017-02-10 19:47:31 /Applications/Tunnelblick.app/Contents/Resources/client.up.tunnelblick.sh -9 -d -f -m -w -ptADGNWradsgnw utun1 1500 1570 10.8.0.3 255.255.255.0 init
**********************************************
Start of output from client.up.tunnelblick.sh
Retrieved from OpenVPN: name server(s) [ 8.8.8.8 8.8.4.4 ], search domain(s) [ ] and SMB server(s) [ ] and using default domain name [ openvpn ]
Not aggregating ServerAddresses because running on OS X 10.6 or higher
Setting search domains to 'openvpn' because running under OS X 10.6 or higher and the search domains were not set manually and 'Prepend domain name to search domains' was not selected
Saved the DNS and SMB configurations so they can be restored
Changed DNS ServerAddresses setting from '192.168.1.1 0.0.0.0' to '8.8.8.8 8.8.4.4'
Changed DNS SearchDomains setting from '' to 'openvpn'
Changed DNS DomainName setting from '' to 'openvpn'
Did not change SMB NetBIOSName setting of ''
Did not change SMB Workgroup setting of ''
Did not change SMB WINSAddresses setting of ''
DNS servers '8.8.8.8 8.8.4.4' will be used for DNS queries when the VPN is active
The DNS servers include only free public DNS servers known to Tunnelblick.
Flushed the DNS cache via dscacheutil
/usr/sbin/discoveryutil not present. Not flushing the DNS cache via discoveryutil
Notified mDNSResponder that the DNS cache was flushed
Setting up to monitor system configuration with process-network-changes
End of output from client.up.tunnelblick.sh
**********************************************
2017-02-10 19:47:35 *Tunnelblick: No 'connected.sh' script to execute
2017-02-10 19:47:35 /sbin/route add -net 85.247.34.209 192.168.1.1 255.255.255.255
add net 85.247.34.209: gateway 192.168.1.1
2017-02-10 19:47:35 /sbin/route add -net 0.0.0.0 10.8.0.1 128.0.0.0
add net 0.0.0.0: gateway 10.8.0.1
2017-02-10 19:47:35 /sbin/route add -net 128.0.0.0 10.8.0.1 128.0.0.0
add net 128.0.0.0: gateway 10.8.0.1
2017-02-10 19:47:35 MANAGEMENT: >STATE:1486756055,ADD_ROUTES,,,
2017-02-10 19:47:35 /sbin/route add -net 10.8.0.1 10.8.0.1 255.255.255.255
route: writing to routing socket: Can't assign requested address
add net 10.8.0.1: gateway 10.8.0.1: Can't assign requested address
2017-02-10 19:47:35 /sbin/route add -net 10.8.0.0 10.8.0.1 255.255.255.0
route: writing to routing socket: File exists
add net 10.8.0.0: gateway 10.8.0.1: File exists
2017-02-10 19:47:35 /sbin/route add -net 192.168.1.0 10.8.0.1 255.255.255.0
add net 192.168.1.0: gateway 10.8.0.1
2017-02-10 19:47:35 Initialization Sequence Completed
2017-02-10 19:47:35 MANAGEMENT: >STATE:1486756055,CONNECTED,SUCCESS,10.8.0.3,85.247.34.209
2017-02-10 19:47:40 *Tunnelblick process-network-changes: A system configuration change was ignored
2017-02-10 19:47:43 *Tunnelblick: This computer's apparent public IP address (85.247.34.209) was unchanged after the connection was made



Can you help me?

TinCanTech
OpenVPN Protagonist
Posts: 11137
Joined: Fri Jun 03, 2016 1:17 pm

Re: Connection Failed

Post by TinCanTech » Fri Feb 10, 2017 10:47 pm

TinCanTech wrote:Please see:
HOWTO: Request Help !

Locked