Starting connection attempt.įeb 01 12:06:04: OpenVPN 2.2.2 Win32-MSVC++ built on Jan 4 2012įeb 01 12:06:07: WARNING: No server certificate verification method has been enabled. To display your routing table, open up Command Prompt from the Start menu, and type "route print" (no quotes).Ĭode: Select all Feb 01 12:06:02: Viscosity 1.3.5 (1120)įeb 01 12:06:02: Checking reachability status of connection.įeb 01 12:06:04: Connection is reachable. If you're still stuck, please post a copy of your OpenVPN log, and your routing table while connected. If this is the case, it can be easily fixed by adding the command "route-delay 20" (no quotes) to the commands section under the Advanced tab (when editing your connection). If you are ending up with a self-assigned IP, or the IP address is taking awhile to be detected, then it's possible OpenVPN may be trying to add the routes before the VPN connection is ready. To do this, check the Details window and see what the IP address is. You should also check that Viscosity is correctly getting an IP address (either from the OpenVPN server, or a DHCP server on your LAN network). If you can ping the server, but not other computers on your LAN, then it means there is problem with your bridge. See if you can ping the server's internal IP address. You should also check things like the firewall to check that they are correctly allowing traffic through. Firstly check that the bridging is correctly setup and working on your OpenVPN server (this is by far the most common reason for it to not work).
0 kommentar(er)
