Network Management
SCP on Windows is not working in NCM
This article provides information related to the use of the SCP protocol while utilizing the SSH Server on the Windows platform. Error: Server refused to start a shell/command Authentication log (see session log for details): Using username "admin". Access denied. Authentication failed. or Error: Error Downloading Config to SCP Host: X.X.X.X
First published date
Last published date
Overview
This article provides information related to the use of the SCP protocol while utilizing the SSH Server on the Windows platform.
While utilizing SCP for config backup, NCM will experience an authentication error. While testing download in NCM, the following error will be shown in Transfer Status grid:
Error Downloading Config to SCP Host: X.X.X.X
While using a standalone SCP client for testing, for example, WinSCP, the following error appears:
Server refused to start a shell/command
Authentication log (see session log for details):
Using username "admin".
Access denied.
Authentication failed.
Product section
Cause
Likely issue related to the implementation of the NCM SCP/SFTP Server and the underlying programmatic components (libraries) used in Windows or could be a result of security settings.
Resolution
Resolution 1:
You may be able to resolve this issue by configuring NCM to utilize a Unix/Linux-based SCP/SFTP server or experimenting with third-party Windows-based SCP/SFTP servers that have been installed on the NCM server and additional polling engines, if applicable. To do this, go to Settings>NCM settings>SCP Server and check the box to "Use third-party SCP Server."
Resolution 2:
1. It is also possible that you need to configure the Device Template for the Device.
2. Assign specific Device Templates and do not use AutoDetermine on the NCM Connection profile.
3. Check the following articles:
Best practices for NCM device templates
Create and manage device templates