Date: Tue, 22 Mar 2005 10:25:55 -0600 From: "Andrew L. Gould" <algould@datawok.com> To: freebsd-questions@freebsd.org Cc: daniel <freebsd@danielquinn.org> Subject: Re: Accessing Windows XP Desktop (Home Edition) remotely Message-ID: <200503221025.55911.algould@datawok.com> In-Reply-To: <200503221102.48828.freebsd@danielquinn.org> References: <20050322155438.GC89505@ns2.wananchi.com> <200503221102.48828.freebsd@danielquinn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 22 March 2005 10:02 am, daniel wrote: > On March 22, 2005 10:54 am, Odhiambo Washington wrote: > > I have this big curse that I have to access the office computer > > from home. The office PC runs WinXP Home, not Professional. > > I have turned the Internet upside-down trying to get an app that > > will enable me access the goddamn XP desktop, using something like > > krdesktop, from home. Something that can run on the Windows XP and > > provide me access to it's desktop from a FreeBSD box running KDE. > > i'd suggest vnc: > http://www.realvnc.com/ > http://www.tightvnc.com/ > > you use realvnc to install the server, then tightvnc to connect (i > find it's faster than the normal vnc client. then to connect all you > need is X running and: > > $ vncviewer <ipaddress> > > security note: > vnc is *not* encrypted and is not generally considered secure. any > ports you open/forward should be directed to your ip only. even > better, try a knocking daemon. One of the advantages of running the tightvnc server is that it also runs a java web server so that you can access the tightvnc server from an internet browser without the use of a tightvnc client. The port number equals 5800 plus the windown number. For example, to access window 1 at 192.168.0.2, to go: http://192.168.0.2:5801 Caveat: I've only tested this from Win2K to FreeBSD, not the other way around. Best of luck, Andrew Gould
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200503221025.55911.algould>