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.
    • 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
                  • A
                    aginformatica
                    last edited by

                    Hello.
                    can anyone help me solve this problem?
                    thank you.

                    1 Reply Last reply Reply Quote 0
                    • momurdaM
                      momurda
                      last edited by

                      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:3389

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

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

                        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.

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