Windows Server 2012 Foundation: Remote Desktop Connection - Credentials did not work

Question

Windows Server 2012 Foundation: Remote Desktop Connection - Credentials did not work

Anonymous

Hi,

I am currently using Windows Server 2012 Foundation and have been using a Remote Desktop connection to access the system.

This has been working for a couple of years. However, since the 14th of August 2016, the Remote Desktop Connection has stopped working and it now says that credentials did not work. I have confirmed that the credentials are correct by logging in directly and have confirmed that the user account is setup to accept remote desktop connections. I have also tried creating a new user account however have been unsuccessful.

In Event Viewer this message is coming up in the general tab

Log Name: Security

Source: Microsoft-Windows-Security-Auditing

Date: 22/08/2016 12:43:25 PM

Event ID: 4625

Task Category: Logon

Level: Information

Keywords: Audit Failure

User: N/A

Computer: ORDERMATE

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: ADMINISTRATOR

Account Domain:

Failure Information:

Failure Reason: Unknown user name or bad password.

Status: 0xC000006D

Sub Status: 0xC0000064

Process Information:

Caller Process ID: 0x0

Caller Process Name:

Network Information:

Workstation Name:

Source Network Address:

Source Port:

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.

Event Xml:

<Channel>Security</Channel>

<Computer>ORDERMATE</Computer>

</System>

<Data Name="TargetUserName">ADMINISTRATOR</Data>

</Data>

<Data Name="LogonProcessName">NtLmSsp </Data>

</Data>

</EventData>

</Event>

Log Name: Security

Source: Microsoft-Windows-Security-Auditing

Date: 22/08/2016 12:43:25 PM

Event ID: 4625

Task Category: Logon

Level: Information

Keywords: Audit Failure

User: N/A

Computer: ORDERMATE

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: ADMINISTRATOR

Account Domain:

Failure Information:

Failure Reason: Unknown user name or bad password.

Status: 0xC000006D

Sub Status: 0xC0000064

Process Information:

Caller Process ID: 0x0

Caller Process Name:

Network Information:

Workstation Name:

Source Network Address:

Source Port:

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.

Event Xml:

<Channel>Security</Channel>

<Computer>ORDERMATE</Computer>

</System>

<Data Name="TargetUserName">ADMINISTRATOR</Data>

</Data>

<Data Name="LogonProcessName">NtLmSsp </Data>

</Data>

</EventData>

</Event>

Any advice would be helpful.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 answer

Answer 1

This question is outside the scope of this site (for consumers) and to be sure you get the best (and quickest) answer it should be asked either on Technet (for IT Pro's) or MSDN (for developers)

http://social.technet.microsoft.com/Forums/en-us/home s/en-US/home

http://social.msdn.microsoft.com/Forum

If you give us a link to the new thread we can point some resources to it

Share via

Windows Server 2012 Foundation: Remote Desktop Connection - Credentials did not work

Account Name:

Account Domain:

Caller Process Name:

Source Network Address:

Source Port:

Transited Services:

Package Name (NTLM only):

Account Name:

Account Domain:

Caller Process Name:

Source Network Address:

Source Port:

Transited Services:

Package Name (NTLM only):

1 answer