Re: Published Server (Terminal Services)
- From: Thor@xxxxxxxxxxxxxxx
- To: isalist@xxxxxxxxxxxxx
- Date: Mon, 10 Dec 2001 08:16:41 -0800
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
At 08:04 AM 12/10/2001, you wrote:
>http://www.ISAserver.org
>
>
>
>So, can I not use the regular 32bit client to access the terminal server
>behind ISA? Do I have to use the TSAC for all those connections?
>
>Thanks,
>Andrew
>
No, you don't have to TSAC to do it... I was going to post something about
the article saying you need to do that, but didn't. You don't have to set
up IIS or any of that stuff- and even if you do, it does not have to be on
the TS server either... As long as the client can reach the URL where the
TSAC is set up, that is all that is necessary. Further, the TSAC does not
allow you to change the TS port: it is hard-coded at 3389. I've tried to
hack it to allow a different port, but with no luck so far. The 32bit
client allows you to save the config to a file, where you can then change
the port the client uses (after changing the listen port on the server).
I thought you were going to go the VPN route... Still doing that, or will
you publish now?
I'm not sure how you will get around your NAT issue. You server publish by
IP, so the client will need to hit the external IP you publish...
AD
-----BEGIN PGP SIGNATURE-----
Version: PGP 7.1
iQA/AwUBPBTf6YhsmyD15h5gEQJqbwCg1mJj20TAINiP94VDA2QqUBuLm0AAoNFl
6E5+WMgd2/hUtoIDbSWiYrM0
=WggW
-----END PGP SIGNATURE-----
Other related posts:
