Does anyone use VNC or Remote Desktop on PC-BSD? - PC-BSD Forums

californiajeff · #1 07-19-2005, 10:59 PM

I am trying to implement a VNC solution in PC-BSD but I am having some difficulty. I am curious if anyone out there is already using something?

My goal is to use VNC so I can access my PC-BSD full screen over the internet and also so I don't have to buy a KVM switch! :wink:

scottro · #2 07-20-2005, 12:12 AM

Install ports. As root

Code:

cd 
cvsup ports-supfile
cd /usr/ports/net/tightvnc
make install clean

When it's done, go back to being regular user and then you can run

Code:

vncserver

It'll ask you for a password, create one. If this box is available on the Internet, pick a strong one.

Then you'll see that it's running a session, probably on screen 1. To access the box--say its is 192.168.8.12 you have the vnc client running on the MS (or whatever box) and for server name or IP address type in
[code]
192.168.8.12:1

It should then ask you for a password and you should be in a basic twm desktop. If you want a different desktop, then look for the .vncrc file in your home directory (Note the dot before its name)

You should see a line something like twm &, which you can change to startkde & (or whatever window manager you want.)

If any of this doesn't work, let me know, I'm doing it from memory but can check tomorrow.

californiajeff · #3 07-21-2005, 05:35 PM

Originally Posted by scottro

Then you'll see that it's running a session, probably on screen 1. To access the box--say its is 192.168.8.12 you have the vnc client running on the MS (or whatever box) and for server name or IP address type in

Code:

192.168.8.12:1

I see what might have ben causing me a problem. I see it looks like youare making a connection on port 1. Maybe that has been my problem all along. I am using UltraVNC on XP and it connects to port 5900 by default. I wonder if that has been the problem all along?

I will try your suggestions either tonight or tomorrow and let you know how it goes.

californiajeff · #4 07-25-2005, 05:40 PM

I still can't get it to work. I am trying to connect to the TightVNC server from UltraVNC running on an XP box. I think I am gonna try installing TightVNC on the XP box to see if I can get any different results.

pepecito · #5 01-27-2006, 05:23 PM

Hi,
I successfully got to control my WindowsXP PC from my PCBSD computer.
Here what I'm using:
Server: Ultravnc under windows.
Client: tightvnc under PCBSD.

Now I'm trying to do the reverse... i.e. control my PCBSD computer from my WindowsXP PC, but I can only get a new Xsession where I can do nothing!
I tryed to change the Xstart file found in the .vnc folder, changing "#twm &" with "startkde &", but it doesn't work.
Here is the log:

Code:

