Remote desktop web access
HI, our terminal server went down, which was windows 2008. we had termnal server runing on it and it worked great, with ts gateway and web access etc.
rebuilt it but with windows server 2008 Rd, which is now remote desktop server. pretty similar but slightly different.
anyway, ive got everything installed and all services up and running, and ive reinstalled the ssl certificate i had previously on the server and the licensing server and the required remote apps and everything seems fine. created CAP and RAP etc but the TS gateway server doesnt work - users get the following message:
your computer cant connec to the remote computer because the remote desktop gateway server is temporarily unavailable.
im guessing its either IIS because i cant browse internally to the web access page, or its the SSL certificate which worked on the server prior to it being rebuilt, and i possibly need to request a new one?
please help, im desperate!!
thanks,
Rhys.
rebuilt it but with windows server 2008 Rd, which is now remote desktop server. pretty similar but slightly different.
anyway, ive got everything installed and all services up and running, and ive reinstalled the ssl certificate i had previously on the server and the licensing server and the required remote apps and everything seems fine. created CAP and RAP etc but the TS gateway server doesnt work - users get the following message:
your computer cant connec to the remote computer because the remote desktop gateway server is temporarily unavailable.
im guessing its either IIS because i cant browse internally to the web access page, or its the SSL certificate which worked on the server prior to it being rebuilt, and i possibly need to request a new one?
please help, im desperate!!
thanks,
Rhys.
ASKER
also if i go to web acess administration it says certificate error when it goes to
https://localhost/rdweb etc which id expect but it also does it when i browse to:
https://servername.domain/rdweb etc and this matches with the ssl certificate.
i never had this problem with terminal sever on the 2008 version prior to r2 but again it may be the certificate although it has happily accepted it
https://localhost/rdweb etc which id expect but it also does it when i browse to:
https://servername.domain/rdweb etc and this matches with the ssl certificate.
i never had this problem with terminal sever on the 2008 version prior to r2 but again it may be the certificate although it has happily accepted it
ASKER
hi, i didnt do that previously, we have a lot of external people who partner with us who logged in via web access, they just went to teh page and it made the ssl connection through teh gateway seamlessly
thanks,
rhys.
thanks,
rhys.
ASKER
i also get the error message "HTTP Error 503. The service is unavailable" if i ignore the certificate warning errors in internet explorer
ASKER
ok, i ve managed to suss out that the rdweb application pool in IIS keeps stopping all the time too, not sure if that has any effect on the gateway issue but thought id mention it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Worked out the solution through trial and error and diagnostics. no other answers forthcoming
Also check if the App pool is stopped altogether. This seems to be the default state right after installing the role service.
if so did you add the cert to the trusted root store on the client machines ?