FreeNX and NXclient problem
I have a FC4 system, setup with FreeNX Server.
The NX system works perfectly fine when I am on my intranet. I can do my stuff easily like that.
However, when I leave my intranet, (ie work) I can't connect to it.
I though oH, it must have been the SSH port not being forward, so I double checked it with SSH, it works.
I can do everything via bash from work. so the port must not be blocked.
The following is how my NX Client failed.
replaced my ip with xxx.xxx.xxx.xxx
NX> 203 NXSSH running with pid: 3324
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: xxx.xxx.xxx.xxx on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
HELLO NXSERVER - Version 1.5.0-50-SVN OS (GPL)
NX> 105 which: no xauth in (/usr/local/bin:/bin:/usr/
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: chungs
NX> 102 Password:
NX> 103 Welcome to: server.home.net user: chungs
which: no xauth in (/usr/local/bin:/bin:/usr/
NX> 105 listsession --user="chungs" --status="suspended,runnin
NX> 127 Sessions list of user 'chungs' for reconnect:
Display Type Session ID Options Depth Screen Status Session Name
------- ---------------- --------------------------
NX> 148 Server capacity: not reached for user: chungs
NX> 105 startsession --link="modem" --backingstore="1" --nodelay="1" --encryption="1" --cache="8M" --images="32M" --media="0" --session="home" --type="unix-gnome" --geometry="1280x1024" --kbtype="pc102/en_US" --screeninfo="1280x1024x32
which: no xauth in (/usr/kerberos/bin:/usr/lo
NX> 1000 NXNODE - Version 1.5.0-50-SVN OS (GPL)
NX> 700 Session id: server.home.net-1000-D4687
NX> 705 Session display: 1000
NX> 703 Session type: unix-gnome
NX> 701 Proxy cookie: 55bdef46c9b8124fb043f3fea9
NX> 702 Proxy IP: 127.0.0.1
NX> 706 Agent cookie: 55bdef46c9b8124fb043f3fea9
NX> 704 Session cache: unix-gnome
NX> 707 SSL tunneling: 1
NX> 105 /usr/bin/nxserver: line 1077: 1963 Terminated sleep $AGENT_STARTUP_TIMEOUT
NX> 596 Session startup failed.
Killed by signal 15.
The NX system works perfectly fine when I am on my intranet. I can do my stuff easily like that.
However, when I leave my intranet, (ie work) I can't connect to it.
I though oH, it must have been the SSH port not being forward, so I double checked it with SSH, it works.
I can do everything via bash from work. so the port must not be blocked.
The following is how my NX Client failed.
replaced my ip with xxx.xxx.xxx.xxx
NX> 203 NXSSH running with pid: 3324
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: xxx.xxx.xxx.xxx on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
HELLO NXSERVER - Version 1.5.0-50-SVN OS (GPL)
NX> 105 which: no xauth in (/usr/local/bin:/bin:/usr/
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: chungs
NX> 102 Password:
NX> 103 Welcome to: server.home.net user: chungs
which: no xauth in (/usr/local/bin:/bin:/usr/
NX> 105 listsession --user="chungs" --status="suspended,runnin
NX> 127 Sessions list of user 'chungs' for reconnect:
Display Type Session ID Options Depth Screen Status Session Name
------- ---------------- --------------------------
NX> 148 Server capacity: not reached for user: chungs
NX> 105 startsession --link="modem" --backingstore="1" --nodelay="1" --encryption="1" --cache="8M" --images="32M" --media="0" --session="home" --type="unix-gnome" --geometry="1280x1024" --kbtype="pc102/en_US" --screeninfo="1280x1024x32
which: no xauth in (/usr/kerberos/bin:/usr/lo
NX> 1000 NXNODE - Version 1.5.0-50-SVN OS (GPL)
NX> 700 Session id: server.home.net-1000-D4687
NX> 705 Session display: 1000
NX> 703 Session type: unix-gnome
NX> 701 Proxy cookie: 55bdef46c9b8124fb043f3fea9
NX> 702 Proxy IP: 127.0.0.1
NX> 706 Agent cookie: 55bdef46c9b8124fb043f3fea9
NX> 704 Session cache: unix-gnome
NX> 707 SSL tunneling: 1
NX> 105 /usr/bin/nxserver: line 1077: 1963 Terminated sleep $AGENT_STARTUP_TIMEOUT
NX> 596 Session startup failed.
Killed by signal 15.
ASKER
Yum said.
Nothing to do
I guess either I already have it, or just don't have the repo set
btw, i did a
yum install *xorg-x11-xauth*
Nothing to do
I guess either I already have it, or just don't have the repo set
btw, i did a
yum install *xorg-x11-xauth*
can you check:
# which xauth
# which xauth
ASKER
/usr/X11R6/bin/xauth
Weird because you seems to have xauth installed but then NX complains that you don't have xauth... are you on the server.home.net machine just to make sure?
ASKER
No..
What I am trying to do is a remote dial in.
So, basically, NX works perfectly fine when I am on my local Intranet.... I have a some what of a decent network setup at home.
I am trying to access the NX server from outside of my intranet. and that was the error that poped up.
I tried SSH, and ssh worked fine.
What I am trying to do is a remote dial in.
So, basically, NX works perfectly fine when I am on my local Intranet.... I have a some what of a decent network setup at home.
I am trying to access the NX server from outside of my intranet. and that was the error that poped up.
I tried SSH, and ssh worked fine.
xauth should be installed in server.home.net machine.
ASKER
yep it is.
what I am puzzled about is.
why is there a reference to 127.0.0.1 too..
is it possible that my problems occur due to a routing issue?
I did forward port 22 to server.home.net
what I am puzzled about is.
why is there a reference to 127.0.0.1 too..
is it possible that my problems occur due to a routing issue?
I did forward port 22 to server.home.net
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
i was also testing NoMachine's systems.. i was having amazing link to them. so that means my current system is capable of going there.
so, the question should be limited to, if FreeNX need configuration to work properly if it is behind a router, with a private IP address inside.
so, the question should be limited to, if FreeNX need configuration to work properly if it is behind a router, with a private IP address inside.
ASKER
Are there any other things one can do??
would Freenx requires another port beside 22?
would Freenx requires another port beside 22?
ASKER
T_T no one know what else I can do??
I still can't answer why nxserver works within the private network, but it won't work if I am outside....
T_T
I still can't answer why nxserver works within the private network, but it won't work if I am outside....
T_T
ASKER
T_T
ASKER
Hey, I've decided to close this thread.
I believe my solution was FreeNX is not completely setup to work with routed users.
I'll most likely install NXServer OSv to see if there is a difference
Thanks
I believe my solution was FreeNX is not completely setup to work with routed users.
I'll most likely install NXServer OSv to see if there is a difference
Thanks
Is xauth giving you the problem? You might want to try putting in xauth:
# yum install xorg-x11-xauth
should do the trick to install.. not sure if that is the problem though