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

    Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005

    IT Discussion
    windows server 2012 windows windows server windows server 2012 essentials remote web access rds
    6
    23
    8.5k
    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 @scottalanmiller
      last edited by

      @scottalanmiller said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

      https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-supported-config

      Windows 10 cannot be used with Server 2012.

      What do you mean? VDI or what?

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

        @dbeato said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

        @scottalanmiller said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

        https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-supported-config

        Windows 10 cannot be used with Server 2012.

        What do you mean? VDI or what?

        VDI access is the same as non-VDI access. The limits of one have to reflect on the other as it is the connection over the network that doesn't work. Right?

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

          @scottalanmiller said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

          @dbeato said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

          @scottalanmiller said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

          https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-supported-config

          Windows 10 cannot be used with Server 2012.

          What do you mean? VDI or what?

          VDI access is the same as non-VDI access. The limits of one have to reflect on the other as it is the connection over the network that doesn't work. Right?

          I understand that but I have still RDS with Server 2008 R2, 2012 and one available and can connect via Windows 10 to Windows 10 Computers behind the RDS while they are non-VDI. Maybe @Osvaldo can clarify but he said Physical Desktops.

          scottalanmillerS 2 Replies Last reply Reply Quote 0
          • scottalanmillerS
            scottalanmiller @dbeato
            last edited by

            @dbeato said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

            @scottalanmiller said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

            @dbeato said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

            @scottalanmiller said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

            https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-supported-config

            Windows 10 cannot be used with Server 2012.

            What do you mean? VDI or what?

            VDI access is the same as non-VDI access. The limits of one have to reflect on the other as it is the connection over the network that doesn't work. Right?

            I understand that but I have still RDS with Server 2008 R2, 2012 and one available and can connect via Windows 10 to Windows 10 Computers behind the RDS while they are non-VDI. Maybe @Osvaldo can clarify but he said Physical Desktops.

            These are physical, but RDS literally cannot tell VDI from non-VDI. The two are identical on the network in every way.

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

              @scottalanmiller yes, they do. I mean try it.

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

                @dbeato said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

                @scottalanmiller yes, they do. I mean try it.

                Try what? Not sure what you mean?

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

                  @dbeato said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

                  @scottalanmiller said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

                  @dbeato said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

                  @scottalanmiller said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

                  https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-supported-config

                  Windows 10 cannot be used with Server 2012.

                  What do you mean? VDI or what?

                  VDI access is the same as non-VDI access. The limits of one have to reflect on the other as it is the connection over the network that doesn't work. Right?

                  I understand that but I have still RDS with Server 2008 R2, 2012 and one available and can connect via Windows 10 to Windows 10 Computers behind the RDS while they are non-VDI. Maybe @Osvaldo can clarify but he said Physical Desktops.

                  You have Windows 2012 (not R2) RDS acting as a front end proxy to Windows 10 that is working?

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

                    The issue that we have, Windows 10 resources will not even show up in RDS (RDW) at all. It won't even show them.

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

                      @scottalanmiller said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

                      @dbeato said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

                      @scottalanmiller said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

                      @dbeato said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

                      @scottalanmiller said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

                      https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-supported-config

                      Windows 10 cannot be used with Server 2012.

                      What do you mean? VDI or what?

                      VDI access is the same as non-VDI access. The limits of one have to reflect on the other as it is the connection over the network that doesn't work. Right?

                      I understand that but I have still RDS with Server 2008 R2, 2012 and one available and can connect via Windows 10 to Windows 10 Computers behind the RDS while they are non-VDI. Maybe @Osvaldo can clarify but he said Physical Desktops.

                      You have Windows 2012 (not R2) RDS acting as a front end proxy to Windows 10 that is working?

                      Yes and Server 2008 R2 as well.

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

                        @scottalanmiller said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

                        The issue that we have, Windows 10 resources will not even show up in RDS (RDW) at all. It won't even show them.

                        That I understand.

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

                          @dbeato said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

                          @scottalanmiller said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

                          @dbeato said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

                          @scottalanmiller said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

                          @dbeato said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

                          @scottalanmiller said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

                          https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-supported-config

                          Windows 10 cannot be used with Server 2012.

                          What do you mean? VDI or what?

                          VDI access is the same as non-VDI access. The limits of one have to reflect on the other as it is the connection over the network that doesn't work. Right?

                          I understand that but I have still RDS with Server 2008 R2, 2012 and one available and can connect via Windows 10 to Windows 10 Computers behind the RDS while they are non-VDI. Maybe @Osvaldo can clarify but he said Physical Desktops.

                          You have Windows 2012 (not R2) RDS acting as a front end proxy to Windows 10 that is working?

                          Yes and Server 2008 R2 as well.

                          So here it is RDS, but with RDW. Not sure if that is the source of the additional limitation.

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

                            @scottalanmiller Yeah, RDW is the problem I understand now. Basically you can remote desktop without need of App Resources Proxy without any problems. But if you try to load the App Resources from a Windows 10 device then yes I understand now.

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

                              @dbeato said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:

                              @scottalanmiller Yeah, RDW is the problem I understand now. Basically you can remote desktop without need of App Resources Proxy without any problems. But if you try to load the App Resources from a Windows 10 device then yes I understand now.

                              Yeah. It's a weird "Essentials only" issue, only on 2012 and older. From what I can tell.

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