On Sunday 07 November 2004 22:36, Richard Bos wrote:
Op zaterdag 6 november 2004 23:50, schreef Anders Johansson:
That last one isn't needed on the xdm machine. In fact, you don't even have to have an X server installed
Did you run SuSEconfig after changing those? Did it take effect? Make sure there isn't an "kdmrc.SuSEconfig" in /etc/opt/kde3/share/config/kdm/
I ran SuSEconfig indeed, and there is no kdmrc.SuSEconfig in the directory mentioned above. <snip> I use kdm indeed and Enable is indeed set to true...
With those settings I expect xdcmp to work, but no.... Oh the command I use on the from box is: X -query 192.168... :1
vt08 shows the grey X background and I can move the mouse, but that's about it. After some time the X times out.... Anything I can try?
Make sure there isn't a firewall running on the 9.2 machine blocking port 177 (udp, I *think*), and that there isn't a firewall on the local machine blocking port 6001
Also, if the 9.0 machine has multiple IP addresses, make sure X is using one that xdm can contact
I have an ethereal trace, it shows the xdmcp willing, request, accept and twice an manage message... May it have to do with X-4... versus X-6...?
It shouldn't have, I haven't tested it but if connections between XFree and x.org break it's a bug. Nothing changed in the protocol Make sure firewalls on both machines are accepting connections. Remember there are two connections being made in xdmcp: one from the local machine to port 177/udp on the remote, and one from the remote to port 6000+<server number>/tcp on the local (so in your example, with server number :1, it would be tcp port 6001 on your local machine)