Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > Blue Coat Invalid data received from remote server in NCM

Blue Coat Invalid data received from remote server in NCM

Updated January 18, 2018


When you attempt to add a Blue Coat node in NCM you receive Test Failed Connection refused. 


  • NCM 7.6 and 7.7


  • SSH2

    NCM tries to negotiate an AES algorithm first (any type). If that fails, NCM tries TripleDES. If TripleDES is not available, NCM tries Blowfish. If Blowfish fails, NCM drops the connection instead of trying DES, which most (new) servers don't support because of its poor security.

For more Details please see the KB post below.


If the device has CSCipher = aes128-cbc, when NCM sees the Cipher it tries to get the connection using AES. The device refuses the connection because the device is not configured to use this AES cipher and the connection is refused. 


This is known issue. SolarWinds suggests trying the following workarounds:

  • Configure device and deny usage of any other ciphers except AES-256 on device side.
  • Use the SSH Auto 
  • Enable Telnet and download the device configuration




Last modified