If your referring to the internal interface on the ISA Server, Yes, it is. Thanks for the reply. Chris -----Original Message----- From: Dan Bartley [mailto:bartleyd@xxxxxxxxxxxxxxxxxxx] Sent: Tuesday, June 03, 2003 7:28 PM To: [ISAserver.org Discussion List] Subject: [isalist] RE: TSAC Issue http://www.ISAserver.org Make sure you have terminal services bound to the internal interface. That is the most common problem. Best Regards, Dan Bartley Senior IT Manager NetCarrier Inc. bartleyd@xxxxxxxxxxxxxxxxxxx <http://www.netcarrier.com/> http://www.netcarrier.com Direct Phone: 215.966.3310 _____ From: Christian Villeneuve [mailto:Christian.Villeneuve@xxxxxxxx] Sent: Tuesday, June 03, 2003 19:23 To: [ISAserver.org Discussion List] http://www.ISAserver.org Hello. I am wondering if anyone can shed some light on this one, because I am not able to get it to work. I am trying to use the Terminal Services Advanced Client to access a Terminal Server on my internal network, but it always gives me this error. "VBScript: Remote Desktop Disconnected. The Client could not establish a connection to the remote computer. The most likely causes for this error are : 1) Remote connections might not be enabled at the remote computer. 2.) The maximum number of connections was exceeded at the remote computer. 3.) A network error occurred while establishing the connection." I followed the "Publishing Terminal Services and the TSAC Client - Updated document on the ISAserver.org site, as well as the "Publishing Windows 2000 Terminal Services to a Non-Standard Port" doc, and the ISA 2000 bible, but still to no avail. I started simple with creating a Packet filter and I am able to get to my ISA Server. I then tried to create a protocol rule, and used Server Publishing and I am able to get access to my ISA Server. I did change the encryption level to high on the ISA Server and I published it using the internal interface on the ISA Server. I also changed my ISA's registry to listen on a different port. All is working fine. My problem is that I can't get access to an internal server running Terminal Services on port 3389. I followed the docs, but am I missing something or doing something wrong? Thanks in advance. Chris ------------------------------------------------------ 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 ------------------------------------------------------ Other Internet Software Marketing Sites: Leading Network Software Directory: http://www.serverfiles.com No.1 Exchange Server Resource Site: http://www.msexchange.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: bartleyd@xxxxxxxxxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub') ------------------------------------------------------ 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 ------------------------------------------------------ Other Internet Software Marketing Sites: Leading Network Software Directory: http://www.serverfiles.com No.1 Exchange Server Resource Site: http://www.msexchange.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: Christian.Villeneuve@xxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')