> >Just to make sure I'm understanding: Do I then set the DISPLAY environment
> >variable on the client to the firewall IP address?
>
> Yes, you point your clients to the firewall IP as if the remote X client
> was the firewall itself.
Wasn't clear there sorry that is correct.
> >Does this solution keep me from simultaneously supporting X servers on
> >both the Linux firewall and the NT machine?
>
> I beleive so. If you choose to forward X into your internal LAN, you can't
> also remotely display X windows nto the firewall too.
Not quite, the X protocol allows for a number of displays on a single
machine, numbered form 1-10 and listening on ports 6001-6010 the export
syntax being: export DISPLAY=<my.ip.address>;0-10. You will have to find
out what the syntax on the X server is to force it to listen to a
different port on the linux machine.
> Also.. I would NOT recommend to mearly do a X window port forward since
> its NOT secure. Do some research and impliment SSH X-Windows
> forwarding. Not only will it give you security but PERFORMANCE. SSH
> has built-in compression!
Neither would I but he said that he had an X server running on NT (which
I'm not sure if there is an X forwarding implmentation of ssh for) already
so I assumed he had met and dealt with the security issues already. But
yess X oover ssh is a much nicer idea in terms of security and speed.
--
Tim Fletcher .~.
/V\ L I N U X
[EMAIL PROTECTED] // \ >Don't fear the penguin<
[EMAIL PROTECTED] /( )\
^^-^^
The most exciting phrase to hear in science, the one that heralds new
discoveries, is not "Eureka!" (I found it!) but "That's funny ..."
-- Isaac Asimov
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
http://tiffany.indyramp.com/mailman/listinfo/masq
Admin requests can be handled by web (above) or [EMAIL PROTECTED]
