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.

black3dynamite

The fix also fixes virtual machine connection too.

aginformatica

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.

black3dynamite

@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?

aginformatica

@black3dynamite
Thanks for the reply.
I'll try tomorrow and I'll let you know.
regards.

Obsolesce

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.

Obsolesce

It's due to MS patching a vulnerability that changes how authentication works. Resolve it by patching, not by lowering your security...

dbeato

@obsolesce said in Windows 10 Cumulative Update for 1709 KB4103727 cause RDP to not connect:

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.

But still the issue with @aginformatica is different as the error is not the one is usually the update issue.

dafyre

It also looks like @aginformatica is connecting on port 1512 as opposed to 3389...

hobbit666

We've found using the Romote Desktop App from the app store works with out changing any settings on the servers

(Win10Pro client machine)

aginformatica

Hello.
I think clients have local access so I do not know if I can download the desktop as an app. all windows 10 PCs after last update have presented the same error during rdp connection.
thank you and greetings.

Obsolesce

@dbeato said in Windows 10 Cumulative Update for 1709 KB4103727 cause RDP to not connect:

@obsolesce said in Windows 10 Cumulative Update for 1709 KB4103727 cause RDP to not connect:

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.

But still the issue with @aginformatica is different as the error is not the one is usually the update issue.

Oh didn't see that, was sticking to the OP.

dbeato

@obsolesce said in Windows 10 Cumulative Update for 1709 KB4103727 cause RDP to not connect:

@dbeato said in Windows 10 Cumulative Update for 1709 KB4103727 cause RDP to not connect:

@obsolesce said in Windows 10 Cumulative Update for 1709 KB4103727 cause RDP to not connect:

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.

But still the issue with @aginformatica is different as the error is not the one is usually the update issue.

Oh didn't see that, was sticking to the OP.

Okay, yeah that's fine then.