How to use networked Arch box like remote desktop

colbert · 2008-04-04 01:13:07

I just added users to nx on my client machine and server, logged out and back in on both. On the client, I run nxclient and still get the above dialog box

How can I completely remove freenx/nxclient from my client machine and start over? pacman -R and a reinstall still gives that above.

serrghi · 2008-04-04 07:48:55

Heres what i did for absic password authentication (not ssh_key file):
pacman -S freenx
edit /opt/NX/node.conf to enable logging.
sudo cp /opt/NX/bin/nx* /usr/bin/
sudo nxsetup --install --setup-nomachine-key --clean
sudo nxserver --status (it should output running)

then simply login to through the client.

HOWEVER i still have the problem that when i login trough freenx i get a black screen in my window. Seems like programs arent beeing forwarded correctly. And the log doesnt give me any errors (log lvl 7 in node.conf)
Ive tried about all the options in the client i can think about.
Anyone bumped into same problem? (running openbox as WM btw)

Last edited by serrghi (2008-04-06 10:20:35)

colbert · 2008-04-06 06:21:51

Thanks serrghi, I followed your steps but get this as soon as I type sudo nxserver status:

NX> 100 NXSERVER - Version 2.1.0-71 OS (GPL)
NX> 500 Error: Function status not implemented yet.
NX> 999 Bye

serrghi · 2008-04-06 10:20:15

you have to run the command as superuser, ie: sudo nxserver --status

typing error in my first post.

colbert · 2008-04-06 16:36:21

Yes I did

Still can't get it to go

Last edited by colbert (2008-04-06 23:20:42)

colbert · 2008-04-08 20:19:15

Okay, managed to get nxclient working right fresh again, and nxserver is showing that it's running on the server box. Here's the output though when trying to connect:

NX> 203 NXSSH running with pid: 7832
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
NX> 285 Setting the preferred NX options
NX> 200 Connected to address: 192.168.1.100 on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
HELLO NXSERVER - Version 2.1.0-71 OS (GPL)
NX> 105 hello NXCLIENT - Version 2.1.0
NX> 134 Accepted protocol: 2.1.0
NX> 105 SET SHELL_MODE SHELL
NX> 105 SET AUTH_MODE PASSWORD
NX> 105 login
NX> 101 User: bobby2
NX> 102 Password: 
NX> 103 Welcome to: mythbox user: bobby2
NX> 105 listsession --user="bobby2" --status="suspended,running" --geometry="3520x1200x24+render" --type="unix-default"
NX> 127 Sessions list of user 'bobby2' for reconnect:

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


NX> 148 Server capacity: not reached for user: bobby2
NX> 105 startsession  --taint="0" --virtualdesktop="0" --link="lan" --backingstore="1" --encryption="1" --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0" --composite="1" --media="0" --session="bobby2" --type="unix-default" --client="linux" --keyboard="pc105/us" --screeninfo="3520x1200x24+render" 

NX> 1000 NXNODE - Version 2.1.0-71 OS (GPL)
NX> 105 /opt/NX/bin/nxserver: line 1283: 17318 Terminated              sleep $AGENT_STARTUP_TIMEOUT
NX> 596 Session startup failed.
NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set SESSION_LOG_CLEAN=0 in node.conf and investigate "/home/bobby2/.nx/F-C-mythbox-1000-FF68316D4F6E1E03B72C05C793FCC32A/session". You might also want to try: ssh -X myserver; /opt/NX/bin/nxnode --agent to test the basic functionality. Session log follows:
NX> 700 Session id: mythbox-1000-FF68316D4F6E1E03B72C05C793FCC32A
NX> 705 Session display: 1000
NX> 703 Session type: unix-default
NX> 701 Proxy cookie: 2841a10fa624b822fb0925ec69b9d03e
NX> 702 Proxy IP: 127.0.0.1
NX> 706 Agent cookie: 2841a10fa624b822fb0925ec69b9d03e
NX> 704 Session cache: unix-default
NX> 707 SSL tunneling: 1
Can't open /opt/NX/var/db/running/sessionId{FF68316D4F6E1E03B72C05C793FCC32A}: No such file or directory.
mv: cannot stat `/opt/NX/var/db/running/sessionId{FF68316D4F6E1E03B72C05C793FCC32A}': No such file or directory
NX> 1006 Session status: closed
NX> 1001 Bye.
NX> 280 Exiting on signal: 15

Last edited by colbert (2008-04-08 20:19:49)

colbert · 2008-04-11 04:54:13

Bump, anyone? Still trying to get this to work

serrghi · 2008-04-11 05:17:54

Im getting a similar error as you Colbert.
Heres mine:

NX> 203 NXSSH running with pid: 408
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
NX> 285 Setting the preferred NX options
NX> 200 Connected to address: 85.200.101.242 on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
HELLO NXSERVER - Version 2.1.0-71 OS (GPL)
NX> 105 hello NXCLIENT - Version 2.1.0
NX> 134 Accepted protocol: 2.1.0
NX> 105 SET SHELL_MODE SHELL
NX> 105 SET AUTH_MODE PASSWORD
NX> 105 login
NX> 101 User: serrghi
NX> 102 Password: 
NX> 103 Welcome to: serrghi user: serrghi
NX> 105 listsession --user="serrghi" --status="suspended,running" --geometry="1280x1024x32+render" --type="unix-application"
NX> 127 Sessions list of user 'serrghi' for reconnect:

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


NX> 148 Server capacity: not reached for user: serrghi
NX> 105 startsession  --virtualdesktop="1" --application="openbox-session" --link="adsl" --backingstore="1" --encryption="1" --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0" --composite="1" --media="0" --session="serrghi.homeunix.net" --type="unix-application" --geometry="1280x971" --client="winnt" --keyboard="pc102/no" --screeninfo="1280x971x32+render" 

NX> 1000 NXNODE - Version 2.1.0-71 OS (GPL)
NX> 700 Session id: serrghi-1000-6FE34FB2F891FC147B950230F755C45D
NX> 705 Session display: 1000
NX> 703 Session type: unix-application
NX> 701 Proxy cookie: ddbebab82dfb7d585ca3694b81450f00
NX> 702 Proxy IP: 127.0.0.1
NX> 706 Agent cookie: ddbebab82dfb7d585ca3694b81450f00
NX> 704 Session cache: unix-application
NX> 707 SSL tunneling: 1
NX> 105 NX> 596 Session startup failed.
NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set SESSION_LOG_CLEAN=0 in node.conf and investigate "/home/serrghi/.nx/F-C-serrghi-1000-6FE34FB2F891FC147B950230F755C45D/session". You might also want to try: ssh -X myserver; /opt/NX/bin/nxnode --agent to test the basic functionality. Session log follows:
NX> 1006 Session status: closed
/opt/NX/bin/nxserver: line 1283: 11138 Terminated              sleep $AGENT_STARTUP_TIMEOUT
Can't open /opt/NX/var/db/running/sessionId{6FE34FB2F891FC147B950230F755C45D}: No such file or directory.
mv: cannot stat `/opt/NX/var/db/running/sessionId{6FE34FB2F891FC147B950230F755C45D}': No such file or directory
NX> 1001 Bye.
NX> 280 Exiting on signal: 15

