RE: TSAC behind ISA
- From: "Jay J. Mobley" <jmobley@xxxxxxxxxx>
- To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
- Date: Tue, 1 Jan 2002 18:57:02 -0800
The TSAC is just a web page. Publish it like you would publish any other
WWW service.
Once your clients hit "connect" however, the browser runs and ActiveX
control to start the RDP client
Now you'll need to publish terminal service. (port 3389)
-----Original Message-----
From: John Paul [mailto:jkeesy@xxxxxxxxxxx]
Sent: Tuesday, January 01, 2002 5:31 PM
To: [ISAserver.org Discussion List]
Subject: [isalist] TSAC behind ISA
http://www.ISAserver.org
Sorry this is so long, but I want to make sure ya'll have all the info
you
need.
Maybe I haven't read enough of the 'Learning Zone' or the message
boards,
but I can't seem to find the answer to my question. It could be I need
more sleep, maybe later.
Question:
How do I setup TSAC to work on a DC other that the one running ISA?
Our network configuration:
This is a MS Backoffice 2000 setup with 3 servers.
1st server (will call it A) is running W2K server, SP 2 w/all patches &
hot fixes (DC) with normal print & file sharing, Exchange 2K (SP 2) ,
IIS
(with a basic home page), ISA server, and Terminal Server that installed
with the Backoffice installation.
2nd server (will call it B) is running W2K server, SP 2 w/all patches &
hot fixes (DC) with normal print & file sharing, IIS (no home page), MS
Access (installed according to MS TechNet installation to work with
Terminal Server), and TSAC.
3rd server (will call it C) is running W2K server, SP 2 w/all patches &
hot fixes (DC) with normal print & file sharing, SQL 2K, and Terminal
Server that installed with the Backoffice installation.
None of these servers have the firewall client installed, just SNAT.
They
can all get to the web just fine. We are connected to the Internet via
SDSL with 5 public IP's and a Netopia R9100 router. Server B has 2
NIC's,
one for the ISP (North) which is connected to the router and one for the
internal network (South) connected to a switch. Servers A & C both have
only 1 NIC a piece and connected to the switch.
With what I learned in the Learning Zone, I have setup ISA server and it
is running great. OWA works and the home page is running fine. All the
clients can browse the web. Thanks in advance for the great articles
that
allowed for a flawless install.
I would like to run the TSAC on server (B) because it will be running
multiple instances, eventually 15 to 20, of MS Access 2000 that will be
connecting to the SQL server. This is not a true client server
application running, so most of the processing will be done on this
Terminal Server. For that reason this server (B) is a Dell PE 2500 Dual
PIII 933 2GB RAM w/3 18GB HD on a hardware RAID controller, set for RAID
5. This server is better that the server (A) one which is a mere PII
400
1 GB RAM (these details probably bore you, sorry).
Anyway, after getting everything setup and running for this client, I
added the other public IP's to the north NIC. Guess what...I can not
ping any of them. I followed the article for publishing TSAC behind the
ISA server, but it still does not work. If possible I want the users to
connect to the TSAC by IP address (e.g. http://133.133.133.133/tsac).
Any help will be greatly appreciated.
PS I need this to be fairly secure as this client has to conform to
HIPPA
security and privacy laws.
Thanks again for anyone's help,
John Paul Keesy
KeeWell Consulting, Inc.
10615 Holly Grove Dr.
Ft. Worth, TX 76108-4611
817.975.3838 business
817.367.2839 fax
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
jmobley@xxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
Other related posts:
