[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [K12OSN] Introducing ourselves


I did what you suggest (interesting indeed) to get remote login screen on K12 server from Fedora 8 chubby client. Since I use Gnome, I asked the F8 start-up screen to show me the menu for remote logins (what you do with KDE), and it did. After a while, the machine came up with a list of remote login servers, including itself (pseudo-remote, actually local) and the K12 server. So I asked for the latter, and, at first, it seemed it worked, it switched to a different graphic mode, it showed briefly a cursor with a "wait" icon, but then it suddenly dropped me to the local login screen, with no error message, and I have no idea of where to look for a log file. I repeated the same operation many times, to no result. I then tried rdesktop-xdmcp combination, and, after showing a wrist-watch icon for a while, it sent me out with a "xnest:malloc() ... " allocation error.
  By the way, I operated with both server and client firewalls off.
Back in the times of Fedora 8, there was that handy program that allowed graphical configuration of local and remote logins, and worked great. Now, since F10-K12 don't have anything similar, I copied /etc/gdm/custom.conf from Fedora 8 to Fedora 10, but this isn't enough for get it running. "gdmgreeter" file is no longer available, so I tried "gdm-simple-greeter" and other greeters, with no success.

  Thanks for your help
Gianugo Altieri
Terrell Prudé Jr. ha scritto:
Gianugo Altieri wrote:
Second problem is a fat client I wish to link. It runs Fedora 8 with some legacy software. I'm trying to let it "open a window" on the server for a graphical login, and also vice versa, i.e. let the server (and therefore the thin clients) open a graphical login on it. The problem is that I don't know how to do it. If I connect the fat client to LTSP LAN, it grabs an IP, but that's all. It doesn't even "ping" the server, let alone opening a remote desktop on it. Any suggestion?

It should certainly be able to ping the server, *if* this fat client is also on the LTSP client network. If not, i. e. it's on the main company LAN and you're using the classic two-NIC LTSP setup, then you have two choices:

1.)  poke a hole in the K12 server's firewall rules for SSH and X11, or
2.)  place the Fedora 8 fat client on the LTSP client network.

I would recommend the second choice, for two reasons. First, you don't need to poke any holes in the built-in packet filter for X11 (proper security is always good). Second, it's just lower maintenance.

Now, once you can ping the K12 server, here's how I would handle graphical logins. I will use KDE as an example, since that's what I happen to run. From your K Menu, choose "Switch user", and choose "Start New Session". You'll get a new graphical login screen, and one of the options at the lower left are two options--"Session Type" and "Menu". Choose "Menu". Of the choices, one of them is "Remote login". That's the one you want. Just point that at your K12 server's IP address, and boom, you have a K12 login prompt. Meanwhile, your "original" Fedora 8 session is still running. To switch between them, you use F7 (to go back) and F8 (to go forward).

I'm not sure how easy it would be to have the clients be able to do the same to the Fedora 8 box, because I've never done that. But fundamentally, it should be possible. It might take some fiddling with some of the configuration files under /opt/ltsp/i386...or if your client has X11 with XDMCP built in, you should be able to configure the client directly. What you want at that point is what's called an "indirect" X11 query. Do some Googling for that--"indirect query", XDMCP, and X11.


K12OSN mailing list
K12OSN redhat com
For more info see <http://www.k12os.org>

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]