Dont really know what to do either..

metalfan · 2008-04-24 13:03:38

Same here, looks like the authentication (according to auth.log) works, but somehow freenx is fucked

colbert · 2008-04-24 15:37:16

I am trying to get help via the very helpful mailing list, I have been directed to the "80% are ssh" section here: http://openfacts.berlios.de/index-en.ph … FAQ/Server

Going to give it a shot later tonight.

tafsen · 2008-05-25 22:33:38

Have you guys solved this problem? I get the same error.

B-Con · 2008-05-26 01:45:34

Sjoden wrote:

finferflu wrote:
Why isn't VNC secure? I'm worried because it's the one I use. To be precise I use:
x11vnc -usepw
on the server side, and vncviewer as a client.
I believe it's because vnc isn't encrypted. Although, I think you can run it over ssh and be fine. I have no experience with the others though. I use vnc at work, and it's fine, not always the fastest, but works.
@all, If your that worried about your traffic being sniffed on a home network... I think you have other things to worry about first. Of course, I'd never run it over the interwebs.

VNC is insecure in two ways: the password strength, and the data stream. Obviously, since it doesn't encrypt VNC traffic, it is insecure in that way. But also note that VNC stores your password as an encrypted 8-byte string. Thus your password can never be more than an effective 8 characters (it will truncate 123456879 to 12345678), which makes brute-forcing quite easy. So leaving VNC setup and accessible to the outside world is asking for someone to brute-force their way in. Also, since your password (such as it is) is encrypted with a constant key, anyone with access to your computer will be able to decrypt and restore your original password with ease; so don't use a password you'd use anywhere else.

The solution to both these problems is to setup VNC with no (or a mock) password, disable all but localhost connections, and then only connect via tunneling through SSH.

Last edited by B-Con (2008-05-26 01:46:41)

finferflu · 2008-05-26 09:29:53

B-Con wrote:

The solution to both these problems is to setup VNC with no (or a mock) password, disable all but localhost connections, and then only connect via tunneling through SSH.

I have always wondered how to do that, but never found a tutorial. Any hint?

Thanks

Allan · 2008-05-26 09:43:12

finferflu wrote:

B-Con wrote:
The solution to both these problems is to setup VNC with no (or a mock) password, disable all but localhost connections, and then only connect via tunneling through SSH.
I have always wondered how to do that, but never found a tutorial. Any hint?
Thanks

well, in a very shortened version:

ssh -L 5901:127.0.0.1:5901 user@remote_computer
start vncserver on remote_computer (should be port 5901 that opens or this won't work)
point vncviewer at HOST=127.0.0.1 PORT=5901

Arch Linux

#26 2008-04-04 01:13:07

Re: How to use networked Arch box like remote desktop

#27 2008-04-04 07:48:55

Re: How to use networked Arch box like remote desktop

#28 2008-04-06 06:21:51

Re: How to use networked Arch box like remote desktop

#29 2008-04-06 10:20:15

Re: How to use networked Arch box like remote desktop

#30 2008-04-06 16:36:21

Re: How to use networked Arch box like remote desktop

#31 2008-04-08 20:19:15

Re: How to use networked Arch box like remote desktop

#32 2008-04-11 04:54:13

Re: How to use networked Arch box like remote desktop

#33 2008-04-11 05:17:54

Re: How to use networked Arch box like remote desktop

#34 2008-04-24 13:03:38

Re: How to use networked Arch box like remote desktop

#35 2008-04-24 15:37:16

Re: How to use networked Arch box like remote desktop

#36 2008-05-25 22:33:38

Re: How to use networked Arch box like remote desktop

#37 2008-05-26 01:45:34

Re: How to use networked Arch box like remote desktop

#38 2008-05-26 09:29:53

Re: How to use networked Arch box like remote desktop

#39 2008-05-26 09:43:12

Re: How to use networked Arch box like remote desktop

Board footer