Windows 10 Cumulative Update for 1709 KB4103727 cause RDP to not connect
-
@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.
-
It's due to MS patching a vulnerability that changes how authentication works. Resolve it by patching, not by lowering your security...
-
@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.
-
It also looks like @aginformatica is connecting on port 1512 as opposed to 3389...
-
We've found using the Romote Desktop App from the app store works with out changing any settings on the servers
(Win10Pro client machine) -
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. -
@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.
-
@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.
-
Hello.
on the server pc with windows 2012r2 it seems that the update kb4103725 insert credssp is not installed. what do you think if I download it manually and install it since windows update does not report it? can I solve the problem even if my error message is not related to credssp?
thank you. regards. -
Hello.
can anyone help me solve this problem?
thank you. -
The screenshot you originally show says it cannot find the computer you are trying to connect to. It doesnt look like you are in a domain environment.
Have you tried
ibm
or
ibm:3389Also i am unsure why you want to connect on port 1512, it is the MS WINS port. If you have WINS enabled you will not be able to have other service like RDP on 1512.
-
Hello.
I tried rdp connection to the server by entering the ip address with relative port (192.168.1.66:1512) and it worked. I do not understand why the problem occurred with the installation of the latest Windows 10 release (April 2018).
thank you. regards.
