Domain Login only working if legacy authentication mode is active

Hello,

Which version of DVLS have you installed?
Which version of RDM are you currently using?

Also, could you please post a print screen of the Authentication tab from the Server settings?

Best regards,

NEW Server-Installation:
Windows 2012 R2

SQL 2014

RDM 11.5.8.0
DVLS 3.2.1.0


regards,

markus

Hello,

What is the format of the username of these users? Do they use the UPN format (user@domain.loc), the Netbios format (domain\user) or only the username?

Could you please test it without any trusted domains and without legacy mode?

Best regards,

all versions of formats tested, with and without trusted domains, with and without legacy mode

result: login is only working if legacy mode is enabled ...

i have tested and installed sooo much times and 1000 variations.

would you like to have a view on the system?

Hello,

Please contact us at support@devolutions.net to set up a remote session.

Best regards,

done

Hello Erica,

I scheduled an appointment as you suggested.

BTW, today I found this log every time we try to logon:

The following error was received by a user at 22.06.2016 11:10:30
Error:
COMException - The specified directory service attribute or value does not exist. at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail) at System.DirectoryServices.DirectoryEntry.Bind() at System.DirectoryServices.DirectoryEntry.get_SchemaEntry() at System.DirectoryServices.AccountManagement.ADStoreCtx.IsContainer(DirectoryEntry de) at System.DirectoryServices.AccountManagement.ADStoreCtx..ctor(DirectoryEntry ctxBase, Boolean ownCtxBase, String username, String password, ContextOptions options) at System.DirectoryServices.AccountManagement.PrincipalContext.CreateContextFromDirectoryEntry(DirectoryEntry entry) at System.DirectoryServices.AccountManagement.PrincipalContext.DoLDAPDirectoryInitNoContainer() at System.DirectoryServices.AccountManagement.PrincipalContext.DoDomainInit() at System.DirectoryServices.AccountManagement.PrincipalContext.Initialize() at System.DirectoryServices.AccountManagement.PrincipalContext.ContextForType(Type t) at System.DirectoryServices.AccountManagement.Principal.set_SamAccountName(String value) at Devolutions.Server.DomainAuthenticationManager.Authenticate(String userName, String password, String domain, String& authenticatedUserName) in c:\Dev\devolutions11_5\Websites\Server\Common\Managers\DomainAuthenticationManager.cs:line 118 at Devolutions.Server.Providers.RDMSMembershipProvider.CheckPasswordActiveDirectoryMultiDomain(String username, String password, MembershipLoginData membershipLoginData) in c:\Dev\devolutions11_5\Websites\Server\Providers\RDMSMembershipProvider.cs:line 798 --- Login
Source:
System.DirectoryServices

FYI,
this path: c:\Dev\devolutions11_5\Websites\Server[/font]
do not exist in our system

AD Tests in Server Settings -> Authentication are all OK

Hi Erica,
Hi Maurice,

any update @ our problem?

regards
Markus

Hello,

We are currently working on it and as soon as it is ready, I will communicate with you.

Best regards,

Hi Erica,
Hi Maurice,
any update @ our problem?
it have been more than 2 months since our online-meeting and we really need a fix.
regards
Markus

Almost done, final rush

You will need to define a set of credentials at the Instance level, that account will need permissions to interrogate AD.

Thank you for your patience

I'm sitting on needles ...

can i test a beta for you?