27/01/06 18:58:50 Xvnc version 3.3.tight1.2.9
27/01/06 18:58:50 Copyright (C) 1999 AT&T Laboratories Cambridge.
27/01/06 18:58:50 Copyright (C) 2000-2002 Constantin Kaplinsky.
27/01/06 18:58:50 All Rights Reserved.
27/01/06 18:58:50 See http://www.uk.research.att.com/vnc for information on VNC
27/01/06 18:58:50 See http://www.tightvnc.com for TightVNC-specific information
27/01/06 18:58:50 Desktop name 'X' (:1)
27/01/06 18:58:50 Protocol version supported 3.3
27/01/06 18:58:50 Listening for VNC connections on TCP port 5901
27/01/06 18:58:50 Listening for HTTP connections on TCP port 5801
27/01/06 18:58:50   URL http://:5801
AUDIT: Fri Jan 27 18:58:51 2006: 1723 Xvnc: client 1 rejected from local host
Xlib: connection to ":1.0" refused by server
Xlib: Client is not authorized to connect to Server
xrdb: Can't open display ':1'
AUDIT: Fri Jan 27 18:58:51 2006: 1723 Xvnc: client 1 rejected from local host
Xlib: connection to ":1.0" refused by server
Xlib: Client is not authorized to connect to Server
xsetroot:  unable to open display ':1'
AUDIT: Fri Jan 27 18:58:51 2006: 1723 Xvnc: client 1 rejected from local host
Xlib: connection to ":1.0" refused by server
Xlib: Client is not authorized to connect to Server
Warning: This program is an suid-root program or is being run by the root user.
The full text of the error or warning message cannot be safely formatted
in this environment. You may get a more descriptive message by running the
program as a non-root user or by removing the suid bit on the executable.
xterm Xt error: Can't open display: %s
AUDIT: Fri Jan 27 18:58:51 2006: 1723 Xvnc: client 1 rejected from local host
AUDIT: Fri Jan 27 18:58:51 2006: 1723 Xvnc: client 1 rejected from local host
Xlib: connection to ":1.0" refused by server
Xlib: Client is not authorized to connect to Server
Can't open display (null)
AUDIT: Fri Jan 27 18:58:52 2006: 1723 Xvnc: client 1 rejected from local host
Xlib: connection to ":1.0" refused by server
Xlib: Client is not authorized to connect to Server
xset:  unable to open display ":1"
AUDIT: Fri Jan 27 18:58:52 2006: 1723 Xvnc: client 1 rejected from local host
Xlib: connection to ":1.0" refused by server
Xlib: Client is not authorized to connect to Server
xsetroot:  unable to open display ':1'
startkde: Starting up...
AUDIT: Fri Jan 27 18:58:52 2006: 1723 Xvnc: client 1 rejected from local host
Xlib: connection to ":1.0" refused by server
Xlib: Client is not authorized to connect to Server
ksplash: cannot connect to X server :1
AUDIT: Fri Jan 27 18:58:54 2006: 1723 Xvnc: client 1 rejected from local host
Xlib: connection to ":1.0" refused by server
Xlib: Client is not authorized to connect to Server
kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
AUDIT: Fri Jan 27 18:58:54 2006: 1723 Xvnc: client 1 rejected from local host
Xlib: connection to ":1.0" refused by server
Xlib: Client is not authorized to connect to Server
kded: cannot connect to X server :1
kded: ERROR: KUniqueApplication: Registering failed!
kded: ERROR: Communication problem with kded, it probably crashed.
AUDIT: Fri Jan 27 18:58:54 2006: 1723 Xvnc: client 1 rejected from local host
Xlib: connection to ":1.0" refused by server
Xlib: Client is not authorized to connect to Server
kcminit: cannot connect to X server :1
AUDIT: Fri Jan 27 18:58:54 2006: 1723 Xvnc: client 1 rejected from local host
Xlib: connection to ":1.0" refused by server
Xlib: Client is not authorized to connect to Server
AUDIT: Fri Jan 27 18:58:54 2006: 1723 Xvnc: client 1 rejected from local host
Xlib: connection to ":1.0" refused by server
Xlib: Client is not authorized to connect to Server
ksmserver: cannot connect to X server :1
startkde: Shutting down...
klauncher: Exiting on signal 1
startkde: Running shutdown scripts...
startkde: Done.

What I would like to do is get the current display, not a brand new one!
Any idea??? :?

gnutux · #6 01-28-2006, 02:13 AM

what's the port to connect from a Windows PC to my tightvnc server? Port 5900? As someone said?

gnutux

pepecito · #7 01-28-2006, 06:49 AM

I can connect using ports 1 and 5901.

jdarnold · #8 01-28-2006, 01:17 PM

I can highly recommend the x11vnc port. It works great for controlling my PCBSD box from my Windows box. The web page is here:

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

And the port is in /usr/ports/net/x11vnc. You just run x11vnc, and then use TightVNC to connect and it is really snappy.

Another option is to just pop an X window up on your PC. It's a little more complicated, because you have to get an X server running on your PC, but I've found that the Cygwin server works great for it too. Then you can just SSH to your box, using the special X server flags for it (-Y is the best one) and you pop X windows right up on your Windows display.

pepecito · #9 01-29-2006, 09:18 AM

This sounds good,... I will try it ASAP...
Anyway, a PBI for those kind of stufs will be necessary for PCBSD. Don't think so? :wink:

antik · #10 02-01-2006, 02:28 PM

Originally Posted by pepecito

This sounds good,... I will try it ASAP...
Anyway, a PBI for those kind of stufs will be necessary for PCBSD. Don't think so? :wink:

Nomachine's NX server/client is much better than dog slow vnc.