3.3.3r2 for Wintel problems
ngkuisp@interpath.com
ngkuisp "at" interpath.com
Wed, 16 Feb 2000 17:46:11 +0000
Yes, it is... thats the problem... it is installed as a service
(verifiably so in regedit), but it will not start until the machine has
been logged onto the network at least once. With it installed as a
service, it survives "Close all programs and log on as a different user"
but its the initial logon that is causing the problems.
"James \(Wez\) Weatherall" <jnw22 "at" cam.ac.uk>
Sent by: owner-vnc-list "at" uk.research.att.com
02/16/2000 11:55 AM
Please respond to vnc-list
To: <vnc-list "at" uk.research.att.com>
cc:
Subject: Re: 3.3.3r2 for Wintel problems
Verify that there is a key for WinVNC under
HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/CurrentVersion/RunServices
This will be how WinVNC is started, when operating as a service under
Win95.
Cheers,
James "Wez" Weatherall
--
"Xenophobes should go back to Xenophobia"
Laboratory for Communications Engineering, Cambridge - Tel : 766513
AT&T Labs Cambridge, UK - Tel : 343000
----- Original Message -----
From: <ngkuisp "at" interpath.com>
To: <vnc-list "at" uk.research.att.com>
Sent: Wednesday, February 16, 2000 2:44 PM
Subject: Re: 3.3.3r2 for Wintel problems
> Yes, I can work around the problem also.. but due to security reasons...
> it is not an option for me to disable signon.
> Is there a way to have VNC function as it should and start up as a
service
> instead of running as an application even though it is installed as a
> service.
>
>
>
>
> "Edwin O. Erdman" <erdmaned "at" ticon.net>
> Sent by: owner-vnc-list "at" uk.research.att.com
> 02/14/2000 07:09 PM
> Please respond to vnc-list
>
>
> To: vnc-list "at" uk.research.att.com
> cc:
> Subject: Re: 3.3.3r2 for Wintel problems
>
> FWIW I am using the vnc viewer in SuSE Linux 6.3 to access a Wintel
> print server running Win95 original release. What I had to do to get it
> to work was change my preferred login in Control Panel|Network to be
> Windows logon instead of Windows Networking logon. Other set-up; Ijust
> stuffed a shortcut into my startup subdirectory. This allows me to (via
> Samba) use two printers that are not directly supported by Linux.
>
> Ed Erdman
>
> ngkuisp "at" interpath.com wrote:
> >
> > Hello guys,
> > I'm a fairly long time VNC user and have been having problems with
> 3.3.3r2
> > that I never had with earlier versions.
> > I have searched the mailing list archives and have found similiar
> problems
> > for NT but not for win95. The FAQ also did not help my problems.
> >
> > Problem 1: This is the worst of the bunch. Even though VNC is
installed
> as
> > a service (verifiably so), a connection cannot be made to a machine
the
> > first time after it has been rebooted. If someone logs on to the NT
> domain
> > and the machine is never rebooted, VNC automatically starts as it
should
> > and can be reached from there on out. The problem is that VNC is not
> > starting until AFTER the machine has been logged on to the network the
> > first time. As long as the machine is not rebooted and "close all
> programs
> > and log on as a different user" is selected... VNC can be used to log
> onto
> > the machine. This problem is reproducible on many machines here with
new
> > VNC 3.3.3r2 installs and also those that have been upgraded from
earlier
> > versions that worked correctly. The error message that displays if you
> try
> > to connect to a machine that has been rebooted and not yet been logged
> on
> > is "Failed to connect to server" (the same one you get when VNC is
> simply
> > not running). The machine is pingable by host name. Again... these are
> > Windows 95 machines that exhibit the problem.
> >
> > Problem 2: This one also did not show up with earlier versions. I did
> see
> > some direct hits for this problem in the archives but never saw a
> > resolution. Once this newest version is initially installed, the
> machines
> > are rebooted and then on the next startup VNC is added as a service. I
> > have done this with both the link AND manually with the -install
option.
> I
> > then provide a password. On subsequent starts the Windows 95 machine
> pops
> > up a dialog box saying that no password has yet been provided even
> though
> > it has. I provide on the initial start after installing as a service.
I
> > can also close VNC as a service and start one in app mode and again
> > provide the password. Same thing happens on the next reboot. I also
run
> > the service helper and default registry settings... same thing. I can
> use
> > regedit and verify that the registry does in fact have my settings...
it
> > just simply takes 5-12 reboots before this new version "sees" that it
> does
> > in fact have a password set. This problem is also reproducible on
EVERY
> > install that I do on a 95 machine with 3.3.3r2.
> >
> > Thanks for any responses to this long winded request for help.
> > Robert Kluttz
> > NGK Ceramics USA, Inc
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, send a message with the line: unsubscribe vnc-list
> > to majordomo "at" uk.research.att.com
> > See also: http://www.uk.research.att.com/vnc/intouch.html
> > ---------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, send a message with the line: unsubscribe vnc-list
> to majordomo "at" uk.research.att.com
> See also: http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, send a message with the line: unsubscribe vnc-list
> to majordomo "at" uk.research.att.com
> See also: http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------
>
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to majordomo "at" uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to majordomo "at" uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------