Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005
-
Got this error setting Remote Web Acess on Windows Server 2012 with RDW for a user (The "user" on client computer "192.168.0.31", met connection authorization policy and resource authorization policy requirements, but could not connect to resource "computer name". Connection protocol used: "HTTP". The following error occurred: "23005"). does anybody knows something about this kind of error?
Don't know if this is related, but this seems to have started after the computers in the clinic in question were updated from Windows 7 to Windows 10. Seem likely that this is the issue.
The Remote Web Access system is used to access physical desktops, not a central RDS server.
-
@Osvaldo said in RD not connecting and RD services showing error 23005:
Got this error setting RD for a user (The "user" on client computer "192.168.0.31", met connection authorization policy and resource authorization policy requirements, but could not connect to resource "computer name". Connection protocol used: "HTTP". The following error occurred: "23005"). does anybody knows something about this kind of error?
Check and make sure the Server they are connected to has the RDS Service running.
Also, temporarily disable the Connection Authorization Policy (or set it to allow all traffic) to test and make sure that is not the cause of the problems either. I've seen that happen a time or two when the server they were connecting to was not in the Allowed list.
-
Hi Dafyre, thank you for your help, I restarted the service and (disable/enable) policy and still the same error, thanks.
-
Does the user workstations have their firewall turn on, and if so are the appropriate exceptions made?
Are you able to rdp into this server from another workstation?
-
The machines that are trying to be accessed are not listed in RWA. They don't show up in the list of available machines, or the list to add.
-
Checked AD and the computers are in the right group.
-
@DustinB3403, The machines firewalls are on and the exceptions are made (for RD) I was able to Remote to the workstations from the server. I mean the main issue is that after updating all workstations to win10 they are not showing in the RDW.
-
@Osvaldo said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:
Got this error setting Remote Web Acess on Windows Server 2012 with RDW for a user (The "user" on client computer "192.168.0.31", met connection authorization policy and resource authorization policy requirements, but could not connect to resource "computer name". Connection protocol used: "HTTP". The following error occurred: "23005"). does anybody knows something about this kind of error?
Don't know if this is related, but this seems to have started after the computers in the clinic in question were updated from Windows 7 to Windows 10. Seem likely that this is the issue.
The Remote Web Access system is used to access physical desktops, not a central RDS server.
Make sure the Group Policy managing the Windows Firewall is set to allow all Remote Desktop inbound rule sets that are available.
Make sure the Group Policy Central Store on the DC(s) has been updated with the most recent PolicyDefinition folders and files.
Make sure the firewall is left on with logging set to ENABLED so that troubleshooting the firewall is a one step deal of looking at the log for the word DROP.
I'm thinking RDP TCP/UDP is being dropped at the endpoint.
-
Hi @PhlipElder, thank you for your suggestion, I was able to RD from the server, and the firewall GPs are set to open, still having same issue. The server has windows essentials too.
-
https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-supported-config
Windows 10 cannot be used with Server 2012.
-
@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?
-
@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?
-
@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.
-
@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.
-
@scottalanmiller yes, they do. I mean try it.
-
@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?
-
@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?
-
The issue that we have, Windows 10 resources will not even show up in RDS (RDW) at all. It won't even show them.
-
@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.
-
@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.
