Cant RDP "Locally as an Admin" into my server once I installed RD Gateway and RDS Services
I have 3 servers in my RDS farm and everything is configured and running well. Employees can connect via their HP terminals and I can migrate computers to and from hosts. The issue is we cannot connect via RDP to the server locally to manage. We can connect via Dame Ware just not RPD. Netstat shows port 3389 in the listening state. Ideas? Maybe a RAP policy in the Gatway manager? Should I use a different port other than 3389? Firewall is off even made the entries and turned it back on to test. NADA
Error on connection: Cannot connect to remote computer please contact your administrator.
note: I can RDP into all servers except the one with the GATEWAY service.
Error on connection: Cannot connect to remote computer please contact your administrator.
note: I can RDP into all servers except the one with the GATEWAY service.
Philip Elder
Log on to the console of the gateway machine and verify that "Allow Remote Connections" is enabled then verify the firewall is allowing 3389 TCP/UDP inbound.
ASKER
Both are enabled and im still getting this error. I can connect to all my other Hyper-V nodes just fine just not the one running Gatway services. I can log in using DameWare which uses port 443 and 6129 so that leads me to believe port 3389 is hanging up or not listening correctly. Is it because Gateway services are using it?
allow.png
allow.png
ASKER
Error on connection
Where is RDWeb? Verify that DefaultTSGateway has been set in IIS --> Sites choose site --> RDWeb --> Pages --> Application Settings --> DefaultTSGateway: rds.mydomain.com
Also, make sure the Access Policies reflect the proper access permissions.
Also, make sure the Access Policies reflect the proper access permissions.
ASKER
Gateway settings are correct. The polices in the gateway should be set like this correct?
RC Cap - specific user group to access Gateway
RD RAP - specific computer group to allow users permission to connect to
Would any of the above cause local RDP directly yo the server name not the RDWEB address break RDP?
RC Cap - specific user group to access Gateway
RD RAP - specific computer group to allow users permission to connect to
Would any of the above cause local RDP directly yo the server name not the RDWEB address break RDP?
I must admit that we've never hit this problem and we've built a lot of RDS Farms over the years.
Is there a Group Policy setting that may be preventing access to the machine? I suggest enabling Logging in the Windows Firewall and running a few connection attempts then check the log to see if it is dropping packets.
Log on via console and from an elevated CMD:
CD \Temp (create if doesn't exist)
GPResult /h GPResultsAdmin.html
Examine the resulting output to see what policies are being applied or denied.
Is there a Group Policy setting that may be preventing access to the machine? I suggest enabling Logging in the Windows Firewall and running a few connection attempts then check the log to see if it is dropping packets.
Log on via console and from an elevated CMD:
CD \Temp (create if doesn't exist)
GPResult /h GPResultsAdmin.html
Examine the resulting output to see what policies are being applied or denied.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.