Hello, everybody!
I got a problem with authentication between two domains in different forests recently.
We have production old domain with many servers providing services to customers and all user computers are part of another domain (we were bought by another company and all user PC were migrated to their domain).
We have two-ways trust between domains, I validated it and it passed fine, ping works fine between two domain controllers.
This configuration was working fine for a year, but recently I got complains from users, who using new domain credentials are trying to contact servers in old domain. SQL Server Management studio doesn't allow to logon, fileshares are not accessible (local security authority cannot be contacted), RDP says "No logon servers available". On the servers of old domain in local groups now I see GUIDs instead of "newdomain\Domain Users". But when I am trying to add "newdomain\Domain Users" there, it says this group already added.
When I trying to reach the server, I see this in event log:
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 6/25/2013 10:09:44 PM
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: FileServer2.olddomain.net
Description:
An account failed to log on.
Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: artem
Account Domain: newdomain
Failure Information:
Failure Reason: An Error occured during Logon.
Status: 0xc000005e
Sub Status: 0x0
Process Information:
Caller Process ID: 0x0
Caller Process Name: -
Network Information:
Workstation Name: ARTEMPC
Source Network Address: 172.20.1.166
Source Port: 51702
Detailed Authentication Information:
Logon Process: NtLmSsp
Authentication Package: NTLM
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Other recent topics
