fchateau I can connect to my Windows Server, but when I try to connect to SQL Server, I get a bad user name or password error. If I change the address from 10.8.0.1 to 10.8.0.2 I get a bad network error, so SQL Server knows the difference between the two addresses. I have confirmed I am entering the correct user name and password. Furthermore, if I enter the user name and password on 10.8.0.1 locally on the server, it connects fine. Is this a problem with Open VPN or with SQL Server? Also, my ipp file says my address is 10.8.0.4 but when I connect it says 10.8.0.6 locally. Is that correct? Here's my config: Server ----------------------- local my-public-ip port 1194 proto udp dev tun dev-node "Ethernet 5" key cs-01.domain.com.key cert cs-01.domain.com.crt ca ca.crt dh dh2048.pem server 10.8.0.0 255.255.255.0 ifconfig-pool-persist ipp.txt keepalive 10 120 tls-auth vpn.tlsauth 0 cipher DES-EDE3-CBC max-clients 100 persist-key persist-tun status openvpn-status.log log-append openvpn.log verb 3 mute 10 script-security 2 up enabletap.cmd Client ------------------------ client dev tun dev-node "Ethernet" proto udp remote domain.com 1194 route 10.8.0.0 255.255.255.0 resolv-retry infinite nobind persist-key persist-tun remote-cert-tls server key desktop-990fx.key cert desktop-990fx.crt ca ca.crt remote-cert-eku "TLS Web Server Authentication" tls-auth vpn.tlsauth 1 cipher DES-EDE3-CBC verb 3 mute 10 script-security 2 up enabletap.cmd
TinCanTech fchateau wroteIf I change the address from 10.8.0.1 to 10.8.0.2 I get a bad network errorPlease See --topology in The Manual v23x Note: --topology net30 (default and in use here) 10.8.0.2 is not a ping-able address by design.
