, September 26, 2003 3:02 PM
To: [EMAIL PROTECTED]
Subject: Re: [expert] TightVNC ?
On Fri, 26 Sep 2003 13:59:05 -0500
H. Carter Harris [EMAIL PROTECTED] uttered:
I am running TightVNC under a new install of Mandrake 9.1 with 256MB
ram. I boot Mandrake at runlevel 3.
If I start vncserver
On Sat, 27 Sep 2003 11:13:46 -0500 H. Carter Harris
[EMAIL PROTECTED] wrote:
Sorry about that. Apparently I am not receiving everything from the
list... probably my fault. I went back and looked at the archive and
bingo.
or maybe messages are rejected from one of Mdk's servers
Exactly, I've got to hurry up and change mail servers.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Pierre Fortin
Sent: Saturday, September 27, 2003 11:30 AM
To: [EMAIL PROTECTED]
Subject: Re: [expert] TightVNC ?
On Sat, 27 Sep 2003 11:13:46 -0500 H
I am running TightVNC under a new install of Mandrake 9.1 with 256MB ram. I
boot Mandrake at runlevel 3.
If I start vncserver at the the command prompt, then IceWM is served up when
I access it from a client. If I startx and then open a command window and
run vncserver, I get KDE when I login
On Fri, 26 Sep 2003, H. Carter Harris wrote:
I am running TightVNC under a new install of Mandrake 9.1 with 256MB
ram. I boot Mandrake at runlevel 3.
[snip]
Even more troubling is trying to use it. Under Ice I get the start
button but Mandrake Control Center won't come up. Under KDE, I
On Fri, 26 Sep 2003 13:59:05 -0500
H. Carter Harris [EMAIL PROTECTED] uttered:
I am running TightVNC under a new install of Mandrake 9.1 with 256MB
ram. I boot Mandrake at runlevel 3.
If I start vncserver at the the command prompt, then IceWM is served
up when I access it from a client.
I am running TightVNC under a new install of Mandrake 9.1 with 256MB ram. I
boot Mandrake at runlevel 3.
If I start vncserver at the the command prompt, then IceWM is served up when
I access it from a client. If I startx and then open a command window and
run vncserver, I get KDE when I login
On Thu, 25 Sep 2003 12:20:45 -0500
H. Carter Harris [EMAIL PROTECTED] uttered:
I am running TightVNC under a new install of Mandrake 9.1 with 256MB
ram. I boot Mandrake at runlevel 3.
If I start vncserver at the the command prompt, then IceWM is served
up when I access it from a client.
You might also need to update your qt libs. Look in MandrakeUpdate and you
may see an update for qt that mentions vnc...
David
-Original Message-
From: Vincent Chen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 16, 2003 6:42 PM
To: [EMAIL PROTECTED]
Subject: [expert] tightvnc
Hi, all
I installed and started a tightvnc server on an IPC. I
can connect to this IPC from another workstation with
no problem. But only icewm is available. If I put the
following line in xstartup:
exec /usr/X11R6/bin/icewm
I got a windows manager after connection established.
exec
On Wed, 17 Sep 2003 08:42:28 +0800 (CST)
Vincent Chen [EMAIL PROTECTED] uttered:
exec /usr/X11R6/bin/startkde
I got nothing.
Why I can't get a KDE desktop?
try just exec kde
--
HaywireMac
Registered Linux user #282046
Homepage: www.orderinchaos.org
exec /usr/X11R6/bin/startkde
I got nothing.
Why I can't get a KDE desktop?
Just use startkde. Works fine for me:
#!/bin/sh
startkde
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
On Tue, 2003-09-16 at 17:42, Vincent Chen wrote:
Hi, all
I installed and started a tightvnc server on an IPC. I
can connect to this IPC from another workstation with
no problem. But only icewm is available. If I put the
following line in xstartup:
exec /usr/X11R6/bin/icewm
I got a
Having a problem with tightvnc and openssh.
my laptop: 192.168.0.100
sshd server: 192.168.0.203
vncserver: 192.168.0.203
[simon@localhost simon]$ ssh -L 5901:192.168.0.203:5900 [EMAIL PROTECTED]
Last login: Tue Dec 17 17:43:10 2002 from 192.168.0.100
[system@sales system]$
When I open
I think you're redirecting VNC from 5901 to localhost:5900, but then
asking the vncviewer to open on port 5901.
What if you do ONE of the following:
ssh -L 5901:192.168.0.203:5901 (instead of 5900)
-OR-
Vncviewer localhost:0
??
--TwinkieStix
On Tue, 2002-12-17 at 10:00, Simon Ree wrote:
TwinkieStix ([EMAIL PROTECTED]) wrote:
I think you're redirecting VNC from 5901 to localhost:5900, but then
asking the vncviewer to open on port 5901.
What if you do ONE of the following:
ssh -L 5901:192.168.0.203:5901 (instead of 5900)
-OR-
Vncviewer localhost:0
??
--TwinkieStix
Fixed with your suggestion and a reinstall of the server
thanks
--
Simon Rée
[EMAIL PROTECTED]
msg62910/pgp0.pgp
Description: PGP signature
Hi,
I've got a ~/.vnc/passwd file, but still every time I start vncserver,
it asks me to provide a password...
What could be the problem here?
Thanks
Hans
signature.asc
Description: This is a digitally signed message part
On Fri, 13 Dec 2002, SainTiss wrote:
Hi,
I've got a ~/.vnc/passwd file, but still every time I start vncserver,
it asks me to provide a password...
What are the exact commands you're using to start the server? You need
to specify the password file on the command line.
Want to buy your
Hans,
Yep if you use the one from MDK on 9.0 it does ask for the password
every time and set a password file every time. (just as if it where
the first time.) I sure haven't figured out why, the start file on MDK
is very different from the stock and I haven't had the time to pull it
apart
What is the permissions on the passwd file in the .vnc directory in ur home?
-Sridhar
SainTiss wrote:
Hi,
I've got a ~/.vnc/passwd file, but still every time I start vncserver,
it asks me to provide a password...
What could be the problem here?
Thanks
Hans
Want to buy your Pack or
On Fri, 2002-12-13 at 12:42, Sridhar wrote:
What is the permissions on the passwd file in the .vnc directory in ur home?
-Sridhar
Sridhar it creates the permissions right 664 and the user right on the
file... It just doesn't tell it to do 2 things
1. check to see if it's there.
2. read it
James,
I went thro' the startup script and found it was related to a permission
problem. The way I solved it was to make the 'passwd' file in my .vnc
folder to be -rwx--. It was not like this before. This is related to
the code in the startup script, must be a bug.
Cheers
Sridhar
James
Could be... I'll have to try it later. Thanks.
James
On Fri, 2002-12-13 at 13:21, Sridhar wrote:
James,
I went thro' the startup script and found it was related to a permission
problem. The way I solved it was to make the 'passwd' file in my .vnc
folder to be -rwx--. It was not like
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sridhar wrote on Fri, Dec 13, 2002 at 02:21:54PM -0700 :
James,
I went thro' the startup script and found it was related to a permission
problem. The way I solved it was to make the 'passwd' file in my .vnc
folder to be -rwx--. It was not
Todd Lyons wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It was like that in 8.1 and 8.2. The issue is that it needs to tell you
that the permissions are incorrect, not just go straight into a password
prompt.
Blue skies... Todd
Yes, that's right. The script needs to be modified to
26 matches
Mail list logo
