Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Network Configuration Manager (NCM) > Error: Login failed [user: <Connection Profile User>] [Source: <Orion Server IP>] [localport: 22] [Reason: Login Authentication Failed]

Learn more about page titles
Error: Login failed [user: <Connection Profile User>] [Source: <Orion Server IP>] [localport: 22] [Reason: Login Authentication Failed]

 

Overview

This article describes the issue where you receive the following error:

Login failed [user: <Connection Profile User>] [Source: <Orion Server IP>] [localport: 22] [Reason: Login Authentication Failed]

 

 

Environment

All NCM versions

 

Cause 

This occurs when the NCM scheduled job downloads the configs from multiple nodes.

 

Resolution

  1. Check the time stamps of the errors and compare them with the ones from the NCM scheduled job, such as the Nightly Config Backup.
  2. Go to All Settings > NCM Settings and make the following changes:
    1. Configs > Simultaneous Downloads/Uploads: from 10 to 5 sessions.
    2. Protocol Settings > Telnet/SSH Connection Timeout: from 45 to 280 seconds.
    3. Protocol Settings > Telnet/SSH Prompt Timeout: from 15 to 180 seconds
  3. Save the changes.

 

 

Last modified
20:00, 18 Apr 2017

Tags

Classifications

Public