Cross domain authentication

I have a pc, joined to domain A
On this pc I have a network share, on a file server on domain B

(on domain B I have group policy enable > after 10 wrong pwd tries, lock user)

I don't understand why, at startup, the pc tries to authenticate on that network drive but it fails (different domain/pwd)

Funny thing, I've also removed the network mapped drive, but even if I \\fileserver, the pc tries to authenticate: it fails again (no pop up for credentials appear) and the user, on domain B is locked

The 2 domain, A & B, are not in trust.
ServiceAdvisoryAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
ServiceAdvisoryConnect With a Mentor Author Commented:
I've already downloaded some tools and I find in netlogon (domain B) the 10 failed attempts from domain A
See above for details

I don't understand what "process" tries to authenticate and why he tries 10 times, if it fails
0
 
Steven WellsSystems AdministratorCommented:
What event is logged in the security log of re server hosting the share?

Have you rebooted and cleared the saved usernames and passwords from the client computer?

You should be able to authenticate across the share as long as the computer isn't trying to use any other credential first
0
 
ServiceAdvisoryAuthor Commented:
09/24 08:13:17 [LOGON] domainB: SamLogon: Network logon of domainA\pippo from WKS007 Entered
09/24 08:13:17 [LOGON] domainB: NlPickDomainWithAccount: domainA\pippo: Algorithm entered. UPN:0 Sam:1 Exp:0 Cross: 0 Root:1 DC:0
09/24 08:13:18 [LOGON] domainB: SamLogon: Network logon of domainA\pippo from WKS007 Returns 0xC000006A

This is what I see from netlogon on DC on domain B
----------------
Yes, in theory I removed mapped network drive and rebooted: no credential should be stored
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
Steven WellsSystems AdministratorCommented:
You could try creating a user account on both networks with the same name and passord

Are you using ntlm authentication on the destination domain?

I would look at the authentication method on the share domain. If Kerberos is being used the client may not be able to authencate.
You will also need to specifify domainb\user from the client on domain a if that makes sense.
0
 
ServiceAdvisoryAuthor Commented:
yes, the user, with the same pwd, exist in both domains

I don't think the problem is the auth method: in the same config, I have 9 users working, 1 not

Any other ideas?
Thx
0
 
Steven WellsSystems AdministratorCommented:
If one user is not working perhaps look at that account. 0xC000006A Refers to unknown error or wrong password.
0
 
ServiceAdvisoryAuthor Commented:
still in trouble... any other suggestions?
0
 
Steven WellsSystems AdministratorCommented:
Is it doing the behavior no matter what user account you logon with on that same machine?

ie, is there something in the profile of that user account doing the mapping, and therefore, the locking?

It sounds like a process or something else is actually doing the connection.

You could use process monitor to monitor the network traffic to see what actually is creating the connection, and then work backwards.   It sounds like a credential manager issue ie, stored usernames and passwords.

If it's related to one profile only, perhaps re-create that profile.
0
 
ServiceAdvisoryAuthor Commented:
the problem happens to random users, from different machines

no mapping, removed all

when I start the pc (nothing mapped) all is ok
when I just write in file Explorer \\filserver, the pc start authentication trough domain, and user get locked
0
 
Steven WellsSystems AdministratorCommented:
Confirm you have checked the credential manger on the clients machines?

Could you perhaps look at guest access to the share, rather than user authentication? ( enable guest account )
Are all machines using the same user account?
0
 
ServiceAdvisoryAuthor Commented:
no pwd stored in the machine

no guest account > strange thing the user worked for several months, and that the issue started
no different machines/accounts
0
 
Steven WellsSystems AdministratorCommented:
You mention that you don't get promoted for credentials. The account just gets locked. I am inclined to think the accounts are being locked out by something on the server domain outside the domain that is connecting in.

I would recommend downloading a lockout examiner product -even just eval- and scan the domain that has the server share to try and work out where the account is being locked out. Or there should be a number of attempts before the account locks. I would we expect the account is being locked out somewhere else.
0
 
Steven WellsSystems AdministratorCommented:
The log just shows the fact the account was locked. It doesn't show where or how. You need to examine the security log on the DC too. The tool may also require changes to the auditing policy too. I can recommend the netrix product for this. It has helped me lots of times.
0
 
ServiceAdvisoryAuthor Commented:
no solution provided
0
All Courses

From novice to tech pro — start learning today.