Logon for user "<usernamegoeshere>" failed with error (0X8007052E)

[loaned_brain]

Hi Everybody,

I ran into this error message while running Windows Module scans on hosts on our MVM 7.5 (Windows 2008 R2, SQL 208 R2) with credentials.

I know for a fact that the user/password combo is correct on the domain, I tried many variations and other local admin accounts, all failed with the same error.

Another symptom that I can't map network drives from MVM, but the non-credential scans are performed without a problem. MVM firewall is off, not joined to the domain, fresh install from scratch a couple days ago.

I looked at (https://community.mcafee.com/message/123772#123772) before that was about a similar issue, but that was a password problem.

2012-12-13 07:41:10-06:00 | <Stuff> | 4 | WindowsModule | 0x0224 | <computername [IP]>: Connecting as <domain>\<domainuser_1>.

2012-12-13 07:41:10-06:00 | <Stuff> | 4 | WindowsModule | 0x0224 | <computername [IP]>: Acquired SeSecurityPrivilege

2012-12-13 07:41:10-06:00 | <Stuff> | 2 | WindowsModule | 0x0224 | <computername [IP]>: Logon for user "<domainuser_1>" failed with error (0X8007052E)

2012-12-13 07:41:10-06:00 | <Stuff> | 4 | WindowsModule | 0x0224 | <computername [IP]>: Connecting as <domain>\<domainuser_2>.

2012-12-13 07:41:10-06:00 | <Stuff> | 4 | WindowsModule | 0x0224 | <computername [IP]>: Acquired SeSecurityPrivilege

2012-12-13 07:41:10-06:00 | <Stuff> | 2 | WindowsModule | 0x0224 | <computername [IP]>: Logon for user "<domainuser_2>" failed with error (0X8007052E)

2012-12-13 07:41:10-06:00 | <Stuff> | 4 | WindowsModule | 0x0224 | <computername [IP]>: Connecting as <domain>\<domainuser_3>.

2012-12-13 07:41:10-06:00 | <Stuff> | 4 | WindowsModule | 0x0224 | <computername [IP]>: Acquired SeSecurityPrivilege

2012-12-13 07:41:10-06:00 | <Stuff> | 2 | WindowsModule | 0x0224 | <computername [IP]>: Logon for user "<domainuser_3>" failed with error (0X8007052E)

2012-12-13 07:41:10-06:00 | <Stuff> | 4 | WindowsModule | 0x0224 | Unable to connect to [<IP>].

Any ideas?

Thanks

[cgrim]

Hi,

Did you check these KB's:

https://kc.mcafee.com/corporate/index?page=content&id=KB69956

https://kc.mcafee.com/corporate/index?page=content&id=KB52601

-Cathy

[loaned_brain]

Thank you for the links.

Meanwhile, we opened a ticket for this issue.

The "net use ..." command did not succeeded, and I suspected earlier (when I tried this before posting here). Is this the root problem? Since the appliance is not joint to our domain, should / would this still work?

In a nutshell: If the appliance is not on the domain, should I expect to use domain credentials out-of-the-box? Or do I need to join the appliance to the domain?

[loaned_brain · Accepted solution]

Actually, we worked it out on our own. (Wasted like a week on "support")

If you watch closely the authentication attempts between MVM <-> Target, you can identify if the security blobs are not compatible...

So go ahead, join the MVM to the domain (where no GP applies to it, just in case), and domain logins should magically starts to work.

[tpowell]

What do you mean by "security blobs are not compatible"?  I'm getting the same error but the system I'm trying to authenticate to isn't on the domain so I didn't think I should have to join the MVM to the domain.