RemoteApp Disconnected your computer can t connect to the Remote Desktop Gateway server
Archived Forums
>
Remote Desktop Services (Terminal Services)
Question
-
0Sign in to vote
Hi
Every so often some of my clients report that they get this message when trying to connect to a remote app:
your computer can't connect to the remote desktop gateway server. Contact your network administrator for assistance.
But the strange things is, if they try again it works straight away. There are no logs on the rdg server.
There is only one rdg server with no load balancing enabled. There are two remote app servers that are served by this rdg server and only one seems to be effected (i.e. no user ever reported issues when connecting to an app on the same server where the rdg is installed)
Another strange thing is that I cannot easily replicated the issue. It will work 9 times out of 10.
Does anyone has any idea ?
AJ
Monday, February 20, 2017 2:30 PM
All replies
-
0Sign in to vote
Hi AJ,
What is the OS of your RDS server? Windows Server 2012 R2?
For the problem, I suggest you install the update for RD gateway service freeze in Windows Server 2012 R2.
"Your computer can't connect to the remote computer" error because RD Gateway service freezes in Windows Server 2012 R2
//support.microsoft.com/en-us/help/3042843/-your-computer-can-t-connect-to-the-remote-computer-error-because-rd-gateway-service-freezes-in-windows-server-2012-r2
And here is an update for reliability improvements for Remote Desktop Session Host and RemoteApp that you should install.
Reliability improvements for Remote Desktop Session Host and RemoteApp
//support.microsoft.com/en-us/help/2959626/reliability-improvements-for-remote-desktop-session-host-and-remoteapp
In addition, I suggest you install latest updates for RDS in your RDS environment.
Here is an article below about available updates for RDS on Windows Server 2012 R2 for your reference.
Available Updates for Remote Desktop Services in Windows Server 2012 R2
//support.microsoft.com/en-us/help/2933664/available-updates-for-remote-desktop-services-in-windows-server-2012-r2
Best Regards,
Jay
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact .Tuesday, February 21, 2017 2:42 AM -
0Sign in to vote
Hi Jay
The sever is running on server2012 r2 and is up to date with updates. The gateway service does not freeze though as at the same time when I get the message another user will connect just fine.
With best regards
AJ
Tuesday, February 21, 2017 9:37 AM -
0Sign in to vote
Hi AJ,
Please confirm the operating systembuild running on the client PCs that are having the issue, using winver.exe. For example, Windows 10 1607 Build 14393.693 , screenshot:
For clients usingWindows Insiderbuilds, you may want to switch back to regular build of Windows 10 and test.
Thanks.
-TP
Saturday, February 25, 2017 9:51 AM -
0Sign in to vote
Multitude of different OSes
Most of them are win 10 (as per screenshot above). But some are Windows 7 Pro as well.
For the Windows 7 part both 32 and 64 bits flavour - with different varieties of updates applied.
None of the clients belong to the same domain and are in no way connected to each other (as if completely different clients from different parts of the globe i.e. USA, Canada, Europe etc)
Best Regards
AJ
Saturday, February 25, 2017 11:50 AM -
0Sign in to vote
Hi,
Can you please share all informations related to your RDS deployment ?
Did you use several CAP & RAP policies or you kept the by default CAP /RAP policies ?
Since when you are experiencing this problem ? did you make any change on your RDG and/or RDSH servers ?
did you already test and validate the switch between the first and second RD Session host server ?
What's the network configuration of your RDG server ? the server has one or two NIC (or vNIC) ?
How remote users connect and access to internal RDS resources ? > by using a RD Web Access or RDP shortcuts ?
Did you recently updated your firewall /router hardware ?
-HK.
Hicham KADIRI | Just Another IT Guy
Livre de référence RDS 2012 R2 désormais disponible !
RDS 2012 R2 reference book is now available !
Découvrez tous mes eBooks )Saturday, February 25, 2017 9:19 PM -
0Sign in to vote
Hi,
Are there any updates?
Best Regards,
Jay
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact .Tuesday, February 28, 2017 6:56 AM -
0Sign in to vote
Hi, please see below
Did you use several CAP & RAP policies or you kept the by default CAP /RAP policies
?
There are default CAP & RAP policies
Since when you are experiencing this problem ? did you make any change on your RDG and/or RDSH servers ?
We experince this issues from the very beginning if I remember correctly.
did you already test and validate the switch between the first and second RD Session host server ?
both of the servers are vm on the same host. Share the same virtual switch and as far as I can tell there is nothing wrong with it
What's the network configuration of your RDG server ? the server has one or two NIC (or vNIC) ?
the RDG server is a vm with one vNIC
How remote users connect and access to internal RDS resources ? > by using a RD Web Access or RDP shortcuts ?
Most of them access it via RD Web with multitude of browsers (and I cannot say for 100% that some of them work better than other i.e. the issues occur when using IE with the activex allowed as well as Chrome etc) some use remote RemoteApp and Desktop Connections from the desktops and some saved RDP files - and all of them experience the issue.
Did you recently updated your firewall /router hardware ?
No, the firewall and the rest of the h/w has not been changed since the deployment of the service.
With best Regards
AJ
Thursday, March 2, 2017 8:08 PM -
0Sign in to vote
Hi AJ,
From your description, the problem may be caused by RDP session is unstable.
Here is an update may be helpful to you.
RDP session is unstable when it uses UDP in Windows 8.1 or Windows Server 2012 R2
//support.microsoft.com/en-us/help/2989039/rdp-session-is-unstable-when-it-uses-udp-in-windows-8.1-or-windows-server-2012-r2
Best Regards,
Jay
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact .Friday, March 3, 2017 2:57 AM -
0Sign in to vote
That is an update for windows 8/8.1 and the errors are reported by clients with different versions of the windows o/s as well (mainly windows 10 - but that's only because of the majority of clients with windows 10)
Also, that update completely does not apply to my situation. Once connected the session is stable.
Regards
AJ
Saturday, March 4, 2017 6:53 PM -
0Sign in to vote
Finally I managed to experience the issue my self - so at least have some logs to go through - although - unfortunately - I must admit- they do not tell me much.
Would there be anyone at Microsoft willing to have a look at it ?
Regards
AJ
Wednesday, March 22, 2017 9:57 PM -
0Sign in to vote
Hi , Did you manage to get this working ? I recently installed an RDS 2012 solution. Multiple users are experiencing exactly this issue.
I have 1 server with gateway / connection broker / licensing
5 RDS hostsclients are reporting that they sometimes get the issue. but they retry 2 or 3 times. then when logged in the connection is stable. it never breaks.
very strange! hope you can answer :)
Regards!
Monday, June 26, 2017 10:22 AM -
0Sign in to vote
Hi
Unfortunately not. I think I will complete re-setup the rds services on the other server as I am running out of ideas (actually I have ran out of ideas this is the last option I can think of).
Wish you all the best .
Regards
AJ
Monday, June 26, 2017 10:31 AM -
0Sign in to vote
Hi AJ,
Maybe we can work together on this and share our experiences.
I have come to something that I believe is working now.
I have enabled "bypass rd gateway for local addres" and I think it is now working. (although I think this is not the way it should be)
Not sure. Because the error occurs now and then. I can not tell you exactly when it happens. it is random.
like the gateway is very busy or something. but it occurs in the morning, midday and evening.
Thx!
JoostTuesday, June 27, 2017 9:24 AM -
0Sign in to voteI see its been a few months since anyones replied to this but was wondering if someone found a answer to this issue im running pretty much the same setup except with server 2016 and I have the physical machine running hyper v server 2016 with two vms one is the session host for the app and the other is the gateway webaccess etc and they are both running server 2016. I noticed also this doesnt happen to all the clients who connect and theres only a couple really having the issue and it seems to be random and if they try again it works.Tuesday, December 19, 2017 6:43 PM
-
0Sign in to vote
Here is the answer to this question...
Change the registry key for HKLM\SYSTEM\CurrentControlSet\Control\Lsa\LmCompatibiltyLevel to a value of 3.
Ref://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-2000-server/cc960646(v=technet.10)
and
//support.microsoft.com/en-us/help/2903333/terminal-services-client-connection-error-0xc000035b-when-you-use-lmco
It seems that every time I get over one issue...there is always another with RDS. This should be the best setting for RDP and also the most secure.
bonnetttc
Monday, May 20, 2019 1:20 AM
14 Replies
· · ·
Pure Capsaicin
OP
DragonsRule
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Microsoft Remote Desktop Services expert
102 Best Answers
339 Helpful Votes
Allferry wrote:
I also get the error internally when unticking "Bypass RD Gateway server for local addresses".
That makes it sound like your Gateway is not properly setup, which would also explain why external access is failing.
Allferry wrote:
installed a paid SSL.
Did you get a wildcard SSL? Have you confirmed that the domain name matches your gateway?
0
· · ·
Jalapeno
OP
flemos89
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
HeyAllferry
I did have the same issue, what I did end up doing was to add an reg key on the user:
Open REGEDIT and go to HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client create a new DWORD
Name: RDGClientTransport
Type: Dword
Value: 1
Cheers,
- AllferryPoblano
0
· · ·
Poblano
OP
Allferry
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
flemos89 I have added the key but not avail.
- flemos89Jalapeno
0
· · ·
Poblano
OP
Allferry
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
DragonsRule We have indeed a wildcard SSL. We have an entry in the SSL that points to our servername, so should be fine.
- DragonsRulePure Capsaicin
0
· · ·
Pure Capsaicin
OP
DragonsRule
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Microsoft Remote Desktop Services expert
102 Best Answers
339 Helpful Votes
Da_Schmoo knows a lot more about SSL certificates than I do. Maybe he'll have a thought about this.
- Da_SchmooMace
0
· · ·
Jalapeno
OP
flemos89
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Allferry wrote:
flemos89 I have added the key but not avail.
HeyAllferry
Can you try and delete de windows credential? I've been checking this kind of issues and one was cleaning the Windows Credential, you can have a look it here.
Also, do you have a Firewall? Are you getting any attempting on the port? I think the Remote uses the TCP 443 and UDP 3391 to secure connect the remote server.
- AllferryPoblano
0
· · ·
Poblano
OP
Allferry
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
flemos89 I don't have any credentials saved on Web Cred nor Windows Cred. Thanks for tip thou.
- flemos89Jalapeno
0
· · ·
Mace
OP
Da_Schmoo
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Microsoft Remote Desktop Services expert
50 Best Answers
207 Helpful Votes
"We have an entry in the SSL that points to our servername, so should be fine."
Do you have a wildcard cert or SAN cert?
That said, I don't think this is a cert issue. Is the server and workstation fully patched? Errors like that started popping up a year or so ago when Microsoft started enforcing depreciated protocols.
This page might be worth a read. Scroll down to the section that specifically mentions this error - it has some suggestions in addition to the registry mod listed above:
//theitbros.com/this-computer-cant-connect-to-the-remote-computer/
Can you successfully remote to a host session via the RDGateway?
1
· · ·
Jalapeno
OP
flemos89
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Allferry can you create a local user with admin rights and give it a go?
Also, is the SSL correctly deploy to the local machine? Are the DNS correctly configured? I'm getting out of ideias, because i've seen the same error resolving with the reg key added, as you can see here.
- AllferryPoblano
0
· · ·
Poblano
OP
Allferry
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Thanks Da_Schmoo , unfortunately none of those problems represent mine. I give some a shot but still the issue. I have a wildcard cert, machines are patched. I can remote connect to my RDS server as per normal but not from the RemoteApps.
- Da_SchmooMace
0
· · ·
Poblano
OP
Allferry
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
flemos89 I can create a user and try, thou i have tried with multiple accounts but not avail. DNS is fine, and i haven't deployed the SSL to clients machines. I never had the need to do thid before with a previous RDS Server.
- flemos89Jalapeno
0
· · ·
Poblano
OP
Best Answer
Allferry
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Hi all,
I managed to fix this issue. I noticed that when trying access my RemoteAPPs in FireFox I get the errors and it was saying insecure...TLS 1.0. Só i when to Server registry and couldnt find any keys. I created TLS keys for 1.0, 1.2, 2.0 for client and server and all worked.
Thanks for you help, all.
0
· · ·
Pure Capsaicin
OP
DragonsRule
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Microsoft Remote Desktop Services expert
102 Best Answers
339 Helpful Votes
TLS 1 really isn't secure anymore so shouldn't be used.
0
· · ·
Poblano
OP
Allferry
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
My mistake, TLS 1.0 was added automatically, and I had to add tLS 1.2 and 2. Server is now using TLS 1.2 and working fine.
Again, thank you all for your help.
0
This topic has been locked by an administrator and is no longer open for commenting.
To continue this discussion, please ask a new question.