The external client has to be able to: 1. resolve the TS server name to an ISA-owned external IP 2. connect to the internal server via TCP-3389 (RDP) through the ISA. that means: 1. you need a DNS enry that points to a unique ISA-external IP for each internal TS server 2. a server publishig rule for each internal TS server Jim Harrison MCP(NT4, W2K), A+, Network+, PCG http://isaserver.org/authors/harrison/ Read the books! ----- Original Message ----- From: Alex Decarli To: [ISAserver.org Discussion List] Sent: Friday, July 05, 2002 9:45 AM Subject: [isalist] TSAC and ISA (vbscript error) http://www.ISAserver.org Does anyone has experencied the error Vbscript error: error connecting to terminal server: <terminalservername>. Isa server can access all terminal servers (netbios, ping). Telnet on 3389 port work. But externally.... no luck Thanks Alex Decarli ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: jim@xxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')