KB44495 - How to Resolve "Server not Reachable or REST Access Failed" Error For Test Connections of Remote TOTP Server Configured with IP (or) Hostname?

How to Resolve "Server not Reachable or REST Access Failed" Error For Test Connections of Remote TOTP Server Configured with IP (or) Hostname ?
 

This article describes an issue where the Remote Time based One Time Password (TOTP) server configured with IP (or) Hostname displays the below error during a test connection.

Server not reachable or REST access failed

 

The Remote TOTP connection is made using REST Call. The REST call will verify the device certificate irrespective of IP or Hostname. The following  error message is seen during a test connection.
 

ⓧerror
For (host:X.X.X.X/Hostname, totp-server:name): Server not reachable or REST Access Failed

For Example: 

ⓧerror 
For (host:10.209.69.6, totp-server:pulsetotp): Server not reachable or REST Access Failed

This issue occurs due to the mismatch of the hostname (or) IP specified on device certificate and the Remote TOTP Server. 

For Example
 

	Device Certificate	Remote TOTP	Result
Scenario  1	*.pulsesecure.net (SAN: DNS=*.pulsesecurelab.net)	totp.lab.net	An error will be thrown due to Hostname does not match
Scenario 2	*.pulsesecure.net (SAN: DNS=*.pulsesecurelab.net)	X.X.X.X  which is resolved to totp.pulsesecure.net	An error will be thrown due to IP does not match

To resolve this error, the attributes on the device certificate(CN / SAN) must match with IP and Hostname mentioned on Remote TOTP.
 

Device Certificate: *.pulsesecure.net (SAN: DNS=*.pulsesecurelab.net,DNS=*.ab.net, IP Address=X.X.X.X  )
Remote TOTP: totp.lab.net   --> Problem will not occur 
Remote TOTP: X.X.X.X  which is resolved to totp.pulsesecure.net  --> Problem will not occur