RDP login error Windows 10 to Windows 7 (LSA error on client, Event 56 on host)
I've spent the last hour or so trying to solve an RDP issue between Windows 10 (we've tried several machines that are regularly used for RDP) and a remote Windows 7 machine. This connection has been used often for several years.
Over the past few weeks we have been unable to get an RDP connection, with the following symptoms.
Client (Windows 10)
The Local Security Authority cannot be contacted
This could be due to an expires password.
Server (Windows 7 - Event Log)
TermDD Code 56: The Terminal Server security layer detected an error in the protocol stream
I've checked the obvious possible issue mentioned in the client error but the password has not expired.
I've researched code 56 but nearly everything online relates to more random freezing / disconnects, with network issues being blamed primarily. I am getting the error instantly on login, and have a rock solid TeamViewer connection whilst trying to solve this so it doesn't seem to be the same issue.
I've also tried installing the RDP 8 update on the client in the hopes it might reset something in the RDP server and fix it, but I'm still getting exactly the same problem
Has anyone else seen this issue or know of a possible solution?
windows-7 remote-desktop
asked Jan 14 at 12:23
USD MattUSD Matt
133116
add a comment |
I've spent the last hour or so trying to solve an RDP issue between Windows 10 (we've tried several machines that are regularly used for RDP) and a remote Windows 7 machine. This connection has been used often for several years.
Over the past few weeks we have been unable to get an RDP connection, with the following symptoms.
Client (Windows 10)
The Local Security Authority cannot be contacted
This could be due to an expires password.
Server (Windows 7 - Event Log)
TermDD Code 56: The Terminal Server security layer detected an error in the protocol stream
I've checked the obvious possible issue mentioned in the client error but the password has not expired.
I've researched code 56 but nearly everything online relates to more random freezing / disconnects, with network issues being blamed primarily. I am getting the error instantly on login, and have a rock solid TeamViewer connection whilst trying to solve this so it doesn't seem to be the same issue.
I've also tried installing the RDP 8 update on the client in the hopes it might reset something in the RDP server and fix it, but I'm still getting exactly the same problem
Has anyone else seen this issue or know of a possible solution?
windows-7 remote-desktop
asked Jan 14 at 12:23
USD MattUSD Matt
133116
add a comment |
I've spent the last hour or so trying to solve an RDP issue between Windows 10 (we've tried several machines that are regularly used for RDP) and a remote Windows 7 machine. This connection has been used often for several years.
Over the past few weeks we have been unable to get an RDP connection, with the following symptoms.
Client (Windows 10)
The Local Security Authority cannot be contacted
This could be due to an expires password.
Server (Windows 7 - Event Log)
TermDD Code 56: The Terminal Server security layer detected an error in the protocol stream
I've checked the obvious possible issue mentioned in the client error but the password has not expired.
I've researched code 56 but nearly everything online relates to more random freezing / disconnects, with network issues being blamed primarily. I am getting the error instantly on login, and have a rock solid TeamViewer connection whilst trying to solve this so it doesn't seem to be the same issue.
I've also tried installing the RDP 8 update on the client in the hopes it might reset something in the RDP server and fix it, but I'm still getting exactly the same problem
Has anyone else seen this issue or know of a possible solution?
windows-7 remote-desktop
asked Jan 14 at 12:23
USD MattUSD Matt
133116
I've spent the last hour or so trying to solve an RDP issue between Windows 10 (we've tried several machines that are regularly used for RDP) and a remote Windows 7 machine. This connection has been used often for several years.
Over the past few weeks we have been unable to get an RDP connection, with the following symptoms.
Client (Windows 10)
The Local Security Authority cannot be contacted
This could be due to an expires password.
Server (Windows 7 - Event Log)
TermDD Code 56: The Terminal Server security layer detected an error in the protocol stream
I've checked the obvious possible issue mentioned in the client error but the password has not expired.
I've researched code 56 but nearly everything online relates to more random freezing / disconnects, with network issues being blamed primarily. I am getting the error instantly on login, and have a rock solid TeamViewer connection whilst trying to solve this so it doesn't seem to be the same issue.
I've also tried installing the RDP 8 update on the client in the hopes it might reset something in the RDP server and fix it, but I'm still getting exactly the same problem
Has anyone else seen this issue or know of a possible solution?
windows-7 remote-desktop
windows-7 remote-desktop
asked Jan 14 at 12:23
USD MattUSD Matt
133116
asked Jan 14 at 12:23
USD MattUSD Matt
133116
asked Jan 14 at 12:23
USD MattUSD Matt
133116
asked Jan 14 at 12:23
USD MattUSD Matt
133116
asked Jan 14 at 12:23
USD MattUSD Matt
133116
133116
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
This isn't really the "right" solution but it seems changing the remote settings to Allow connections from computers running any version of Remote Desktop allows me to connect.
Obviously I'd rather leave this set to the NLA option so it will still be useful if anyone else has some input on what might be causing this issue.
answered Jan 14 at 12:28
USD MattUSD Matt
133116
Doesn't look like I'll get a definitive answer...
– USD Matt
Jan 16 at 14:29
add a comment |
I was suffering the from the same issue and found a fix in KB 4487345 and it's downloadable in Microsoft's update catalog
Microsoft's patches from 2018-01-08 introduced "security fixes" in Windows 7 and 2008 R2 that broke remote access for users who are admins locally (on the server).
This was my initial source with a more detailed description.
answered Feb 7 at 20:22
LimerLimer
414
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1394100%2frdp-login-error-windows-10-to-windows-7-lsa-error-on-client-event-56-on-host%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
This isn't really the "right" solution but it seems changing the remote settings to Allow connections from computers running any version of Remote Desktop allows me to connect.
Obviously I'd rather leave this set to the NLA option so it will still be useful if anyone else has some input on what might be causing this issue.
answered Jan 14 at 12:28
USD MattUSD Matt
133116
Doesn't look like I'll get a definitive answer...
– USD Matt
Jan 16 at 14:29
add a comment |
This isn't really the "right" solution but it seems changing the remote settings to Allow connections from computers running any version of Remote Desktop allows me to connect.
Obviously I'd rather leave this set to the NLA option so it will still be useful if anyone else has some input on what might be causing this issue.
answered Jan 14 at 12:28
USD MattUSD Matt
133116
Doesn't look like I'll get a definitive answer...
– USD Matt
Jan 16 at 14:29
add a comment |
This isn't really the "right" solution but it seems changing the remote settings to Allow connections from computers running any version of Remote Desktop allows me to connect.
Obviously I'd rather leave this set to the NLA option so it will still be useful if anyone else has some input on what might be causing this issue.
answered Jan 14 at 12:28
USD MattUSD Matt
133116
This isn't really the "right" solution but it seems changing the remote settings to Allow connections from computers running any version of Remote Desktop allows me to connect.
Obviously I'd rather leave this set to the NLA option so it will still be useful if anyone else has some input on what might be causing this issue.
answered Jan 14 at 12:28
USD MattUSD Matt
133116
answered Jan 14 at 12:28
USD MattUSD Matt
133116
answered Jan 14 at 12:28
USD MattUSD Matt
133116
answered Jan 14 at 12:28
USD MattUSD Matt
133116
133116
Doesn't look like I'll get a definitive answer...
– USD Matt
Jan 16 at 14:29
add a comment |
Doesn't look like I'll get a definitive answer...
– USD Matt
Jan 16 at 14:29
Doesn't look like I'll get a definitive answer...
– USD Matt
Jan 16 at 14:29
Doesn't look like I'll get a definitive answer...
– USD Matt
Jan 16 at 14:29
add a comment |
I was suffering the from the same issue and found a fix in KB 4487345 and it's downloadable in Microsoft's update catalog
Microsoft's patches from 2018-01-08 introduced "security fixes" in Windows 7 and 2008 R2 that broke remote access for users who are admins locally (on the server).
This was my initial source with a more detailed description.
answered Feb 7 at 20:22
LimerLimer
414
add a comment |
I was suffering the from the same issue and found a fix in KB 4487345 and it's downloadable in Microsoft's update catalog
Microsoft's patches from 2018-01-08 introduced "security fixes" in Windows 7 and 2008 R2 that broke remote access for users who are admins locally (on the server).
This was my initial source with a more detailed description.
answered Feb 7 at 20:22
LimerLimer
414
add a comment |
I was suffering the from the same issue and found a fix in KB 4487345 and it's downloadable in Microsoft's update catalog
Microsoft's patches from 2018-01-08 introduced "security fixes" in Windows 7 and 2008 R2 that broke remote access for users who are admins locally (on the server).
This was my initial source with a more detailed description.
answered Feb 7 at 20:22
LimerLimer
414
I was suffering the from the same issue and found a fix in KB 4487345 and it's downloadable in Microsoft's update catalog
Microsoft's patches from 2018-01-08 introduced "security fixes" in Windows 7 and 2008 R2 that broke remote access for users who are admins locally (on the server).
This was my initial source with a more detailed description.
answered Feb 7 at 20:22
LimerLimer
414
answered Feb 7 at 20:22
LimerLimer
414
answered Feb 7 at 20:22
LimerLimer
414
answered Feb 7 at 20:22
LimerLimer
414
414
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1394100%2frdp-login-error-windows-10-to-windows-7-lsa-error-on-client-event-56-on-host%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
