ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Windows 10 Cumulative Update for 1709 KB4103727 cause RDP to not connect

    IT Discussion
    dash win10 nightmare rdp credssp
    12
    34
    8.8k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • wrx7mW
      wrx7m
      last edited by wrx7m

      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

      1 Reply Last reply Reply Quote 2
      • pmonchoP
        pmoncho @Dashrender
        last edited by

        @dashrender

        What version of RDP do you have? I don't have that option.

        This is what I have.

        0_1525972523391_rdp.PNG

        1 Reply Last reply Reply Quote 0
        • DashrenderD
          Dashrender
          last edited by

          You change it on the device you're connecting to, not the PC you're connecting from.

          pmonchoP 1 Reply Last reply Reply Quote 1
          • pmonchoP
            pmoncho @Dashrender
            last edited by

            @dashrender
            Thanks.

            1 Reply Last reply Reply Quote 0
            • scottalanmillerS
              scottalanmiller
              last edited by

              I tested on 2012 R2, it worked there.

              DashrenderD 1 Reply Last reply Reply Quote 0
              • DashrenderD
                Dashrender @scottalanmiller
                last edited by

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

                scottalanmillerS 1 Reply Last reply Reply Quote 0
                • scottalanmillerS
                  scottalanmiller @Dashrender
                  last edited by

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

                  1 Reply Last reply Reply Quote 0
                  • black3dynamiteB
                    black3dynamite
                    last edited by

                    The fix also fixes virtual machine connection too.

                    1 Reply Last reply Reply Quote 0
                    • A
                      aginformatica
                      last edited by

                      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.0_1528649933636_IMG_6474.JPG

                      black3dynamiteB 1 Reply Last reply Reply Quote 0
                      • black3dynamiteB
                        black3dynamite @aginformatica
                        last edited by

                        @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.0_1528649933636_IMG_6474.JPG

                        Have to you tried connecting via IP instead of hostname?

                        A 1 Reply Last reply Reply Quote 1
                        • A
                          aginformatica @black3dynamite
                          last edited by

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

                          1 Reply Last reply Reply Quote 0
                          • ObsolesceO
                            Obsolesce
                            last edited by

                            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.

                            dbeatoD 1 Reply Last reply Reply Quote 1
                            • ObsolesceO
                              Obsolesce
                              last edited by Obsolesce

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

                              1 Reply Last reply Reply Quote 2
                              • dbeatoD
                                dbeato @Obsolesce
                                last edited by

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

                                ObsolesceO 1 Reply Last reply Reply Quote 0
                                • dafyreD
                                  dafyre
                                  last edited by

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

                                  1 Reply Last reply Reply Quote 2
                                  • hobbit666H
                                    hobbit666
                                    last edited by

                                    We've found using the Romote Desktop App from the app store works with out changing any settings on the servers
                                    0_1528724287526_rdp.png
                                    (Win10Pro client machine)

                                    1 Reply Last reply Reply Quote 0
                                    • A
                                      aginformatica
                                      last edited by

                                      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.

                                      1 Reply Last reply Reply Quote 0
                                      • ObsolesceO
                                        Obsolesce @dbeato
                                        last edited by

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

                                        dbeatoD 1 Reply Last reply Reply Quote 0
                                        • dbeatoD
                                          dbeato @Obsolesce
                                          last edited by

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

                                          1 Reply Last reply Reply Quote 0
                                          • A
                                            aginformatica
                                            last edited by

                                            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.

                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 2 / 2
                                            • First post
                                              Last post