Highlighted
Rising star

Re: The connection to FNMP succeeded, but the server did not respond to the test correctly.

To maybe clarify if the sender or receiver has a problem, do you think you could try the Beacon "talk" to another endpoint (a different Beacon), just for a quick test?

Softline Group is Europe's leading independent expert in Software Asset Management.
0 Kudos
Highlighted
Occasional contributor

Re: The connection to FNMP succeeded, but the server did not respond to the test correctly.

Hi Manish,

The said symptoms may arise because of IPv6 as well.

Besides making sure that TLS 1.1 and 1.2 are enabled, do a binding of the default web-site for IPv6, and do this on Application Server as well as Beacons. The same certificate would be used for binding as used for IPv4, in case port 443 is being used.

Lemme know if that works for you.

Regards,

Vishal

Highlighted
Occasional contributor

Re: The connection to FNMP succeeded, but the server did not respond to the test correctly.

0 Kudos