Issue accessing share from other forest. No logon servers available to serve your request.

Question

Hello, gents!
We have two AD forests and external 2-way trust between them. About month ago I was able to reach share on fileserver from localdomain.com to remotedomai.com without any issues. Now when I am trying to do it I have an error
"\\servername\share is not available.You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
there are currently no logon server available to service the logon request".
I validated trusts - everything validating fine.
In the event log of remote server, I am trying to access I found this error EventID 4625 from Microsoft Windows Security:
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: localdomain
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: ANOMDC1
Source Network Address: 172.20.0.10
Source Port: 53693
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.
What would be the proper steps to troubleshoot it?

Answer 1

See what is the status/substatus and see which number correspod to your system
Status and Sub Status Codes
Description (not checked against "Failure Reason:") 
0xC0000064
user name does not exist
0xC000006A
user name is correct but the password is wrong
0xC0000234
user is currently locked out
0xC0000072
account is currently disabled
0xC000006F
user tried to logon outside his day of week or time of day restrictions
0xC0000070
workstation restriction
0xC0000193
account expiration
0xC0000071
expired password
0xC0000133
clocks between DC and other computer too far out of sync
0xC0000224
user is required to change password at next logon
0xC0000225
evidently a bug in Windows and not a risk
0xc000015b
The user has not been granted the requested logon type (aka logon right) at this machine
 Regards
Milos