Note: The connection between the Tunnel server and the API server connection must be successful to achieve the expected result. In the Tunnel server, enter the following command: systemctl status vpnd.The server must display the port that is mentioned in the tunnel configuration. In the Tunnel server, enter the following command: netstat -tlpn.In the command prompt, enter the following command: openssl s_client -connect : -servername.From the device connected network, ensure that the device connects to the Tunnel server on the port that is mentioned in the tunnel configuration.The device must get connected and display the Tunnel server Front-End SSL certificate.If device is unable to communicate with the Tunnel server on the mentioned port, you may not be able to reach the Tunnel gateway. Tunnel server FQDN resolves to an IP address. In the command prompt, enter the following command: nslookup.
From the device connected network,ensure that the Tunnel server FQDN resolves to an IP address.You might encounter DNS resolution error if the VMware Tunnel server FQDN does not get resolved to an IP address. If not, restart the vpnd service on the UEM console and republish the VPN profile. Verify if the thumbprint on the device, server, and the UEM console is the same.On the server side, open /opt/vmware/tunnel/vpnd/nf and search for ssl_thumbprint.Scroll down to the SHA-1 text box and verify the certificate thumbprint.Click More Details and under the Certificate section, click the certificate with the Tunnel hostname.For all the iOS devices, navigate to Settings > General > Device Management> Device Manager.For all the Android devices, open the Workspace ONE Intelligent Hub and under the Profiles section, verify the certificate thumbprint for the Type.cer.In the UEM console, navigate to the Tunnel configuration page and verify the Front-End Certificate Thumbprint under server Authentication.You encounter this error if the SSL certificate present on the device does not match with the certificate on the server or if the certificate is not valid.
0 kommentar(er)
