Open the appropriate ports on your network. By default, the port number for incoming connections from VNC clients to the server is 5900+display number. If you will be using VNC clients with -listen, open the appropriate ports as necessary.

Run the server from the connect-to userid on your OpenBSD platform for the first time:$vncserver
Provide a connection password for normal connection.
Optionally provide a display only password for restricted connection.

Kill the server:$pkill vnc

Edit ~/.vnc/xstartup. Have it start gnome-session, rather than running the default fvwm window manager.

Open the appropriate ports on your network. By default, the port number for incoming connections from VNC clients to the server is 5900+display number. If you will be using VNC clients with -listen, open the appropriate ports as necessary.

Run the server from the connect-to userid on your OpenBSD platform for the first time:$vncserver
Provide a connection password for normal connection.
Optionally provide a display only password for restricted connection.

Kill the server:$pkill vnc

Edit ~/.vnc/xstartup. Have it start gnome-session, rather than running the default fvwm window manager.

Rerun the vncserver

Connect from your VNC client(s).

I would be grateful if you give more information about this line

Code:

Edit ~/.vnc/xstartup. Have it start gnome-session, rather than running the default fvwm window manager

what I must do when I want vncserver run in startup ?
I vnc connection enough secure ?
what I must do for better secure connection ?

If it is a server it should run 24/7 If you want to run VNC server on your desktop
then you can put something like

Code:

exec vncserver

into your .xsession.

You could probable run it as a local daemon by editing rc.local.

TightVNC uses C, C++, and Java. You can imagine how secure is Java code.
On another hand you can enhance security by SSH tunneling and using SSL.
It kind of defeats purposes because you could as well run remote X clients on
your local X server with ssh -Y

For client side if you must use VNC I strongly recommend you to use SSVNC.

I find that I have no problems ever when I have an .xinitrc file that launches my window manager in my home directory. I can start X by "xinit" or "startx" and it will produce the same result, which is starting Fluxbox.

I don't know if you need to go through all that trouble. I didn't look it up, it's just a suggestion for you to try real quick when you get frustrated or you've exhausted other options.

Quick and painless is usually the way to go.

I might try putting VNC on this OpenBSD box and see what happens myself later today.