Hi Glen, I am posting the auth.log file can you please check and help me regarding this issue.
Mar 31 05:58:32 r-17-VM sshd[5292]: pam_unix(sshd:session): session closed for user root Mar 31 05:58:32 r-17-VM sshd[5295]: Accepted publickey for root from 169.254.0.1 port 35569 ssh2 Mar 31 05:58:32 r-17-VM sshd[5295]: pam_unix(sshd:session): session opened for user root by (uid=0) Mar 31 05:58:33 r-17-VM sshd[5295]: pam_unix(sshd:session): session closed for user root Mar 31 05:58:33 r-17-VM sshd[5377]: Accepted publickey for root from 169.254.0.1 port 35570 ssh2 Mar 31 05:58:33 r-17-VM sshd[5377]: pam_unix(sshd:session): session opened for user root by (uid=0) Mar 31 05:58:33 r-17-VM sshd[5377]: pam_unix(sshd:session): session closed for user root Mar 31 05:58:34 r-17-VM sshd[5380]: Accepted publickey for root from 169.254.0.1 port 35571 ssh2 Mar 31 05:58:34 r-17-VM sshd[5380]: pam_unix(sshd:session): session opened for user root by (uid=0) Mar 31 05:58:34 r-17-VM sshd[5380]: pam_unix(sshd:session): session closed for user root Mar 31 05:58:53 r-17-VM sshd[5613]: Accepted publickey for root from 169.254.0.1 port 35573 ssh2 Mar 31 05:58:53 r-17-VM sshd[5613]: pam_unix(sshd:session): session opened for user root by (uid=0) Mar 31 05:58:53 r-17-VM sshd[5613]: pam_unix(sshd:session): session closed for user root Mar 31 05:58:54 r-17-VM sshd[5616]: Accepted publickey for root from 169.254.0.1 port 35574 ssh2 Mar 31 05:58:54 r-17-VM sshd[5616]: pam_unix(sshd:session): session opened for user root by (uid=0) Mar 31 05:58:54 r-17-VM sshd[5616]: pam_unix(sshd:session): session closed for user root Regards, Venkat Boggarapu -----Original Message----- From: Glenn Wagner [mailto:[email protected]] Sent: Wednesday, March 30, 2016 8:41 PM To: [email protected] Subject: RE: REMOTE VPN CONNECTION FAILED IN UPGRADED CLOUDSTACK FROM 4.3.1 TO 4.71 Hi Could you post the auth.log file of the Virtual Router you are trying to connect too Glenn Regards, Glenn Wagner [email protected] www.shapeblue.com 2nd Floor, Oudehuis Centre, 122 Main Rd, Somerset West, Cape Town 7130South Africa @shapeblue -----Original Message----- From: Venkat Boggarapu [mailto:[email protected]] Sent: Wednesday, 30 March 2016 3:02 PM To: [email protected] Subject: RE: REMOTE VPN CONNECTION FAILED IN UPGRADED CLOUDSTACK FROM 4.3.1 TO 4.71 Hi Glen, We done upgraded all the virtual routers after the cloudstack upgrade. Thanks, Venkat Boggarapu -----Original Message----- From: Glenn Wagner [mailto:[email protected]] Sent: Wednesday, March 30, 2016 6:24 PM To: [email protected] Subject: RE: REMOTE VPN CONNECTION FAILED IN UPGRADED CLOUDSTACK FROM 4.3.1 TO 4.71 Hi, Did you upgrade the virtual routers after the upgrade too 4.7.1. Regards Glenn Regards, Glenn Wagner [email protected] www.shapeblue.com 2nd Floor, Oudehuis Centre, 122 Main Rd, Somerset West, Cape Town 7130South Africa @shapeblue From: Venkat Boggarapu [mailto:[email protected]] Sent: Wednesday, 30 March 2016 1:55 PM To: [email protected] Subject: REMOTE VPN CONNECTION FAILED IN UPGRADED CLOUDSTACK FROM 4.3.1 TO 4.71 Hi Team, Recently I upgraded cloud stack 4.7.1 from 4.3.1 using 4.6 system VM template. When I am using 4.3.1 the REMOTE VPN is working fine with all windows vms like windows 7, 8 and 8.1. I followed the link http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.8/networking/using_remote_access.html to enable the "REMOTE VPN" settings After upgradation to cloudstack4.7.1 the remote VPN is not connecting with the same windows VMS and new VMS, we are getting the following error [cid:[email protected]] "L2TP CONNECTION ATTEMEPT FAILED BECAUSE THE SECURITY LAYER ENCOUNTERED A PROCESSING ERROR DURING INITIAL NEGOTIATIONS WITH THE REMOTE COMPUTER" Please share your knowledge with high importance if anyone have faced the same issue with provided documentation. Thanks, Venkat Boggarapu
