cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

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

After configuring a beacon we receive the following error when testing:

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

The uploader log files produce show a 404 error and then the failed to create error.

 

This is what has been checked and verified:

  1. All IIS and App pool settings are correct
  2. The certificates (Checkcertificaterevocation and checkservercertificate have been set to false in the registry
  3. port 443 is opened
  4. all permissions are correct
  5. The beacon config files are also correct

What else could we check?

 

(7) Replies
mfranz
By Level 17 Champion
Level 17 Champion

Hi,

Some questions:

  • Do you have other Beacons working correctly?
  • Have you configured the Beacon's parent connection manually?
  • Has the Beacon been registered to FNMS and does it show in the Beacons overview/the Beacon_MT table?
  • Have you tried activating advanced loggin in the IIS?
  • Have you tried accessing files manually via a browser?

Best regards,

Markward

Hi @mfranz 

Just an FYI this is a cloud implementation.

Some questions:

  • Do you have other Beacons working correctly? - Yes
  • Have you configured the Beacon's parent connection manually? - We have tried both
  • Has the Beacon been registered to FNMS and does it show in the Beacons overview/the Beacon_MT table? - Beacon is there but says - Check connectivity
  • Have you tried activating advanced loggin in the IIS? - No, have not done that. What would be the reason for that?
  • Have you tried accessing files manually via a browser? - Yes, but they do not open, does not even open, just errors out

regards

Manish

Hi Manish,

Have you checked if the BeaconStatus files are imported correctly? Is the Scheduled Task running correctly? Do files get consumed without errors or are there "BadLogs" in C:\ProgramData\Flexera Software\Incoming\BeaconStatus

Advanced logging may help find additional details regarding the error.

Best regards,

Markward

No "bad Logs" are produced. All tasks are running ok.

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?

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