Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Cannot logon Domain\Username when creating AD accounts

Cannot logon Domain\Username when creating AD accounts

Updated 20th March 2018

Overview

When your deployment includes multiple trusted domains with your Orion Platform products installed in one of them and are creating AD accounts so that users from the trusted domains can log in to the Orion Web Console, you receive the following error message even though the account and credentials are correct.

Cannot logon Domain\Username via NetworkCleartext/Default

ad.PNG

Environment

  • Products using Orion Platform 2017.3 and earlier, such as NPM 12.2 and earlier

Cause 

When you provide the User Name and Password in the Specify credentials section and then provide the domain\username in the Search for Account section, the Search tries to use data specified in the fields even though it does not need it.

image.png

Resolution

To resolve the issue:

  1. Select the Specify credentials to access... option to activate the User Name and Password fields.
  2. Clear the User Name field so that it is empty.
  3. Search again.

 

Another workaround: Create individual accounts for your users.

 

 

Last modified

Tags

Classifications

Public