Try recreating the default protocol definition. I spoke to a M/S ISA Specialist on a unrelated issue and he said that it is common to have difficulty with the default rule. Are you able to connect to your Terminal Server coming inbound through the internet? This is my problem I am having with it. Cheers, Adam Houghton -----Original Message----- From: Richard Pettigrew [mailto:Richard@xxxxxxxxxxx] Sent: Tuesday, January 29, 2002 12:36 PM To: [ISAserver.org Discussion List] Subject: [isalist] RE: Terminal Services Client out through the firewall http://www.ISAserver.org You also must define a Packet filter for this port. -----Original Message----- From: Martin Kearn [mailto:MartinK@xxxxxxxx] Sent: 29 January 2002 15:58 To: [ISAserver.org Discussion List] Subject: [isalist] Terminal Services Client out through the firewall http://www.ISAserver.org How can I configure ISA server so that clients behind the firewall can contact terminal servers on the internet. On the client we are using the terminal services client tool supplied with Windows 2000, and the 'Remote Desktop Connection' tool built into Windows XP. We have created a protocol rule to allow outbound traffic on port '3389', but it still does not seem to work. We can ping both the IP address and host name of the terminal servers we are trying to access on the internet form our clients and ISA server. What are we missing? Regards Martin Kearn ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: richard@xxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub') ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: ahoughton@xxxxxxxxxxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')