Try without the .0 on the end.
sp00n, now I found the syslog.0 in /var/log/.
However, even after runing usercheck (perhaps because it does not return any errors for me) or a failed atempt it does not contain anyting NX related.
AlesZib and SpOOn, did you make any progress? I have exactly the same problems: I can login as NX user but when I try to access through the GUI I get authorization failed. Even the syslog.0 looks the same...Please let me know
Unofortunatelly no. Still hoping that some expert will post some solution here. I'm relatively new to linux and have no idea what else I could do.
reading these posts:
http://lists.kde.org/?l=freenx-knx&m...4212328392&w=2
and
http://ubuntuforums.org/archive/index.php/t-449382.html
I got the impression that the problem may be related to the sshd_config file on the server. They suggest to put a line relating to the .ssh/authorized_keys2 file.
However, I cannot play right now with the sshd_config file because I am far away from my server. I'll keep you informed...
I think I tried this and it did not work. The difference between at least my problem and their is that I can log in as a nx user (that is, as user names "nx") and aslo --usercheck reports that everything is ok, but I ctill can not connect.
Hi alenis / AlesZib,
No, not fixed it, I have given up. could not get freenx to work either, same problem.
I am experiencing the same issue as AlesZib, the ssh authentication is fine for user nx, I can ssh in as that user no problem. the issue seems to be the authentication of the user that nx does after the ssh session has been initiated.
Initially, I found out about freenx from ubuntuguide and followed the install from the freenx homepage. Everything is working for remoting into the machine remotely. The weird thing that I am experiencing is that I have a monitor, keyboard, mouse connected to that system. I have the machine to autologin my account. When the system boots, I have display through the bios and the Ubuntu splash screen, but after that, the screen goes blank. I can remote in (NoMachine) from another system, I just find it weird that machine went headless on me.
Anyone know why this happening? It is not a huge issue. I plan to use the system headless, but while I am still setting up my fileserver and shares, it would be nice to do it at the local console.
gotmonkey
chown -R us ./base
This thread has been very helpful to me. One additional point that I discovered after a long afternoon of frustration is as follows.
In attempting to secure ssh and NX access I modified my working server sshd_config and hosts files as follows:
This resulted in a an inability to connect and a variety of unhelpful error messages. I was able to get things working again after adding:Code:#In sshd_config Port 55555 Protocol 2 LoginGraceTime 2m MaxAuthTries 3 PermitRootLogin no StrictModes yes PermitEmptyPasswords no # /etc/hosts.allow sshd: 192.168.0.0/255.255.255.0 sshd: a trusted external ip address # /etc/hosts.deny sshd: ALL
I think I now have moved ssh to a different port, and restricted access to selected IP addresses.Code:# /etc/hosts.allow sshd: LOCAL
Maybe adding sshd: LOCAL will help someone else.
Bookmarks