Sponsored Content
Full Discussion: Open vnc:0
Operating Systems Linux Open vnc:0 Post 302762229 by tokiwinter on Monday 28th of January 2013 09:12:36 AM
Old 01-28-2013
Hi,

Depending on the RedHat (or clone) version, you'll need to install the vnc-server or tigervnc-server package, or similar, run vncpasswd, then start the server with vncserver :<display>.

Please provide the output of

Code:
cat /etc/redhat-release
rpm -qa | grep vnc

and some more details on what you're trying to do.

Cheers,
Toki
 

7 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

VNC via Rs232

Hi ! Is there somebody who is able to connect a VNC session via serial cable ? There is a hint on the VNC homepage that it is possible to configure that. But how? thanks joerg (2 Replies)
Discussion started by: joerg
2 Replies

2. UNIX for Dummies Questions & Answers

Vnc

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

3. Solaris

VNC Installation

Hi, I would like to install VNC on my Solaris 6/10 x86 machine. Can someone walk me thru it step by step? I'm very new to Solaris and I would like to get this running ASAP for school so I can VNC into it and use it remotely. I have serached online but the information is so abundant. I don't know... (1 Reply)
Discussion started by: kungpow
1 Replies

4. Red Hat

cannot set user id: Resource temporarily unavailable (not open file/open process related)

First post, sorry to be a bother but this one has been dogging me. I have a process user (java application server) that trips a resource limit every couple weeks and need help finding what limit we're hitting. First, this is what's running: This is the error when jobs are run or the... (0 Replies)
Discussion started by: Katahdin
0 Replies

5. UNIX Desktop Questions & Answers

Question on VNC

Hi, I set-up my VNC Server on a Fedora 13 and I have a client on windows. I can access the Fedora PC but when I move the mouse and click on folders, I do not see the Fedora Desktop updating (I don't see the things that I am doing in my client on the Fedora PC) Then, when I do something on... (0 Replies)
Discussion started by: h0ujun
0 Replies

6. UNIX for Beginners Questions & Answers

Vim help.txt automatically open every time I open vi

Hi Friends, Every I try to open a vi window vim help.txt automatically opens evertime. After doing ZZ or :q! also the same page opens automatically. How to stop this? Is it machine specific ? Other users who are opening the same servers and files are not facing this issue. Thanks... (1 Reply)
Discussion started by: sudiptabhaskar
1 Replies

7. Shell Programming and Scripting

Vim help.txt automatically open every time I open vi

Hi Friends, Every I try to open a vi window, vim help.txt automatically opens evertime. After doing ZZ or :q! also the same page opens automatically. How to stop this? Is it machine specific ? Other users who are opening the same servers and files are not facing this issue. Thanks... (3 Replies)
Discussion started by: sudiptabhaskar
3 Replies
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)
All times are GMT -4. The time now is 01:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy