Hi Bob, What part isn't working? Remember that you can't publish an internal Terminal Server if the Terminal Server on the ISA Server itself is listening on the external interface of the ISA Server. If you change the listening adapter to the internal adapter, then TCP 3389 should not be listening on the external interface. Then create the Server Publishing Rule to publish an internal Terminal Server. BUT, this won't work if you're making the changes remotely via TS, because you *need* that connection to make the configuration changes, but that connection *cannot* be active in order to make it work! It must be done *at the console*. If it makes you feel any better, I painted myself in the same corner once myself :-) HTH, Tom www.isaserver.org/shinder -----Original Message----- From: Bob Cheeseman [mailto:bob@xxxxxxxxxxx] Sent: Saturday, January 05, 2002 12:43 PM To: [ISAserver.org Discussion List] Subject: [isalist] How to Server Publish a Terminal Server with ISA while also running Terminal Services on the ISA Server (Q294720) http://www.ISAserver.org So, We read Thomas's book, followed all the instructions, and couldn't get our internal terminal server to work. kept connecting to isa server or no connection at all. Went to Microsoft's site and followed the instructions on the above noted document. Both of us read this document several times and agreed that if we followed step 3 we would be screwed. But we tried it anyway. Step Three: Bind Terminal Services on the ISA Server to the Internal Adapter on the Server To bind Terminal Services on the ISA Server to the internal adapter on the server, perform the following steps: Click Start , point to Programs , click Administrative Tools , and then click Terminal Services Configuration . Click the Connections folder, and then click the RDP-TCP connection. Right click this connection and click Properties . Click the Network Adapter tab and click to select the Internal network adapter in the Network Adapter check box. NOTE : By default, Terminal Services binds to All network adapters configured with this protocol . Therefore, you will need to set it specifically to the internal adapter. :( Now our day is done. We can no longer connect to any server via terminal services. Just what we thought would happen. we were working remotely, and there is no one in the office to change the setting back. Oh well, Monday is another day as they say. Bob ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: tshinder@xxxxxxxxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')