asked on RemoteApp Disconnected - This computer can't connect to the remote computer.
I've been spending hours using google, etc., to try to figure this out myself, but I'm coming up blank. Everything was working perfectly 2 days ago. Since then, I replaced the Comcast supplied cable/modem/router with a Zoom which forced me to change all of my internal IP numbering. I then "re-keyed" the SSL certificates that I use for the Remote Gateway and the Host Session and now I can't connect my RemoteApps (using .RDP files or RDWeb...). I'm thinking that the problem must be in the Remote Gateway, since I don't even get to the login screen using RDWeb!? Internally, from one of my workstations I get this error:
![RemoteApp-Disconnected.jpg]()
Externally, from an outside network, the .RDP connection prompts for credentials, then responds with this error:
![RemoteApp-Disconnected--2-.jpg]()
I'm guessing it must be something simple, but, as much as I really like the RemoteApp capability built into Windows, whenever ANYTHING changes, it always creates problems.
Externally, from an outside network, the .RDP connection prompts for credentials, then responds with this error:
I'm guessing it must be something simple, but, as much as I really like the RemoteApp capability built into Windows, whenever ANYTHING changes, it always creates problems.
Remote AccessWindows Server 2008
Last Comment
Natty Greg
since you change ip addressing you will have to update the dns to reflect the new settings and also the .rdp files (should have used \\servername vice \\192.168.x.x.\
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Couple of followup comments. First, I've taken the firewall out of the picture. I did have to change my public IP address for my Gateway server (thanks for that suggestion...). I'm using an alternate port (i.e. not using 3389) and this has worked fine for the past couple of years, so I'm convinced that this is not the issue. I still can't even get the login screen to display using the RDWeb functionality, yet I can ping my Gateway domain address with no problem. Something seems to be blocking access to the "https://www.mydomain.com/RDWeb/en-us" web page and until I can access thru RDWeb via my browser, obviously, I'm not going to be able to connect using my .RDP files. I've been trying everything I can think of and some basic setup options from a 3-part RemoteApp install and setup article I've used in the past!?
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
too bad you don't appear to have a setting in the cable modem/router to set your server in its DMZ
ASKER
Gave the points for the tip to check my public IP address after the cable modem switch, and this turned out to be a part of the problem since my domain name was still pointing to my prior IP address. If I hadn't made this change, then I would still be working on this!
thank you
trace the server IP ...
all the best