Re: Publishing TSWeb
- From: Thor@xxxxxxxxxxxxxxx
- To: isalist@xxxxxxxxxxxxx
- Date: Tue, 7 Aug 2001 13:38:39 -0700
The client uses 80 to load the ActiveX control into its (the client's)
memory via the TSWeb interface. Once the ActiveX control in loaded on the
client, the client uses 3389 to get to the actual Terminal Server interface.
----- Original Message -----
From: Richard Manning
To: [ISAserver.org Discussion List]
Sent: Tuesday, August 07, 2001 1:28 PM
Subject: [isalist] Re: Publishing TSWeb
http://www.ISAserver.org
I thought Web Terminal Services would use default http port ( 80 ).
-----Original Message-----
From: David Dellanno [mailto:david@xxxxxxxxxx]
Sent: 07 August 2001 21:13
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: Publishing TSWeb
http://www.ISAserver.org
You need to create a Protocol Definition to allow port 3389 to enter
inbound traffic. Once you have created the protocol definition, then
you need to create a packet filter to allow that specific port through
ISA. Once that is set, you should be working from there, funny I'm
working on the documentation as we speak.
-----Original Message-----
From: Richard Manning
Sent: Tuesday, August 07, 2001 4:10 PM
To: [ISAserver.org Discussion List]
Subject: [isalist] Publishing TSWeb
http://www.ISAserver.org
Hello
I am running ISA, Exchange 2000, Win2000, IIS, DNS & AD all on the same
box. Exchange & IIS services published ok - eventually got my OWA
published through ISA after disabling socket pooling - but I still have
this one problem left - I am unable to publish Web Terminal Services
through ISA successfully.
I have installed the advanced ts client on the server.
I have created a destination set with a Name/IP Range of www.domain.com
and a directory path of /tsweb/*
I have web published this destination set choosing to redirect the
request to this internal web server ( internal ip address ) and to send
the original host header to the publishing server instead of the actual
one ( specified above ).
What happens is that I get the " Enter Network Password " box appear, I
login, then I'm confronted with the Windows2000 Terminal Services Web
Connection screen.
This is where it is failing. I try every combination of login. i.e.
internal ip, external ip, host name, send logon information for this
connection, don't send logon information for this connection - I am
stumped.
The error that appears is a VBScript " Error connecting to Terminal
Server". From inside the network it works fine.
Can anyone help?
Regards
Richard Manning
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
thor@xxxxxxxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
Other related posts:
