On Monday 03 March 2003 10:40, Leendert Meyer wrote:
On Monday 03 March 2003 10:14, Richard Bos wrote:
Op maandag 3 maart 2003 09:48, schreef Leendert Meyer:
Op maandag 3 maart 2003 00:19, schreef Leendert Meyer:
Is this a bug in kde, or is it something else?? <<== It would be nice to get this confirmed.... [...] BTW, any luck with remote X login sessions like I suggested in my
On Monday 03 March 2003 09:22, Richard Bos wrote: previous mail?
Still the same story. I now checked with ethereal and I know for sure that XDMCP protocal is established and I would say even works. I e.g. see an Xwilling pkg that shows the load of the machine. I've seen this in an Xwilling script. After that an xdmcp manage message is sent (so no firewall problems too).
1. Try it without the firewall. If you use a local network, set IP_FORWARD="yes" in /etc/sysconfig/sysctl and run SuSEconfig.
2. Try it with xdm login instead of kdm login.
I just tried the xdm login, with the firewall off on both machines. This works well! What kind of login dialog appears (xdm/kdm) depends on what is running on the remote machine. [...]
X :1.0 -once -query 192.168.0.2 -- works -- I get a kdm login dialog works with xdm too
X :1.0 -indirect 192.168.0.2 -- does not work, should get a chooser, but X comes 5 times up -- have to kill X with <Ctrl>+<Alt>-<Backspace>
Update: after waiting a bit longer (~ 1 min), a kdm login dialog appears. Still no kdm chooser. With xdm logins on remote machine, I get a xdm chooser! :-) So it seems that the kdm chooser is broken???
X :1.0 -once -broadcast -- works -- I get a watch mouse cursor first, then the kdm login dialog
works with xdm too What still remains is figuring out how to let this work with the firewall ON. Cheers, Leen