Windows 10 Cumulative Update for 1709 KB4103727 cause RDP to not connect
-
@dustinb3403 said in Windows 10 Cumulative Update for 1709 KB4103727 cause RDP to not connect:
I remember this being an issue some years ago as well.
Before Remmina app got updated, I had to disable NLA awhile ago.
-
FYI - Windows Server 2016 KB4093137 (2018-04 Update) and KB4103723 (2018-05 Cumulative Update) are not installed on the server yet.
Will reboot tonight to see if that fixes this?
-
@dashrender said in Windows 10 Cumulative Update for 1709 KB4103727 cause RDP to not connect:
FYI - Windows Server 2016 KB4093137 (2018-04 Update) and KB4103723 (2018-05 Cumulative Update) are not installed on the server yet.
Will reboot tonight to see if that fixes this?
I have it installed and will let you know if users are having issues.
-
I just ran into something similar with Windows 10 connecting to 2012 R2 RDG and having the remember credentials checked. It would not let anyone login after it remembered their creds.
It requires a registry entry for the client. Not sure if it would benefit you, but here it is.
reg.exe Add "HKCU\Software\Microsoft\Terminal Server Client" /V "RDGClientTransport" /T REG_DWORD /D "1"
-
@wrx7m said in Windows 10 Cumulative Update for 1709 KB4103727 cause RDP to not connect:
I just ran into something similar with Windows 10 connecting to 2012 R2 RDG and having the remember credentials checked. It would not let anyone login after it remembered their creds.
It requires a registry entry for the client. Not sure if it would benefit you, but here it is.
reg.exe Add "HKCU\Software\Microsoft\Terminal Server Client" /V "RDGClientTransport" /T REG_DWORD /D "1"
Not sure if it's related, but I deleted the Default.RDP file from my documents and that didn't fix it either. The posts I got that suggestion said it was related to remembering creds.
-
-
@dbeato said in Windows 10 Cumulative Update for 1709 KB4103727 cause RDP to not connect:
Saw this today:
https://www.askwoody.com/2018/problems-with-credssp-updates-cve-2018-0886-breaking-rdp-connections/
I had been meaning to go back and look at the article from April referencing the credssp cve, but haven't had a chance. According to what others are saying there, any cumulative update for the server from March 2018 and later should have the patch and will allow connections.
-
@dbeato said in Windows 10 Cumulative Update for 1709 KB4103727 cause RDP to not connect:
Saw this today:
https://www.askwoody.com/2018/problems-with-credssp-updates-cve-2018-0886-breaking-rdp-connections/
Yup, hit us today for sure.
-
Here is the post that contains more specific information on the patch and necessary configurations
https://www.askwoody.com/2018/patch-lady-tracking-some-post-release-issues/
and straight from Microsoft-
https://support.microsoft.com/en-us/help/4093492/credssp-updates-for-cve-2018-0886-march-13-2018 -
-
You change it on the device you're connecting to, not the PC you're connecting from.
-
@dashrender
Thanks. -
I tested on 2012 R2, it worked there.
-
@scottalanmiller said in Windows 10 Cumulative Update for 1709 KB4103727 cause RDP to not connect:
I tested on 2012 R2, it worked there.
What worked where?
-
@dashrender said in Windows 10 Cumulative Update for 1709 KB4103727 cause RDP to not connect:
@scottalanmiller said in Windows 10 Cumulative Update for 1709 KB4103727 cause RDP to not connect:
I tested on 2012 R2, it worked there.
What worked where?
The fix.
-
The fix also fixes virtual machine connection too.
-
Hello
in a network with a 2012r2 server after the update to the last customer relationship win10 home / prof. This error appears:
can not find the "server01" computer. It is possible that "server01" does not belong to the specified network. Verify the computer name and the domain to which you are trying to connect.
which instructions can I follow, in addition to those listed in the discussion as well as update the server, to solve the problem?
thank you. regards.
-
@aginformatica said in Windows 10 Cumulative Update for 1709 KB4103727 cause RDP to not connect:
Hello
in a network with a 2012r2 server after the update to the last customer relationship win10 home / prof. This error appears:
can not find the "server01" computer. It is possible that "server01" does not belong to the specified network. Verify the computer name and the domain to which you are trying to connect.
which instructions can I follow, in addition to those listed in the discussion as well as update the server, to solve the problem?
thank you. regards.Have to you tried connecting via IP instead of hostname?
-
@black3dynamite
Thanks for the reply.
I'll try tomorrow and I'll let you know.
regards. -
This happens when one system is up to date and the other is not. I ran into this with our Hyper-V hosts because our desktops got updated first. Updating the Hyper-V hosts resolved the issue, as well as other systems.
