RE: Problem Timeout after 240 Sec on rdp session over ssl

  • From: "Thomas W Shinder" <tshinder@xxxxxxxxxxx>
  • To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
  • Date: Wed, 22 Feb 2006 06:22:13 -0600

Please study this
http://www.isaserver.org/tutorials/Publishing-Remote-Desktop-Web-Connect
ion-Sites-ISA-Firewall-Part1.html so you don't make the same conceptual
error again.

Thomas W Shinder, M.D.
Site: www.isaserver.org
Blog: http://spaces.msn.com/members/drisa/
Book: http://tinyurl.com/3xqb7
MVP -- ISA Firewalls

 

> -----Original Message-----
> From: choub [mailto:m.laffargue@xxxxxxxxx] 
> Sent: Wednesday, February 22, 2006 6:02 AM
> To: [ISAserver.org Discussion List]
> Subject: [isalist] Problem Timeout after 240 Sec on rdp 
> session over ssl
> 
> http://www.ISAserver.org
> 
> hi everyone,
> we have a problem with rdp sessions over ssl.
> 
> situation:
> Isa server STD 2004 SP2
> 
> Internal-User ---> 
> InternalCard-ISA<--->ExternalCard-ISA<--->Appliance FW<--->WEB.
> 
> 1. Internal user connect to http External site and etablish ssl
> connection. this step is Ok.
> 
> 2. after ssl connection etablished, user click on link that 
> enables rdp
> session. no problem here, (ActiveX download).
> 
> 3. user works fine, but, if there is no traffic during 5 minutes, a
> timeout message arrives.
> 
> 4. with only appliance FW we have no problem
> 
> 
> ------------------------------------------------------
> 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
> ------------------------------------------------------
> Visit TechGenix.com for more information about our other sites:
> http://www.techgenix.com
> ------------------------------------------------------
> You are currently subscribed to this ISAserver.org Discussion 
> List as: tshinder@xxxxxxxxxxxxxxxxxx
> To unsubscribe visit 
> http://www.webelists.com/cgi/lyris.pl?enter=isalist
> Report abuse to listadmin@xxxxxxxxxxxxx
> 
> 


Other related posts: