Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

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

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

Updated April 18th, 2017

 

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

Tags

Classifications

Public