01-22-2004
vncserver on SCo 505
I have installed vnc on my SCO 505 box. its running fin, but when I start a session and connect to it from my win machine I do get an Xsession but I only get an xterm and thats it. I know my settings are in my //.vnc/xstartup file but what exactly am I supposed to see there.
will some one send an example of thair settings.
Thanks to all that help and who attempt to help others.
10 More Discussions You Might Find Interesting
1. IP Networking
Right now, i have an SCO 505 with IP, GATEWAY e MASK configured.
I have one router that is my gateway.
The SCO is able to connect to all of the local computers, including the router.
However, i´m not unable to ping anything that is not local with SCO.
I believe I tried setting the... (1 Reply)
Discussion started by: Danielnr
1 Replies
2. UNIX for Dummies Questions & Answers
I need to run a back up that will take more than one tape. What is the command that will continue the back up on to a second tape drive. the first is /dev/rStp0 second is /dev/rStp1. Anyone? (1 Reply)
Discussion started by: franruiz
1 Replies
3. Red Hat
hello,
I have two fedora 8 systems connected in LAN.
I have typed "vncserver" on one terminal; gave a password.
Then went to the next terminal and typed "vncviewer".It asked me for host server.I gave the IP address of the above system.But it prompted that "server not found".
I tried "ping"... (4 Replies)
Discussion started by: nsharath
4 Replies
4. AIX
Guys
I have an AIX 5.3 box.I am getting following messages if i try to switch to any non root user.
bash-3.00# su - sys
3004-505 Cannot set process environment.
bash-3.00# su - daemon
3004-505 Cannot set process environment.
bash-3.00# su - adm
3004-505 Cannot set process environment.... (4 Replies)
Discussion started by: ak835
4 Replies
5. Red Hat
Hi,
I am trying to install vncserver on a fedora system.
I am wondering how can i get the vncserver rpm to install.
I am not having it in the yum repository. (by the way is vncserver free ?)
How could i download the rpm and install it ?
Please advice me on this.
Thanks in advance! (12 Replies)
Discussion started by: lramsb4u
12 Replies
6. Ubuntu
Hi,
I am having trouble connecting to the vncserver on my Ubuntu server 10.04.2.
# vncserver :1
A VNC server is already running as :1
# ps -ef | grep vnc
root 2944 1683 0 13:47 pts/0 00:00:00 grep --color=auto vnc
I think I have got all the necessary binaries (below) but when I... (0 Replies)
Discussion started by: Duffs22
0 Replies
7. Red Hat
Hi All,
Just wondering if someone can help me out here:
Wanted to install vnc server on Centos 6, yum installed tigervnc but there after I do not see any services associated with it.
Also, I had installed SAMBA and proceeded with SWAT installation but I am unable to access... (2 Replies)
Discussion started by: a2z1982
2 Replies
8. Linux
Hi all,
I received following messages while trying to run vncserver,
what could be reason behind this.
vncserver
Warning: system1.pen.com:1 is taken because of /tmp/.X11-unix/X1
Remove this file if there is no X server system1.pen.com:1
Warning: system1.pen.com:2 is taken because of... (2 Replies)
Discussion started by: manalisharmabe
2 Replies
9. UNIX Desktop Questions & Answers
Hi,
While trying to connect vncserver, i am gettting below errors:
sh: /home/$USER/.vnc/$HOSTNAME:2.log: Permission denied
sh: /home/$USER/.vnc/$HOSTNAME:2.pid: Permission denied
New '$HOSTNAME:2 ($USER)' desktop is $HOSTNAME:2
Starting applications specified in... (1 Reply)
Discussion started by: pandeesh
1 Replies
10. AIX
Hi there
I've bought a used System p 9115-505. When I attach the LAN cable to my router the HMC receives an IP address from my router, but the HMC is unreachable. There are no open ports.
Does anybody know that problem?
Any help greatly appreciated. Greetings from Italy! (2 Replies)
Discussion started by: mediaset23
2 Replies
LEARN ABOUT DEBIAN
tightvncpasswd
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)