It looks like the server is making a seperate connection back to the client, kind of like ftp. This (unfortunately) doesn't work with ssh tunnelling. http://docs.jabber.org/general/html/protocol.html Another option is to ssh tunnel your application, or use VNC/tightVNC. On Thu, 15 Nov 2001, Bob Tanner wrote: > Quoting Clay Fandre (clay at fandre.com): > > That should work since jabber uses a single connection for everything. What problems are you having? Add the -v option to ssh to get more info. Are you sure that's the correct port? > > > > BTW, you can use -N option to just forward ports. > > > > -N Do not execute a remote command. This is useful if you just want > > to forward ports (protocol version 2 only). > > Interesting with the -N I get a core dump ala Bug Buddy. Debug input follows: > > debug1: Connection to port 5222 forwarding to jabber.org port 5222 requested. > debug1: fd 8 setting O_NONBLOCK > debug1: fd 8 IS O_NONBLOCK > debug1: channel 2: new [direct-tcpip] > debug1: channel 2: open confirm rwindow 32768 rmax 16384 > debug1: channel 2: rcvd eof > debug1: channel 2: output open -> drain > debug1: channel 2: obuf empty > debug1: channel 2: output drain -> closed > debug1: channel 2: close_write > > -- > Minneapolis St. Paul Twin Cities MN | Phone : (952)943-8700 > http://www.mn-linux.org Minnesota Linux | Fax : (952)943-8500 > Key fingerprint = 6C E9 51 4F D5 3E 4C 66 62 A9 10 E5 35 85 39 D9 > > _______________________________________________ > Twin Cities Linux Users Group Mailing List - Minneapolis/St. Paul, Minnesota > http://www.mn-linux.org > tclug-list at mn-linux.org > https://mailman.mn-linux.org/mailman/listinfo/tclug-list