Hi Tim, Thanks for the quick reply. Unfortunately, its not a firewall issue. There is a firewall on the remote machine, but only on the external side - I'm ssh'ing in from the internal side on a different eth. I'm also not doing a second telnet / ssh. In any case, that would not explain why ssh remote.machine /usr/X11R6/bin/xclock works and foward x-apps correctly while ssh remote.machine by itself does not forward x correctly. Regards, Raj. "Evans, Tim" wrote: > > Can anybody suggest a > > reason / solution for this bizarre behaviour? Thanks. > > My Solaris system works right. > > To begin with, recognize that, as currently setup on the firewall, you can > only 'ssh' directly to 'mail.' If you then oo to another host, via ssh or > any other protocol such as 'telnet,' you will have lost x-forwarding > capabilities; your $DISPLAY doesn't follow you, and you can't reset it > manually. > > This could be resolved by assigning other port numbers for the firewall > redirects to other internal hosts. That is, for example: > > ssh -p 2222 www.dbi.tju.edu <--takes you to 'mail' > ssh -p 2223 www.dbi.tju.edu <--takes you to 'blade1' > > This takes a bit of fixup, but can be done. > -- > Tim Evans, T.Rowe Price Investment Technologies | [EMAIL PROTECTED] > P.O. Box 89000, Baltimore, MD 21289-0374 | (410) 345-8134 > http://www.troweprice.com/ | (410) 345-8150 (Fax) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
