connect to OpenBSD BOX with VNC

[mfaridi]

I use OpenBSD 4.4 with Gnome , I have another computer use FreeBSD and Windows XP , can someone guide me how I can connect to OpenBSD machine with VNC from another system.???

Please guide me step by step

[Oko]

Originally Posted by mfaridi

I use OpenBSD 4.4 with Gnome , I have another computer use FreeBSD and Windows XP , can someone guide me how I can connect to OpenBSD machine with VNC from another system.???

Please guide me step by step

http://www.freebsddiary.org/tightvnc.php

Basic configuration of VNC server is the same on any Unix-like system.

Now the deeper problems are:

1. Proper PF rules which will enable you to get to your OpenBSD box?

2. DNS issues. Do you have static or Dynamic IP? Are you doing NAT or not?

Without knowing the topology of your network I can not help you with
1 and 2.

Cheers,
OKO

[jggimi]

Step-by-step for mfaridi:

1. Install tightvnc package.
2. 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.
3. 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.
4. Kill the server:
   $ pkill vnc
5. Edit ~/.vnc/xstartup. Have it start gnome-session, rather than running the default fvwm window manager.
6. Rerun the vncserver
7. Connect from your VNC client(s).

[mfaridi]

Originally Posted by jggimi

Step-by-step for mfaridi:

1. Install tightvnc package.
2. 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.
3. 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.
4. Kill the server:
   $ pkill vnc
5. Edit ~/.vnc/xstartup. Have it start gnome-session, rather than running the default fvwm window manager.
6. Rerun the vncserver
7. Connect from your VNC client(s).

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

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

I want connect to my OpenBSD BOX , and use Gnome or XFCE.

[jggimi]

It's a shell script, mfaridi. Look at your the script, and compare it to the default xinitrc: /usr/X11/xinit/xinitrc. Then, look at your ~/.xinitrc or ~/.xsession script, and compare.

[spoon-feed]

To have it start gnome, it should look something like:

#!/bin/sh
/usr/local/bin/gnome-session

To have it start xfce, it should look something like:

#!/bin/sh
/usr/local/bin/startxfce4

[/spoon-feed]

[mfaridi]

I put

#!/bin/sh
/usr/local/bin/startxfce4

and

#!/bin/sh
/usr/local/bin/gnome-session

but when I connect to OpenBSD box with VNCviewer I login into very old windows manager and I can not connect with Gnome or XFCE

[mfaridi]

oh my GOD I can connect with XFCE , first I run this command
and kill vncserver and then start it agian

pkill vnc

thanks

[mfaridi]

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

[Oko]

Originally Posted by mfaridi

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

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.

http://www.karlrunge.com/x11vnc/ssvnc.html

The only claim to fame of VNC is portability but even that is very questionable.
There are many more far more suitable protocols for desktop virtualization like
Ericom Blaze, OpenNX, Citrix, RDP...

What do you actually want to accomplish?

[tetrodozombie]

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.