Re: publishing terminal server
- From: <HCALM1@xxxxxxxx>
- To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
- Date: Thu, 13 Dec 2001 14:32:46 -0500
I'm not able to stop the terminal server client, don't know why. You know
my internal Terminal Server also a Citrix server. You know what rule I
would have to enable to publish that one to see if it works. I WAS able to
successfully publish my telnet server.
Thanks,
Andrew
Thor@xxxxxxxxxxxxxxx on 12/13/2001 10:01:25 AM
Please respond to "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
cc:
Subject: [isalist] Re: publishing terminal server
http://www.ISAserver.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
At 03:20 AM 12/13/2001, you wrote:
>http://www.ISAserver.org
>
>
>
>
>Sorry, I'm trying to terminal server into 192.16.254.102 from the other
>side of the ISA server, not the router. I've also tried from the actual
ISA
>server. I'm just trying to get this to work before I even worry about NAT.
>So I have to segmented networks, the 192.168 and the 172.16 networks.
>
>Hope that makes sense...
>
>Andrew
Yes- that makes sense. I'm just trying to get the full picture. Let's
start from the beginning:
1) You have Terminal Services running on the ISA box, but have gone into TS
Connections, and bound it only to the internal NIC.
2) You have Terminal Services running on your internal box at 172.16.7.1,
and have tested its operation internally.
3) You have defined a custom protocol definition for inbound tcp 3389 and
called it TServer or something.
4) You have created a Server Publishing rule, where you publish
192.16.254.102 (pretending it is an external address) to the internal
machine at 172.16.7.1.
After all of this, when you go to connect to 192.16.254.102 externally, you
get nothing, when you should get the internal TS box.
Is this all correct?
Just for giggles, let's try completely disabling TS on the ISA server
itself (stop the service) - though only bound to the internal, it has to
publish via the internal card, and I'm not really sure how that will pan
out. I have published terminal servers, and I have left only the internal
NIC bound to TS on ISA, but I have never done both at the same time- any
time I have published an internal TS, I have completely stopped the TS
service on the ISA box.
After you stop TS on the ISA, restart the firewall service... Let's see
where that takes us.
AD
-----BEGIN PGP SIGNATURE-----
Version: PGP 7.1
iQA/AwUBPBjCxYhsmyD15h5gEQLb+QCgpHjdThjOPApa6IT7M5eFuv5rXMcAn1tB
aAz00Dt3adtw7RISRpU19V6y
=2JJG
-----END PGP SIGNATURE-----
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
hcalm1@xxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
Other related posts:
