VNC on HP-UX11

[Jack_126]

Hi,
I am new to install Vncserver on HP-UX system.
I have installed the depot file downloaded from realvnc.com. Now I have directory /usr/local/bin
where Xvnc,vncserver files are there.

Now how to configure the vnc on server so that I can access it from client.I did not find any document that which files I have to modify and what parameters I have to set.

Regards
Jack

[Alex Lavrov. · Accepted solution]

I used it on HPUs and that's what I did:

You have directory:
/.vns (hidden in the root)

There you have file "xstartup" where you configure all the properties of vnc. Permissions, what environment to run etc ...


I run there "mwm" and also out "xhost +" so everyone can connect, because it's private network with no access to/from outside.

Alex.

[Jack_126]

Hi Alex,

I am able to connect to VNC server. but not able to connect to the following ports.
The following message is comming.

Warning: hp124:1 is taken because of /usr/spool/sockets/X11/1
Remove this file if there is no X server hp124:1

Warning: hp124:2 is taken because of /usr/spool/sockets/X11/2
Remove this file if there is no X server hp124:2

when I go to the following directory. These are owned by other user.
srwxrwxrwx 1 root sys 0 Jul 2 2003 0
srwxrwxrwx 1 oracle dba 0 May 16 2002 1
srwxrwxrwx 1 root sys 0 Aug 29 11:13 10
srwxrwxrwx 1 appldev oaa 0 May 12 2004 2
srwxrwxrwx 1 neerajb users 0 Sep 11 11:05 5
srwxrwxrwx 1 devendra users 0 Sep 11 11:33 6
-rw------- 1 appldev oaa 44 May 12 2004 appldev:2
-rw------- 1 oracle dba 44 May 17 2002 oracle:0
-rw------- 1 oracle dba 44 May 16 2002 oracle:1
-rw------- 1 root sys 44 Jul 2 2003 root:0
-rw------- 1 root sys 44 Aug 29 11:13 root:10

how can I use these ports.

Regards

[Alex Lavrov.]

I don't think I understood what ports are you talking about?

The messages you get are only warning, do they prevent you to connect to VNC?

Alex.

[Raj D.]

Hi Jack ,

You need to kill the port 1 ,

Try # vncserver -kill :1


To configure from client , to get the xwindow , you need to define a port in the server and the same port needs to define in the client , that will establish a ssh tunnel to get xterm.

I use putty to establish a ssh tunnel , and in tunnel give port:5910 , for port no 10.

You can run at the server , for that user which will be connecting for X window ,
$ vncserver
And it will ask password and will assign a port number. And create a password in
$HOME/.vnc/password [ in case of password forget need to delete this file to clear pw]

Let us know your senario.

Cheers,
Raj.

[Raj D.]

Try using port # 3 it is not used,

you can check with this for the ports used:
# ls -l /usr/spool/sockets/X11/

Cheers ,
Raj.

[Jack_126]

Hi,

I am facing the problem on my hp-ux system where I have configured the vnc server.This entry I have made in .profile of the user.

export DISPLAY=10.15.235.45:0.0 or 10.0
xhost +

The error i receive
xhost: unable to open display"10.15.235.45:0.0"

because of this I ma not able to run the xclock as well.

Any suggestion how I can resolve it.

Thanks
Jack

[Bob_Vance]

The whole point of using VNC is *not* to have to fool with X -- the VNC server asks as an X display on the host side and and a VNC server on the network side.

I have used VNC 4.1.1 many times on HPUX .
You don't have to modify any files after installation and you normally don't have to monkey with DISPLAY. All you need is to be sure that '/usr/bin/X11/mwm' exists -- it's normally there by default.

After installation, just log in as whatever user you want VNC to run as and execute 'vncserver'. If this is the first time that 'vncserver' has been run for the user, you'll be asked to assign a password -- it can be modified later via 'vncpasswd' .

You can launch vncserver multiple times and even as different users; i.e., you could have one vncserver launched as "root" and 2 launched as "user -- each user/vnc will have its own password. Each session will have its own display number ( the ":N" that is shown when you start vncserver).

From a PC or Unix client, connect via 'vncviewer' to 'server:N', where N is the session you want to connect to.
When you connect, there should be an 'xterm' there. DISPLAY is normally already set to
:N:0
again, where N is the session number.

To kill a server, issue
vncserver -kill :N
where N is the session you want to kill.


If you execute vncserver a bunch of times, those servers will stay running until you either kill them or reboot.


Make sure that any/all VNC sessions are gone:

# for x in `ls /usr/spool/sockets/X11`; do vncserver -kill :$x; done

Then, delete any remaining "N" files in "/usr/spool/sockets/X11" .

Now, start vncserver.

# ps -ef | grep -i vnc | grep -v grep.

You should see a server process:
Xvnc :1 ...

Connect to "host:1" from vncviewer on a PC client.
Immediately in the 'xterm' window, do

# echo $DISPLAY

it should show ":1.0"

If not, a profile may be setting or unsetting it -- just manually set it to that:
export DISPLAY=:1.0

Now, 'xhost +' .

Then, 'xclock &' should give you a clock !!

It's good to run the X programs in background (e.g., 'sam &') so that they don't tie up your term window -- unless you have other term windows available.

I typically launch another 'xterm' or two to have multiple term windows:
# xterm -sb -sl 500 &
# xterm -sb -sl 500 &


hth
bv

[Yogeeraj_1]

hi,

seems like you don't have an xclient (e.g. reflection x) running on the client pc.

please confirm

kind regards
yogeeraj

[Bob_Vance]

>export DISPLAY=10.15.235.45:0.0 or 10.0
>xhost +
> xhost: unable to open display"10.15.235.45:0.0"

Yes, the error he's getting is technically because he has no X server at 10.15.235.45 serving display0/screen0.

But, if he's doing this in the context of VNC, the X server is the localhost 'vncserver' serving display "1:0" (or N:0, depending on how many VNC sessions he has running).

Normally, you should not have to set DISPLAY in the xterm window after connecting to 'vncserver' using 'vncviewer' VNC, unless your profile is mucking around with DISPLAY.
Again, if this is true, you must manually reset it (or add new code to the profile;.):

export DISPLAY=":1.0"

To see the VNC processes, do
# ps -ef | grep -i vnc | grep -v grep
bobv 1369 1 0 07:53:38 pts/0 0:10 Xvnc :1 -desktop roger:1 () -httpd /usr/local/vnc/classes -a
bobv 1375 1 0 07:53:42 pts/0 0:00 vncconfig -iconic

Here, we have an Xvnc associated with ":1" (the first argument).
This Xvnc process associated with ":1" will be serving clients on Xwindow port 6001 and VNC clients on port 5901.

Note that this is a "real" X server and it can actually serve X clients from *anywhere*, e.g., another HPUX box, assuming that 'xhost' had been used to allow it (e.g., 'xhost +'. For example, I could have another telnet login on the same host, set 'export DISPLAY=127.0.0.1:1.0', then run 'xclock' and an xclock window will appear in the VNC session.
Or even from another Unix host entirely!
set 'export DISPLAY=vncserverhost:1.0', then run 'xclock'.


hth
bv

[Jack_126]

hi BV,

thanks for such a nice clarification. But you said that we don't have to edit or modify any file.After installing the VNC server. I modified two files /etc/services and /etc/inetd.conf. I am attaching the input of those files. It will be very nice if you could explain the concept behind it.
/etc/services
# Add VNC services
vnc800x600x8 5950/tcp vnc800x600x24 5951/tcp
vnc1024x768x8 5952/tcp
vnc1024x768x24 5953/tcp

/etc/inetd.conf
#
# VNC Servers
#
vnc800x600x8 stream tcp nowait vnc /usr/local/bin/Xvnc Xvnc -dpi 75 -i
netd -query localhost -once -geometry 800x600 -depth 8
vnc800x600x24 stream tcp nowait vnc /usr/local/bin/Xvnc Xvnc -dpi 75 -i
netd -query localhost -once -geometry 800x600 -depth 24
vnc1024x768x8 stream tcp nowait vnc /usr/local/bin/Xvnc Xvnc -dpi 75 -i
netd -query localhost -once -geometry 1024x768 -depth 8
vnc1024x768x24 stream tcp nowait vnc /usr/local/bin/Xvnc Xvnc -dpi 75 -i
netd -query localhost -once -geometry 1024x768 -depth 24

Regards
Jack

[Bob_Vance]

Well, I was saying that it is not *necessary* to modify any files to get it to work.
Beyond that, there are many things that you can do.

In my discussion, you'll notice that I manually executed 'vncserver' to get Xvnc launched. That's how I typically do it -- it's basically for me and when I'm done I just do a 'vncserver -kill :N' . I'm not a GUI kind of guy, so I only use VNC for when I want to run some program, like 'sam', in GUI mode rather than character mode, or some program that *only* supports X, like the Oracle installer.

VNC is great from connecting remotely because it is much more bandwidth efficient than a direct Xwindow connection. Try running Data Protector from home over X -- on second thought, don't even try it ;>) Using VNC, it's almost like you're right there on the X console at the server.


What you have here is cool, in that you've set up some service entries that will be handled dynamically by 'inetd'.

When a vncviewer connects to port 5952 (instead of 5901, which is the target of the "normal" 'vncviewer host:1'), 'inetd' is listening (the "vnc1024x768x8 5952/tcp" entry in /etc/services) and will launch 'Xvnc' as defined by the "vnc1024x768x8 ..." entry in /etc/inetd.conf.

However, the client will have to know to connect to :52, rather than :1
i.e.,
vncviewer host:52

The entries that you have defined, with "-query" assume that XDMCP is being supported - basically that you have CDE dtlogin running from init state 3. This is normal for HPUX and allows you to connect to CDE window/desktop manager on the server.

I haven't really played with it.
I really don't use CDE and prefer to run Xwindow programs ad hoc rather than having a GUI desktop -- I'm a command-line kinda guy.


hth
bv

[Jack_126]

Thnks BV and all other experts. I got answer for my most of the querys.

Regards
Jack