Mine still does Tom, all patched and up to date. Steve -----Original Message----- From: Thomas W Shinder [mailto:tshinder@xxxxxxxxxxxxxxxxxx] Sent: Wednesday, October 02, 2002 4:27 PM To: [ISAserver.org Discussion List] Subject: [isalist] Cannot Publish Terminal Services on a Alternate Port http://www.ISAserver.org Hey guys, A while ago there was some discussion on how to publish TSAC sites to an alternate port. The hack was to move the Windows XP TSAC files over to a Windows 2000 machine and then change some parameters in the connect.asp file. If you download the new TSAC Web client software, you'll notice that there is no connect.asp file. So, there's no way to change the port number the clients use to connect to the Terminal Server. There are entries in the default.htm file that look like they might do the same thing, but they don't work. You might think "well, this isn't a problem, because I'll just use the Windows XP files". However, if you apply the latest security updates to IE, you'll find that you won't be able to connect to the old TSAC site :-( So, with the new TSAC web client, you're stuck with TCP 3389. HTH, Tom www.isaserver.org/shinder ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Exchange Server Resource Site: http://www.msexchange.org/ Windows Security Resource Site: http://www.windowsecurity.com/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: steve@xxxxxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')