What's in the eBook?
- Full list of reasons for poor performance
- Ultimate measures to speed things up
- Primary web monitoring types
- KPIs you should be monitoring in order to increase your ROI
Course Of The Month
7 days, 14 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
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 1 day ago
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
Active 3 days ago
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 1 day ago
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
The following article is comprised of the pearls we have garnered deploying virtualization solutions since Virtual Server 2005 and subsequent 2008 RTM+ Hyper-V in standalone and clustered environments.
- Virtualization
- Windows 10
- Windows Server 2016
- Windows Server 2012
- Hyper-V
- Windows, Azure, *Clustering
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
In this Micro Tutorial viewers will learn how to use Boot Corrector from Paragon Rescue Kit Free to identify and fix the boot problems of Windows 7/8/2012R2 etc. As an example is used Windows 2012R2 which lost its active partition flag (often happen…
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target.
To install the necessary roles, go to Server Manager, and select Add Roles and Featu…
Suggested Courses
Earn Certification
HTML5 Specialist - Certification
Free withPremium
Course of the Month7 days, 14 hours left to enroll
617 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.