[FreeNX-kNX] getting to my freenx box at home from work

[Jim McNelis]

Thanks for the tips. I think what I'm finding is that the issue is with the
proxy server here at work. NXClient 1.5 is not proxy-compliant and HTTPort
is not helping. Probably our corporate proxy has CONNECT functionality
disabled. Has anyone tried NX version 2.0? The change list talks about
implementing proxy compliance for the NX client.

On 6/26/06, Jay Zach <jayspam at zachfamily.org> wrote:
>
> On Friday 23 June 2006 6:44 pm, Jim McNelis wrote:
> > I've searched this archive and couldn't find an answer that worked for
> my
> > situation. But I suspect I'm not alone so here goes:
> >
> > I have 2 Linux PC's at home behind a wireless router/firewall. I
> installed
> > freenx on one of them and have sshd and nxserver configured to listen on
> > port 8888. I know it works because I can access that desktop from my
> other
> > Linux PC at home.
> >
> > My problem is accessing my home freenx server from work. I setup port
> > forwarding on my wireless router (for ports 22 and 8888). I also have a
> > dyndns account setup to have a hostname for my home router. At work I
> have
> > a WinXP workstation (hold the boos) and it sits behind a corporate
> > firewall. Access to the web at work is via a proxy server. I've
> installed
> > the Windows NoMachine client and pointed it at my dyndns hostname on
> port
> > 8888 but all I ever get is connection timeout errors. I read one thread
> > here about transconnect but our corporate web filter blocks proxy web
> pages
> > (including theirs) so I guess that's out.
> >
> > If somebody suggests port forwarding or tunneling, that's great but
> you'll
> > have to step me thru it cuz I'm fairly ignorant with all that. Is there
> any
> > way to get this to work or do I pursue something like echoserver
> instead?
> >
> > Any help is mucho appreciated!
>
>
> Instead of port forwarding to 8888 straight through on your wireless
> router,
> you might try forwarding port 443 on the wireless router to 8888 on your
> box
> running NX.  That way if your proxy is blocking all ports besides 80 and
> 443,
> you can still get through.  This trick has worked nicely for me before. :)
>
>
> --
>
> --------------------------------------------------------------------------------
>
> tmps_base = tmps_max;                /* protect our mortal string */
>              -- Larry Wall in stab.c from the perl source code
>
> Monday Jun 26, 2006
>
>
> --------------------------------------------------------------------------------
>
>
> ________________________________________________________________
>      Were you helped on this list with your FreeNX problem?
>     Then please write up the solution in the FreeNX Wiki/FAQ:
>   http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
>          Don't forget to check the NX Knowledge Base:
>                  http://www.nomachine.com/kb/
>
> ________________________________________________________________
>        FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>       https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20060627/a88d3f6e/attachment.html>