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 Thor@xxxxxxxxxxxxxxx on 12/12/2001 06:13:45 PM 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 11:45 AM 12/12/2001, you wrote: >http://www.ISAserver.org > > > > From the ISA server, I can terminal server into it by it's internal IP >address (172.16.7.10), but if I try to terminal server into 192.168.254.102 >- which is the ip I published it to in my rule, it doesn't respond. The ISA >server's internal NIC is 172.16.7.1 > >Thanks, >Andrew You try to TS into 192.168.254.102 from where? I'm confused on how you got this NAT thing to work- how can the outside world hit 192.168.254.102? AD -----BEGIN PGP SIGNATURE----- Version: PGP 7.1 iQA/AwUBPBfkqYhsmyD15h5gEQInogCdHoD1SWoH8VMT8GhrlrttHWoUUf4An3mp eqIwMwuCoWj4jrgFFHtww+YP =t1D7 -----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')