From: Adam P. <apa...@be...> - 2004-06-15 04:45:54
|
James Yonan said the following on 6/14/2004 10:31 PM: >The "TLS handshake failed" condition is very general and could simply mean >that there's no OpenVPN running on the other side of the connection, or >there's a link failure. > >If the sample certs provided work but your own certs don't, then I would >question whether or not your own certs were generated correctly. > >If the sample certs don't work, then it may just be a network connection issue. > > I'm getting real close here. The TLS handshake is now successful with beta5. However, when the client's connection is initiated, a bunch of: Mon Jun 14 23:38:43 2004 TLS Error: Unknown data channel key ID or IP address re ceived from ip.address.of.server:port: 0 (see FAQ for more info on this error) ...messages are displayed; but it is sporadic -- it only happens ~50% of the time. The FAQ seems to imply that this is a server-only message, but in my case, it's only appearing on the client. Q: Is is mandatory that each client use unique certificate in server mode? FYI, when installing beta5 on an additional client, the installer reported that "An error occurred installing the TAP-Win32 device driver." <http://pavelec.net/s/?PBNSW8MS>, although everything seemed to work fine afterwards. The machine was rebooted after uninstalling beta4, and after installing beta5. -Adam |