Date: Wed, 18 Jul 2007 22:53:09 -0700 From: "Michael S. Eubanks" <mse_software@charter.net> To: freebsd-questions@freebsd.org Subject: Re: RE : Re: Remote Desktop tool for FreeBSD Message-ID: <1184824389.4195.20.camel@yak.mseubanks.net> In-Reply-To: <1b4e25200707180517j4024ff32lbcf9776bfae41eda@mail.gmail.com> References: <469DD07A.2090501@u.washington.edu> <698316.33697.qm@web27513.mail.ukl.yahoo.com> <20070718092517.GA40914@demeter.hydra> <1b4e25200707180517j4024ff32lbcf9776bfae41eda@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2007-07-18 at 09:17 -0300, Mario Augusto Mania wrote: > VNC > > 2007/7/18, Chad Perrin <perrin@apotheon.com>: > > On Wed, Jul 18, 2007 at 11:06:01AM +0200, simon butsana wrote: > > > Hi Garett, > > > > > > I apologize if you saw that as an offense. I never intended to hijack anyone's thread, and you will probably notice that I changed the subject (although I missed to remove the email body). > > > > > > > The key problem in this case seems to be that, rather than creating an > > email from scratch with the freebsd-questions address as the recipient, > > you hit "reply". Emails actually kinda keep track of whether they're in > > response to other emails, ane which emails those are. Many of us use > > mail clients that make use of that to enhance our ability to deal with > > email efficiently, and when you hit "reply" when you're starting a whole > > new discussion topic you end up with your email being slotted into a > > "thread" dedicated to a different topic. As such, you end up "hijacking > > a thread". Rule of thumb: Unless you're actually replying to something > > someone else said, don't use the "reply" button in your email client. > > > > As for your question: read up on "X forwarding" with the "ssh" tool. If > > you need further help beyond that, *please* start a new thread and ask > > there. I'll try to keep an eye out for such a thread so I can reply if I > > have some help to offer. > > > > -- > > CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ] > > Baltasar Gracian: "A wise man gets more from his enemies than a fool from > > his friends." I've been following this thread because I was trying to set up XDMCP. I ended up getting the TightVNC/Gnome Remote Desktop to work properly, but I would much rather have XDMCP. So far, I log in as root, open a terminal, and use the gdmsetup process to get the Gnome Login Window Preferences configuration dialog. I then click on the Remote tab and select "Same as Local" from the drop down menu. A button named "Configure XDMCP" should appear at the bottom of the window. When clicked, a bunch of miscellaneous options are shown, but note the UDP port 177. That should be open on the firewall along with ports 6000 through 6005 (or something like that). I simply used the defaults. Next, click on the Security tab at the top of the dialog window (after closing the "Configure XDMCP" dialog). I unchecked the "Deny TCP connections to Xserver" (though I think this is not necessary). Then, click on the bottom button named "Configure X Server". You need to have at least one Xserver available for remote connections. This is where I get stuck. Using Xming on Windows XP, I was able to connect to the Xserver and get the grey root screen, but that is it. Also, I am using GDM as a display manager. I have found no good HOWTO's yet, so help would be appreciated. The Help is fairly descriptive, but does not walk you through the process. Finally, the X manual pages describe how to setup XDM, but so far I have not tried that approach. Hopefully this is helpful to the original poster of this thread. -Michael S. Eubanks mse_software@charter.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1184824389.4195.20.camel>