Task Manager for Hyper-V provides critical information that allows you to monitor Hyper-V performance by displaying real-time views of CPU and memory at the individual VM-level, so you can quickly identify which VMs are using host resources.
Solved
rds servers not accepting connections
Posted on 2016-11-21
Hi all,
I've set up 2 RDS 2012 R2 servers and created a collection and one of the servers as a broker. If i try to connect directly to RDS2 then i can log on fine however if i try to RDP to RDS1 (the broker) i get "this computer can't connect to the remote computer"
I have confirmed that remote desktop is enabled and the user is allowed ?
Also if i open the MSTS with /admin and try it i then get a "the requested session access is denied" error ?
This "seems" to have stopped working since i put the broker on
any help would be great.
Thanks
I've set up 2 RDS 2012 R2 servers and created a collection and one of the servers as a broker. If i try to connect directly to RDS2 then i can log on fine however if i try to RDP to RDS1 (the broker) i get "this computer can't connect to the remote computer"
I have confirmed that remote desktop is enabled and the user is allowed ?
Also if i open the MSTS with /admin and try it i then get a "the requested session access is denied" error ?
This "seems" to have stopped working since i put the broker on
any help would be great.
Thanks
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2-
2
4 Comments
Active today
you will not be directed to RDS2 via RDS1
I believe you also have installed RD Web access role on RDS1 (broker)
Open web browser and logon to broker server via rd web access portal some thing like below
https://rdweb.domain.com/rdweb.aspx
Then you will be able to list there RDS2 as RDP connection where you can connect
Else whatever u are doing (connecting directly to RDS 2) is also fine, the request 1st will routed to broker and broker will again redirect to RDP server
Mahesh
I believe you also have installed RD Web access role on RDS1 (broker)
Open web browser and logon to broker server via rd web access portal some thing like below
https://rdweb.domain.com/rdweb.aspx
Then you will be able to list there RDS2 as RDP connection where you can connect
Else whatever u are doing (connecting directly to RDS 2) is also fine, the request 1st will routed to broker and broker will again redirect to RDP server
Mahesh
Thanks Mahesh but i just want to be able to RDP directly to RDS1 to begin with so i'm not concerned about it re-redirecting me to RDS2 at present ?
If i log onto RDWEB then it does only give me RDS1 but i get the same error connecting each time
If i log onto RDWEB then it does only give me RDS1 but i get the same error connecting each time
Active today
Ok
Got it
U r trying to access RD broker server also as a RD session host server
You have deployed standard RDS deployment with role separation, hence you are facing issues, RD connection broker in separation mode won't allow you to connect via RDP in application mode, you can connect to that sever only with administration RDP mode
You need to do this setup differently
Try below
destroy current deployment and then install all RDS role on single server (Quick start deployment)
Then check if you are able to connect to RDS deployment
Once that is successful, add another RD session host server in that deployment and see if you can connect to both servers
Check below link for quick start deployment
https://blogs.technet.microsoft.com/yungchou/2013/02/07/remote-desktop-services-rds-quick-start-deployment-for-remoteapp-windows-server-2012-style/
Mahesh.
Got it
U r trying to access RD broker server also as a RD session host server
You have deployed standard RDS deployment with role separation, hence you are facing issues, RD connection broker in separation mode won't allow you to connect via RDP in application mode, you can connect to that sever only with administration RDP mode
You need to do this setup differently
Try below
destroy current deployment and then install all RDS role on single server (Quick start deployment)
Then check if you are able to connect to RDS deployment
Once that is successful, add another RD session host server in that deployment and see if you can connect to both servers
Check below link for quick start deployment
https://blogs.technet.microsoft.com/yungchou/2013/02/07/remote-desktop-services-rds-quick-start-deployment-for-remoteapp-windows-server-2012-style/
Mahesh.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Every now and then, Microsoft does something that totally impresses me. It doesn't happen often, but in this case I must say I am thoroughly impressed with Windows Server Backup. One of the long time issues with Windows Backup has been the ability t…
How to deal with a specific error when using the Enable-RemoteMailbox cmdlet to create a mailbox in the cloud-based service, for an existing user in an on-premises Active Directory.
In this Micro Tutorial viewers will learn how to use Windows Server Backup to create full image of their system. Tutorial shows how to install Windows Server Backup Feature on Windows 2012R2 and how to configure scheduled Bare Metal Recovery backup.…
In this Micro Tutorial viewers will learn how to restore single file or folder from Bare Metal backup image of their system. Tutorial shows how to restore files and folders from system backup. Often it is not needed to restore entire system when onl…
Suggested Courses
Course of the Month11 days, 10 hours left to enroll
730 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.