Re: [FW1] X11 protocol outward bound

[Cameron Palmer]

Title: X11 protocol outward bound

Because the connection is initiated from within.  So there is no state for the protocol.  The best solution is SSH tunneling.   cameron. ----- Original Message ----- From: Cubelic, Ivan To: 'Cameron Palmer' ; [EMAIL PROTECTED] Sent: Wednesday, February 28, 2001 20:44 Subject: RE: [FW1] X11 protocol outward bound Yeah, the cost is too pricy.......   I wonder why other services are able to travel back and forth, however X11 can't (without using AnyInternalNetwork) -----Original Message----- From: Cameron Palmer [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 01, 2001 3:40 PM To: Cubelic, Ivan; [EMAIL PROTECTED] Subject: Re: [FW1] X11 protocol outward bound Allow an AnyInternalNetwork to NegatedAnyInternalNetwork AnyService outbound rule.  This will allow the traffic to flow back to the client.  Unfortunately this opens a big hole.  Otherwise I suggest tunneling with SSH.   cameron. ----- Original Message ----- From: Cubelic, Ivan To: '[EMAIL PROTECTED]' Sent: Wednesday, February 28, 2001 18:09 Subject: [FW1] X11 protocol outward bound Hi all, I have a user who wants to access his HPUX servers from home. I have him authenticating through Checkpoint SecuRemote v4.1 and when I look at the firewall logs, I can see that the X11 protocol is coming into the LocalEncryptionDomain fine. However, the X11 protocol doesn't seem to be able to get back out to my remote user. How can this be? How can this be resolved? Step by step would be nice Ta Ivan