Welcome to ISAserver.org

TSAC

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2000 General] >> Web Publishing >> TSAC

Page: [1]

Message

<< Older Topic Newer Topic >>

TSAC - 16.May2001 11:59:00 PM

cannibal

Posts: 2
Joined: 16.May2001
Status: offline

I am trying to set up the terminal server advanced client so that my network users may run it through our website. The web server and the ISA server are the same machine. Everything works fine from within the network itself, but from an outside location it gives an error that it couldn't connect to the server. Do I need to get another IP address to make the server name accessable or is there some way that I can reroute the terminal server request using ISA?
Any help would be greatly appriciated.

Post #: 1

Featured Links*

RE: TSAC - 17.May2001 4:48:00 PM

mmillar

Posts: 30
Joined: 17.May2001
From: London, UK
Status: offline

Cannibal,

Terminal Server runs on port 3389. You need to setup a packet filter which give access to this port. However, if you do this it means anyone on the Internet can get to the logon prompt of your server. We get round this by first creating a VPN connection to the server and then connecting to Terminal Services. You then don't need to open 3389.

(in reply to cannibal)

Post #: 2

RE: TSAC - 17.May2001 5:55:00 PM

cannibal

Posts: 2
Joined: 16.May2001
Status: offline

I want people on the internet to be able to access the terminal server logon, there will be a password authentication system so it will be pretty safe. What I don't understand is how to redirect the request. Is it actually the iis server requesting access to the terminal server or is it the client. If it is the client, then there has to be more to it since the client can't resolve the hostname of the terminal server without it having it's own external ip. If it was the server requesting the terminal server, then no routing should have to be done at all anyway. Am I correct on this?

(in reply to cannibal)

Post #: 3

RE: TSAC - 17.May2001 6:29:00 PM

mmillar

Posts: 30
Joined: 17.May2001
From: London, UK
Status: offline

Sorry Cannibal, I don't really understand what you mean.

* I am assuming your ISA server and Web server are running on the same machine.
* If you have a PC on the Internet then they must have an Internet IP address.
* If your ISA/Web server is on the Internet then it also must have an Internet IP address.

Your PCs on the Internet run up the Terminal Services 'Client Connection Manager', put in the IP address of your ISA/Web server and hey presto (so long as port 3389 is open) it works.

(in reply to cannibal)

Post #: 4