[FreeNX-kNX] problem with freenx server

[ankush grover]

>
>
> You have to allow the special user "nx" to log in via SSH with pubkey
> authentication. "nx" will establish a secure channel for the real user's
> password authentication and start the NX components that make the session
> work on behalf of the user.
>
> See what it tells you below  :-)
>
> Cheers,
> Kurt
>
> hey Mr.Kurt,

Thanks for the reply but as I was trying to login through a real user why it
is saying nx user is not allowed. That means freenx will run only when nx
user is allowed to ssh .

Can it be possible to run freenx with some other user as nx will be known to
the world and I would like to run freenx with some other user .

I check that nx was locked (passwd -S nx)

I unlocked the user and put the entries for nx in sshd_config and I have
even make sshd listen on 0.0.0.0 as the freenx needs to connect to the
localhost after authentication

After doing everything I am still not able to get the freenx working


NX> 203 NXSSH running with pid: 4500
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
NX> 200 Connected to address: 192.168.1.10 on port: 3009
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
HELLO NXSERVER - Version 1.4.0-44 OS (GPL)
NX> 105 hello NXCLIENT - Version 1.5.0
NX> 134 Accepted protocol: 1.5.0
NX> 105 SET SHELL_MODE SHELL
NX> 105 SET AUTH_MODE PASSWORD
NX> 105 login
NX> 101 User: john
NX> 102 Password:
NX> 103 Welcome to: server.sun.net user: john
NX> 105 listsession --user="john" --status="suspended,running"
--geometry="1024x768x32+render" --type="unix-kde"
NX> 127 Sessions list of user 'john' for reconnect:

Display Type             Session ID                       Options  Depth
Screen         Status      Session Name
------- ---------------- -------------------------------- -------- -----
-------------- ----------- ------------------------------


NX> 148 Server capacity: not reached for user: john
NX> 105 startsession --session="server" --type="unix-kde" --cache="8M"
--images="32M" --cookie="******" --link="lan" --kbtype="pc102/en_US"
--nodelay="1" --encryption="1" --backingstore="when_requested"
--geometry="fullscreen" --media="0" --agent_server="" --agent_user=""
agent_password="******""  --screeninfo="1024x740x32+render"

NX> 1000 NXNODE - Version 1.4.0-44 OS (GPL)
NX> 700 Session id: server.sun.net -1002-55B054AA85070A1F4DB8F10CC558C635
NX> 705 Session display: 1002
NX> 703 Session type: unix-kde
NX> 701 Proxy cookie: 2cc82de2e03104d89eb537f81317f47e
NX> 702 Proxy IP: 127.0.0.1
NX> 706 Agent cookie: 2cc82de2e03104d89eb537f81317f47e
NX> 704 Session cache: unix-kde
NX> 707 SSL tunneling: 1
NX> 1004 Error: Session did not start.
NX> 504 Session startup failed.
NX> 999 Bye
Killed by signal 15.

What is the problem why it is not able to start the session?

Thanks & Regards

Ankush Grover
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20060411/3deabbcc/attachment.html>