At 10:37 AM 4/27/01 -0700, Eddy Kalem wrote:
>Roy,
>
>Try setting the conn to 0:00:00. I think this will make it so the session
>doesn't timeout at all.
>
>EK
I just discovered the conn statement this morning.. can you specify a port
or something. I have the impression that it's kind of a global statement
and might be a problem leaving abandoned sessions... then again the 520 has
more connections than we'll ever use with just a class c behind it. At
least that's what my totally unscholarly thought is on the situation.
Roy
>-----Original Message-----
>From: Roy [mailto:[EMAIL PROTECTED]]
>Sent: Friday, April 27, 2001 6:45 AM
>To: '[EMAIL PROTECTED]'
>Subject: Xwindows on PIX
>
>
>I'm having a problem with Xwindows timing out. When someone comes in from
>the outside via telnet and then starts an X11 session on a server. They
>work for an hour and then time out, the default time out for the PIX. The
>problem is that the telnet session that started the x session get's no
>activity and when the pix times it out it also kills the X session.
>
>I ran into this problem a few years ago on a Checkpoint firewall and turned
>of a time out parameter that was global to the whole firewall. That didn't
>matter since it was in a lab environment.
>
>I'm a newbie on the PIX and never got past semi-newbie (I have a patten on
>that word along with the gene that makes presidential idiots)on the check
>point with a large lag in between, so you'll have to speak a little slower
>than normal :-)
>
>Thanks
>
>Roy
>
>-
>[To unsubscribe, send mail to [EMAIL PROTECTED] with
>"unsubscribe firewalls" in the body of the message.]
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
