Site Manager 8.0.6524 login delay with AD accounts


Author
Message
AlexI
AlexI
New Member
New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)
Group: Forum Members
Posts: 2, Visits: 5
Hi Everyone,

It's my first time using Site Manager and after installing it on one of my test laptops which is joined to a domain. I noticed that the login with any kind of admin AD account takes a very very long time to go through, when with a local one it's instant. Tried it on a different device and the same thing.

Any idea why these delays happen ?

Kind regards,
Alex

Alex
Alex
Macrium Representative
Macrium Representative (448 reputation)Macrium Representative (448 reputation)Macrium Representative (448 reputation)Macrium Representative (448 reputation)Macrium Representative (448 reputation)Macrium Representative (448 reputation)Macrium Representative (448 reputation)Macrium Representative (448 reputation)Macrium Representative (448 reputation)Macrium Representative (448 reputation)
Group: Moderators
Posts: 257, Visits: 905
AlexI - 12 April 2022 12:03 PM
Hi Everyone,

It's my first time using Site Manager and after installing it on one of my test laptops which is joined to a domain. I noticed that the login with any kind of admin AD account takes a very very long time to go through, when with a local one it's instant. Tried it on a different device and the same thing.

Any idea why these delays happen ?

Kind regards,
Alex

Hi Alex,

On our test equipment at Macrium, login via AD takes the same time as for local accounts. We do use LDAP for validating Active Directory logins so there are a couple of cases I can think of which have some slowdown -
1. When the domain is a manually configured domain that the SM server is not joined to - sometimes the Windows LDAP functions have a bit of a delay as they can try to do a DNS/network lookup of some server names which fails and causes some timeout
2. We try secure LDAPS before trying normal LDAP - some systems can have LDAPS enabled, but not working, which causes a delay as SM attempts to negotiate LDAPS and fails
3. If your domain is part of a forest where security/distribution groups on one domain are members of groups in other domains - that requires SM to track down all the group memberships manually (as cross-domain/global catalog lookups don't include local groups)

There is a log in c:\ProgramData\Macrium\SiteManager\accessLog.log. This will have various amounts of technical detail about the stages of a login and might be useful to pinpoint where the problem is. Our support team can probably help analyse this too if you raise a ticket. I'd advise that you don't include the logs on this forum as while we never log passwords, there may be some information on your IT infrastructure contained in them (account and server names, IP addresses, ports etc)

Kind regards,
Alex,
Macrium Development.

AlexI
AlexI
New Member
New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)
Group: Forum Members
Posts: 2, Visits: 5
Alex - 12 April 2022 12:18 PM
AlexI - 12 April 2022 12:03 PM
Hi Everyone,

It's my first time using Site Manager and after installing it on one of my test laptops which is joined to a domain. I noticed that the login with any kind of admin AD account takes a very very long time to go through, when with a local one it's instant. Tried it on a different device and the same thing.

Any idea why these delays happen ?

Kind regards,
Alex

Hi Alex,

On our test equipment at Macrium, login via AD takes the same time as for local accounts. We do use LDAP for validating Active Directory logins so there are a couple of cases I can think of which have some slowdown -
1. When the domain is a manually configured domain that the SM server is not joined to - sometimes the Windows LDAP functions have a bit of a delay as they can try to do a DNS/network lookup of some server names which fails and causes some timeout
2. We try secure LDAPS before trying normal LDAP - some systems can have LDAPS enabled, but not working, which causes a delay as SM attempts to negotiate LDAPS and fails
3. If your domain is part of a forest where security/distribution groups on one domain are members of groups in other domains - that requires SM to track down all the group memberships manually (as cross-domain/global catalog lookups don't include local groups)

There is a log in c:\ProgramData\Macrium\SiteManager\accessLog.log. This will have various amounts of technical detail about the stages of a login and might be useful to pinpoint where the problem is. Our support team can probably help analyse this too if you raise a ticket. I'd advise that you don't include the logs on this forum as while we never log passwords, there may be some information on your IT infrastructure contained in them (account and server names, IP addresses, ports etc)

Thank you for your quick input on this, I will have a look at the access log.
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Login

Explore
Messages
Mentions
Search