Windows Server 2008
--
Questions
--
Followers
Top Experts
Terminal Services error - Remote Desktop can't connect to the remote computer "xxx.com" for one of these reasons
We have an application server that is running Terminal Services. Customers connect to this through IE over the internet and the site is configured to run over port 443. Customers will get the error below if they don't have port 443 opened on their firewall. We have a customer that has opened 443 and is still getting this error (please see attachment for screenshot). What else can we do to troubleshoot? The site is working fine internally and for other external customers.
Remote App Disconnected - Remote Desktop can't connect to the remote computer "xxx.com" for one of these reasons:
1) Your user account is not listed in the RD Gateway's permission list...
2) You might have specified the remote computer in NetBIOS format (for example, computer1), but the RD Gateway is expecting FQDN or IP address format (for example, computer1.fabrikam.com or 157.60.0.1).
Contact your network administrator for assistance.
- ob1
TS-error.jpg
Remote App Disconnected - Remote Desktop can't connect to the remote computer "xxx.com" for one of these reasons:
1) Your user account is not listed in the RD Gateway's permission list...
2) You might have specified the remote computer in NetBIOS format (for example, computer1), but the RD Gateway is expecting FQDN or IP address format (for example, computer1.fabrikam.com or 157.60.0.1).
Contact your network administrator for assistance.
- ob1
TS-error.jpg
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Has this customer have another firewall, other than Windows? Also, have you had the customer try RDP via IP address? Perhaps their DNS service does not see the netbios name.
Sorry, there must be some firewall (corporate?) in the way. Port forwarding or NAT?
Sorry, there must be some firewall (corporate?) in the way. Port forwarding or NAT?
ASKER CERTIFIED SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
problem on customer's side, needed to open port 3389
Ancient, closed, thread.
But in case anyone else stumbles on this, I do not know what the OP's issue was here, but if the client can only connect on 3389, something's wrong on the server.
RDC tries 443 first, and if it can't connect, tries 3389. That would account for the end user's findings from their FW logs. But if everything's right on the server side, RDC will use ONLY 443. Anyone connecting on 3389 is using RDP alone, and making an end run around all the TS/RDS Gateway goodness.
If you have a Terminal Services or Remote Desktop Gateway, do not allow TCP 3389 inbound.
And if you are a TS/RDS Gateway client, do not allow TCP 3389 outbound to the RDS host.
But in case anyone else stumbles on this, I do not know what the OP's issue was here, but if the client can only connect on 3389, something's wrong on the server.
RDC tries 443 first, and if it can't connect, tries 3389. That would account for the end user's findings from their FW logs. But if everything's right on the server side, RDC will use ONLY 443. Anyone connecting on 3389 is using RDP alone, and making an end run around all the TS/RDS Gateway goodness.
If you have a Terminal Services or Remote Desktop Gateway, do not allow TCP 3389 inbound.
And if you are a TS/RDS Gateway client, do not allow TCP 3389 outbound to the RDS host.
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Windows Server 2008
--
Questions
--
Followers
Top Experts
Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.