Your computer cant connect to the remote computer because the remote desktop gateway server address
SymptomsWhen this issue occurs, you receive the following error message that prevents you from accessing the Remote Desktop Services (RDS) server: Show
Hotfix informationImportant Do not install a language pack after you install this hotfix. If you do, the language-specific changes in the hotfix will not be applied, and you will have to reinstall the hotfix. For more information, see Add language packs to Windows.
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. PrerequisitesTo apply this hotfix, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows Server 2012 R2. Registry informationTo use the hotfix in this package, you do not have to make any changes to the registry. Restart requirementYou may have to restart the computer after you apply this hotfix. Hotfix replacement informationThis hotfix does not replace a previously released hotfix. your computer can't connect to the remote computer because the remote desktop gateway server address is unreachable or incorrect
Answers
All replies
Below is not an exhaustive list of connection errors, it’s just a some things that have tripped me up. If you have a nasty error that you have fixed, feel free to drop me a line, send me some screenshots and the fix, and I’ll add them as well. RDP error: This computer can’t connect to the remote computerChipotle
OP
I had exactly the same error message however it was working the day I setup but next day it just died. However, my setup wasn't as like your external and internal - mine is purely internal. I tried everything deleting certificate from IIS, RDP server, and client. Re-creating and assigning but none worked. one thing I remembered as I was going thru the whole suite of RDP components: RDP Manager, RDP Session Host, RDP Remote App etc etc... I found: RemoteApp Manager > RD Host Session Server Setting (click Change) > RD Gateway tab and ticked Automatically detect RD Gateway Server Settings. Then I restarted the Remote Desktop Gateway service and what do you know...DAMN THING ACTUALLY WORKED!!! Wooohoooo... So you might want to check in your environment this might help.... Cheers, IT
1
· · ·
Jalapeno
OP
Hey thanks for the reply, I tried to turn them to automatic and the results are not any better. Instead of the certificate error I know get an error stating: The gateway server you are trying to contact it temporarily unavailable. It is actually working internally and I have rebuilt this server more than once. I have even gone as far as setting up a test environment to try to resolve the issues I see from a far. However nothing has worked yet, Microsoft's instructions to get this working are designed for internal use only and are convoluted to say the least. There is very little instruction or even experience around the external access for this service. I have already dumped so many hours into this, I am almost looking for a alternative solution. maybe I will just open a VPN tunnel to allow remote access to the server.
0
· · ·
Chipotle
OP
Your main issue here is that externally not able to access - correct? 1-) I think you might want to try putting it on your DMZ just for test. 2-) Assuming that you have done the routing on your firewall? 3-) Assuming you have mapped to external IP (NATing)and published the URL externally? 4-) Check the port the RDP WebAccess connecting on - you need to open that port on your firewall. 5-) Assuming you have configured HTTPS traffic for this site with port?
0
· · ·
Jalapeno
OP
Best Answer
This has been resolved. It was a problem with the certificate and where I was creating it from. I was creating a self-signed cert from IIS. in order to specify my external domain I had to create the self signed certificate through the RD gateway manager. After I did this BOOM everything was working.
1
· · ·
Chipotle
OP
Good work!
0
· · ·
Pimiento
OP
Please Can you explain what you did exactly to solve that issue ??!!
0
· · ·
Serrano
OP
Running into this problem ourselves, an explanation would be most appreciated :)
0
· · ·
Pure Capsaicin
OP
Little Green Man
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
See Bold.
0
· · ·
Pure Capsaicin
OP
Little Green Man
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
See above BA.
0
· · ·
Pimiento
OP
If you still need help with this, I can expalin. I don't want to go through the trouble though if you don't need it, so let me know by replying.
0
· · ·
Jalapeno
OP
Sorry Bill, I haven't circled back to this in quite sometime. Basically there are multiple ways to issue a self signed certificate to a server. In this particular situation there is three, one through IIS manager, one through the certificate MMC snap-in, and one through the RDP gateway properties. The third place is where I was able to associate my server with my external domain and have it self sign. Once I created the certificate through the RDP gateway settings my website was loading my applications. I hope this helps.
0
· · ·
Sonora
OP
Hello all, One of my clients had a certificate expire on their server yesterday and now all the users are getting the following error on their desktop. I issued a new certificate (Renewed) on the server and it took care of the local computer errors, however, the remote desktop users from outside the organization still can't get Or this... RWA users can't remote desktop in because they get this error... And when you view certificate, the install certificate button is missing (See below) I "copied to file" and installed it to the Trusted Root Cert folder, but they still can't get access through remote desktop. Any help would be greatly appreciated! I'm trying to learn this certificate stuff...
0
· · ·
Pimiento
OP
Were you able to resolve your issue? If so I would like to know how this was resolved.
%uFEFFI am having a similar problem with a traveling user and it references the Hotel's wireless certificate. There is no "install" option. Thank you. ~Lynn
0
· · ·
Ghost Chili
OP
starg33ker
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Hilynntober-rice2, welcome to SpiceWorks! When you see that there's been a "best answer" marked, that means the issue has been resolved. The poster mentioned the solution here http://community.spiceworks.com/topic/post/2521776 If this does not fix your issue, I would recommend you starting a new topic as you'll receive little to no help in a 2 year old thread. Hope to see you around!
2
9 Replies· · ·
Mace
OP
bbigford
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
My knee jerk reaction is check your firewall rules/port forwarding/authentication groups pointing to any internal authentication servers using something like RADIUS. Are you using RADIUS for authentication? If so, check your NPS authentication group(s).
2
· · ·
Mace
OP
Justin1250
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Can you manually use the RDG from the outside?
1
· · ·
Pure Capsaicin
OP
dbeato
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
My recommendation is pretty much close to the other ones. Check that the RD gateway is accessible through the public IP as well. Trace the configuration same as your working environment and make sure it matches your configuration obviously with different IP addresses but same logic.
2
· · ·
Jalapeno
OP
Sorry don't know how to answer this yet. I never had to configure this part manually even on the existing working RDS. I'll get back to you on this. I only setup the RD CAP and RAP and they seem to be correct.
0
· · ·
Jalapeno
OP
I can access the FQDN and IP of the Gateway from external and internal (had to add DNS forwarders internally). Right now the setup is single server (public IP > single server). Public IP works and I have tried two different Public IPs just to isolate the forwarding rules as well.
0
· · ·
Jalapeno
OP
I'm clueless, even with running BPA doesn't show any errors. Tried different remote locations and computers and they all seem to give the same result.
0
· · ·
Jalapeno
OP
Best Answer
Thanks for the input guys. I figured out my issue. Based from the information I provided above and the BPA result, it kinda suggested that there wasn't an issue with my RDS config. I reviewed my network settings and updated it it to a simpler structure. Works well now.
0
· · ·
Mace
OP
bbigford
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
Can you provide more input about what you changed? Something with your firewall/etc? You mentioned a "simpler network", please elaborate on that.Definitely helpful to people in the community, as well as anyone online that stumbles upon this thread, to give some clarity about what specifically resolved your issue, if no suggestions in here were helpful.
2
· · ·
Jalapeno
OP
Can you provide more input about what you changed? Something with your firewall/etc? You mentioned a "simpler network", please elaborate on that.Definitely helpful to people in the community, as well as anyone online that stumbles upon this thread, to give some clarity about what specifically resolved your issue, if no suggestions in here were helpful. Well basically my main network is on 10.0.0.xx with 255.255.0.0 and I was trying to build the new RDS environment on 10.0.12.xx. I can ping everything from anywhere internally so I never thought it would be an issue. I would say, I haven't found the real cause of issue or mis-configuration I made. But placing the new RDS environment on the same octet with the prod network made it easier. My network is simple, no vlans or complex routing, but would need to revisit placing the RDS network to a different octet next time. does that make sense?
1
Your computer can’t connect to the remote computer because the Remote Desktop Gateway server address is unreachable or incorrect – RemoteApps, Windows server2012R2Posted: December 23, 2020 in Windows Server0 We have Remote Desktop apps hosted on Windows server 2012 R2, for past few years. Everything worked fine for years, then suddenly, we started to get following error: “Your computer can’t connect to the remote computer because the Remote Desktop Gateway server address is unreachable or incorrect. Type a valid Remote Desktop Gateway server address” Opened https://remote.example.com/RDWEB, type credentials, remote apps are shown, then after clicking on application, again prompted for password and getting error above.Restarted RDP gateway, recreated Remote session no help. The strange things is that all works fine from the LAN, but not from the internet. Even stranger things is that Remote Application can be launched from mobile phone outside company network. After some googling, found a “fix”, on machines from which tried to launch Remote App ( reg.exe Add "HKCU\Software\Microsoft\Terminal Server Client" /V "RDGClientTransport" /T REG_DWORD /D "1"
It started to work,but, according to this thread , traffic is sent using HTTP , in other words, in plain text. So tried to find other solution. In Remote properties of RDP Gateway, server, unchecked “Allow connections only from computers Running Remote Desktop with Network Layer Authentication (recommended) “ Then, on client machine removed registry “fix” and finally was able to launch remote app from the internet. Just for curiosity, captured packets between client computer and RDP Gateway with Wireshark, and traffic was encrypted Share this:Like this:Like Loading... RelatedLeave a Reply Cancel replyEnter your comment here... Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/ Change) You are commenting using your Google account. (LogOut/ Change) You are commenting using your Twitter account. (LogOut/ Change) You are commenting using your Facebook account. (LogOut/ Change) Cancel Connecting to %s Notify me of new comments via email. Notify me of new posts via email.
Δ |
