TS Web Access stopped working

Essendon

So TS Web Access was working just fine before I installed TS Gateway on my terminal server. Now, when I https://server3/ts to my TS from a client or from the TS itself, it throws an HTTP 404.0 - Not Found error.

The certificate issued by the CA is valid and the IIS service is running on my TS. I also chose "Do not use a TS Gateway Server" in the RemoteApp Deployment settings, just so the gateway side of things dont come in to the picture. I get the same error when I do a https://localhost/ts locally on my TS. I have also reinstalled all my RemoteApp programs after the gateway was installed.

TIA.

Essendon

Anyone?

Hyper-Me

does it work if you actually try to use the TS Gateway?

Essendon

Nope, it doesnt.

Actually, when I try to use the TS Gateway when accessing my TS (via an RDC) from a client machine, it throws me an error saying the TS Gateway Service server is unavailable. If I revert back to Automatically detect TS Gateway server settings or Do not use a TS Gateway Server, I am able to connect to my TS just fine.

BradH

I had an issue with my TS Gateway and the cert that it was using. For unknown reasons it was failing when I was applying a cert, and then prompting me to have the cert installed again when it already. This from memory caused some of the TS services to stop.

I then rebooted, re-applied the certificate to the TS Gateway and it started to work again.

Might assist.

Essendon

Easy fix in the end folks.

I had been thinking the whole time that the problem was with IIS, not with the terminal server. So I restarted my default web site, and WebAccess is up and running again. Well, I learned a bit doing all the troubleshooting, so time wasnt wasted.