My experience is that, you can publish TS via ISA server, (If you use = that. That is my case) But you need to change the listening port of your = published server. I maked this worked when the internal server is on the = same subnet of internal NIC of ISA. But I had trouble when internal = server is on off-subnet IP of internal NIC of ISA. I didn't bother to = fix it. Because lately, I believe setup VPN connection before TS is a = better solution, which is more secure and you don't have to bothering = change listening port of server and TS client. Carson -----Original Message----- From: Rod Falanga [mailto:rfalanga@xxxxxxx] Sent: Wednesday, May 07, 2003 10:18 AM To: windows2000@xxxxxxxxxxxxx Subject: [windows2000] Is it necessary to make a VPN connection, before making a TS (or RDC) connection? Yesterday I attended a local Microsoft launch event for Windows 2003 =3D Server. One of the more interesting things for me was Terminal Services. =3D20 However, this raises a rather basic question for me. When setting up external clients to access our network we have first set up a VPN connection, and then had them go into the Terminal Services Client, in = =3D order to bring up a TS session. Is it necessary for them to first get a VPN connection? Or can they just bypass the VPN connection and use TS right off? Rod =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D To Unsubscribe, set digest or vacation mode or view archives use the below link. http://thethin.net/win2000list.cfm ================================== To Unsubscribe, set digest or vacation mode or view archives use the below link. http://thethin.net/win2000list.cfm