Hi guys, sometimes it works fine but sometimes we have to connect 2-3 times before the connection is made. seeing this in the event logs. been trying to figure it out for a while. the issue has been there for as long as I can remember. I need your help. Thanks ! I'll see the error below in the logs, when I get the error on the client side and then usually on the 2 or 3rd try, it'll work...
1-
An account failed to log on.
Subject:
Security ID:
SYSTEM
Account Name:
RDS1$
Account Domain:CORP
Logon ID:
0x3E7
Logon Type:10
Account For Which Logon Failed:
Security ID:
NULL SID
Account Name:
Administrator
Account Domain:RDS1
Failure Information:
Failure Reason:Unknown user name or bad password.
Status:
0xC000006D
Sub Status:
0xC0000064
Process Information:
Caller Process ID:0x1f40
Caller Process Name:C:\Windows\System32\winlogon.exe
Network Information:
Workstation Name:RDS1
Source Network Address:x.x.x.x
Source Port:
0
Detailed Authentication Information:
Logon Process:User32
Authentication Package:Negotiate
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.
2-
Network Policy Server discarded the request for a user.
Contact the Network Policy Server administrator for more information.
User:
Security ID:
NULL SID
Account Name:
CORP\username
Account Domain:CORP
Fully Qualified Account Name:CORP\username
Client Machine:
Security ID:
NULL SID
Account Name:
Pat-PC
Fully Qualified Account Name:-
OS-Version:
-
Called Station Identifier:UserAuthType:PW
Calling Station Identifier:-
NAS:
NAS IPv4 Address:-
NAS IPv6 Address:-
NAS Identifier:-
NAS Port-Type:Virtual
NAS Port:
-
RADIUS Client:
Client Friendly Name:-
Client IP Address:-
Authentication Details:
Connection Request Policy Name:TS GATEWAY AUTHORIZATION POLICY
Network Policy Name:-
Authentication Provider:Windows
Authentication Server:RDS1.corp.smith.co
Authentication Type:Unauthenticated
EAP Type:
-
Account Session Identifier:-
Reason Code:
5
Reason:
The Network Policy Server was unable to connect to a domain controller in the domain where the account is located. Because of this, authentication and authorization for the RADIUS request could not be performed.
3-
The user "CORP\username", on client computer "x.x.x.x", did not meet connection authorization policy requirements and was therefore not authorized to access the RD Gateway server. The authentication method used was: "NTLM" and
connection protocol used: "HTTP". The following error occurred: "23003".