10-04-2012
I think its Solaris 5.6. I did uname -r to find this out.
I dont know if the vncserver is run in root or not. i can get into SU mode so i have the # but then if i type vncserver it says it can't find it. As soon as i exit SU and get back to normal /usr/me and run vncserver it will run.
When i use vnc viewer to access Solaris the username field is grey'd out so i think its just taking the IP address as the username.
thanks for your reply
---------- Post updated 04-10-12 at 12:24 PM ---------- Previous update was 03-10-12 at 03:54 PM ----------
Any other contributions ?
From the look of the log file has vncserver even started properly with them errors ?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Anyone know of a site where I can download a copy (non-evaluation copy and preferably free. ;) nods to Neo's post in UNIX Operating System thread) of VNC for RedHat 8? Thanks in advance. (7 Replies)
Discussion started by: google
7 Replies
2. Solaris
my desktop is a linux box, and I was wondering if there was a way to leverage X11/associated applications on a v440 remotely...
like "Sun Update Connection"...thanks,
manny (4 Replies)
Discussion started by: mr_manny
4 Replies
3. Solaris
hey. i have been installing the VNC server from the solaris Companion cd under solaris 8 SPARC,
when i try to open the vncserver i get: Xvnc is not in your PATH, how do i add it to the PATH ? and how do i install it if i need to do that,
thx (0 Replies)
Discussion started by: mads-nielsen
0 Replies
4. Solaris
Hi all....!!!
Can someone tell the essential packages need to install VNC from soalris 10 companion cd...?
I think there are three packages are essential. (SFWvnc, SFWgcmn, .....)
Please help me..
thank you..
Rgd...
Leshan (0 Replies)
Discussion started by: leshan
0 Replies
5. Red Hat
Hello all,
I have the folowing problem:
When I connected to a VNC server instance, the screen on the vncserver was frezzed. So, I executed the following commands in order to reestablish the VNC instance:
service vncserver stop
service vncserver start
No problem at this point, but now when... (5 Replies)
Discussion started by: mig28mx
5 Replies
6. Solaris
First you need to know that I'm 100% new to solaris/unix.
I'm trying to setup VNC on my sparc based server that I just installed solaris 10 on but when I type in vncserver to start it, I get "couldn't find "xauth" on your PATH"
What do I do so I can get a gui up and running remotely on my... (20 Replies)
Discussion started by: QuadRunner750
20 Replies
7. Solaris
Hello,
We have machines running Solaris 2.8
These are part of a process control system. A selection menu after the launch of Solaris can be selected whether the Solaris desktop or Leitsoftware to start.
VNC server is up and running when the Solaris user interface is started or when the... (1 Reply)
Discussion started by: eckart.t
1 Replies
8. Solaris
Hi,
I have installed vnc software in my desktop and trying start solaris gui and all i get is a partial gui that has one window open.
the window i am getting with vncviewer is (1 Reply)
Discussion started by: chidori
1 Replies
9. Solaris
Dear all,
I recently installed did VNC configuration on a Solaris Server. I am using VNC E4 2 7 as my Windows client.
The issue is that every time I log into my machine and use terminal ( a few commands like df -h or any other command and then close VNC ( windows).
When I log back in ,... (9 Replies)
Discussion started by: Junaid Subhani
9 Replies
10. Solaris
Hi guys,
First of all I would like to thank you for reading my post.
My question is about having autologin and VNC.
I already configure VNC that works perfectly using the following procedure:
1. svcadm enable svc:/application/x11/xvnc-inetd:default
2. vi /etc/services
vnc-server... (0 Replies)
Discussion started by: dennis3
0 Replies
LEARN ABOUT DEBIAN
vncpasswd
vncpasswd(1) TightVNC vncpasswd(1)
NAME
vncpasswd - set passwords for VNC server
SYNOPSIS
vncpasswd [file]
vncpasswd -t
vncpasswd -f
DESCRIPTION
The vncpasswd utility should be used to create and change passwords for the TightVNC server authentication. Xvnc uses such passwords when
started with the -rfbauth command-line option (or when started from the vncserver script).
vncpasswd allows to enter either one or two passwords. The first password is the primary one, the second password can be used for view-only
authentication. Xvnc will restrict mouse and keyboard input from clients who authenticated with the view-only password. The vncpasswd util-
ity asks interactively if it should set the second password.
The password file name defaults to $HOME/.vnc/passwd unless the -t command-line option was used (see the OPTIONS section below). The
$HOME/.vnc/ directory will be created if it does not exist.
Each password has to be longer than five characters (unless the -f command-line option was used, see its description below). Only the
first eight characters are significant. If the primary password is too short, the program will abort. If the view-only password is too
short, then only the primary password will be saved.
Unless a file name was provided in the command-line explicitly, this utility may perform certain sanity checks to prevent writing a pass-
word file into some hazardous place.
If at least one password was saved successfully, vncpasswd will exit with status code 0. Otherwise the returned status code will be set to
1.
OPTIONS
-t Write passwords into /tmp/$USER-vnc/passwd, creating the /tmp/$USER-vnc/ directory if it does not exist, and checking the permis-
sions on that directory (the mode must be 700). This option can help to improve security when your home partition may be shared via
network (e.g. when using NFS).
-f Filter mode. Read plain-text passwords from stdin, write encrypted versions to stdout. One or two passwords (full-control and view-
only) can be supplied in the input stream, newline terminates a password. Note that in the filter mode, short or even empty pass-
words will be silently accepted.
SEE ALSO
vncserver(1), Xvnc(1), vncviewer(1), vncconnect(1)
AUTHORS
Original VNC was developed in AT&T Laboratories Cambridge. TightVNC additions were implemented by Constantin Kaplinsky. Many other people
participated in development, testing and support.
Man page authors:
Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de>,
Tim Waugh <twaugh@redhat.com>,
Constantin Kaplinsky <const@tightvnc.com>
August 2006 vncpasswd(1)