Surviving a Win NT reboot
Tim Hawkins
Tim.Hawkins "at" LOOT.com
Wed, 01 Mar 2000 08:38:12 +0000
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01BF8358.860404D0
Content-Type: text/plain;
charset="iso-8859-1"
Jacob, on all our NT servers VNC definatly starts before logon, otherwise I
would have to spend a lot of time running to and fro. Are you absolutly sure
the VNCServer is starting as a service, and is not just placed into the
startup group on the NT box. We had a number of systems installed by one of
my admins in this way, and they exhibit simular behavior.
Also check to see if the networking has any dependancies that are causing it
not to start untill logon, the only time I have seen that happen is on some
NIC's in Laptops where the pcmcia system does not seem to load untill you
hit CAD.
-----Original Message-----
From: Jacob_Cherian "at" Dell.com [mailto:Jacob_Cherian "at" Dell.com]
Sent: 28 February 2000 18:05
To: vnc-list "at" uk.research.att.com
Subject: RE: Surviving a Win NT reboot
This is not on 9x machine. I want the VNC service to start before logon and
be able to get to the desktop. The logon then will be the regular Win NT
logon.
Jacob Cherian
Enterprise Storage Developement I
Dell Computer Corporation
Ph: (512) 723 3247
Email: Jacob_Cherian "at" dell.com
-----Original Message-----
From: John Meek [mailto:JMeek "at" uswebcks.com]
Sent: Saturday, February 26, 2000 3:35 PM
To: 'vnc-list "at" uk.research.att.com'
Subject: RE: Surviving a Win NT reboot
That is not surprising if you see this behavior on an 9x machine. the local
redir is not loaded until the login process starts. In Nt the network is
independant of the user context, in 9x they are the same. Because of that
the machines will not be listening on the VNS ports because the machine does
not even have VNC loaded yet (not even networking VxDs) until user logon.
This can be verified by using TweakUI or a null windows login password to
have the machine get to the desktop automagically and the VNC will work. If
the machine is displaying the login prompt or a username/password challange
the VNC "Service" has not been started.
-----Original Message-----
From: Jacob_Cherian "at" Dell.com [ mailto:Jacob_Cherian "at" Dell.com
<mailto:Jacob_Cherian "at" Dell.com> ]
Sent: Friday, February 18, 2000 8:48 AM
To: vnc-list "at" uk.research.att.com
Subject: Surviving a Win NT reboot
I have the same problem listed below. Does someone have a fix/workaound for
this.
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.
Jacob Cherian
Enterprise Storage Developement I
Dell Computer Corporation
Ph: (512) 723 3247
Email: Jacob_Cherian "at" dell.com
---------------------------------------------------------------------
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
<http://www.uk.research.att.com/vnc/intouch.html>
---------------------------------------------------------------------
**********************************************************************
Confidential Communication.
The information contained in this e-mail and any files transmitted with it
are confidential and may be subject to legal professional privilege. It is
intended solely for the addressee(s). If you received this e-mail by
mistake, please promptly inform the sender by reply e-mail or collect
telephone or facsimile, and immediately delete the e-mail from your system
and destroy any printed copy. You must not disclose, copy, print, forward
or disseminate or use in any way the information contained in this e-mail
and/or any files transmitted with it.
**********************************************************************
------_=_NextPart_001_01BF8358.860404D0
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: Surviving a Win NT reboot</TITLE>
<META content="MSHTML 5.00.2920.0" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=737212708-01032000>Jacob,
on all our NT servers VNC definatly starts before logon, otherwise I would have
to spend a lot of time running to and fro. Are you absolutly sure the VNCServer
is starting as a service, and is not just placed into the startup group on the
NT box. We had a number of systems installed by one of my admins in this way,
and they exhibit simular behavior. </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=737212708-01032000></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=737212708-01032000>Also
check to see if the networking has any dependancies that are causing it not to
start untill logon, the only time I have seen that happen is on some NIC's in
Laptops where the pcmcia system does not seem to load untill you hit CAD.
</SPAN></FONT></DIV>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
<DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Jacob_Cherian "at" Dell.com
[mailto:Jacob_Cherian "at" Dell.com]<BR><B>Sent:</B> 28 February 2000
18:05<BR><B>To:</B> vnc-list "at" uk.research.att.com<BR><B>Subject:</B> RE:
Surviving a Win NT reboot<BR><BR></DIV></FONT>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=504010618-28022000>This
is not on 9x machine. I want the VNC service to start before logon and be able
to get to the desktop. The logon then will be the regular Win NT
logon.</SPAN></FONT></DIV>
<DIV> </DIV>
<P><I><FONT color=#000080 face=Arial size=1>Jacob Cherian</FONT></I>
<BR><I><FONT color=#000080 face=Arial size=1>Enterprise Storage Developement
I</FONT></I> <BR><I><FONT color=#000080 face=Arial size=1>Dell Computer
Corporation</FONT></I> <BR><I><FONT color=#000080 face=Arial size=1>Ph: (512)
723 3247</FONT></I> <BR><I><FONT color=#000080 face=Arial size=1>Email:
Jacob_Cherian "at" dell.com</FONT></I> </P>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
<DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> John Meek
[mailto:JMeek "at" uswebcks.com]<BR><B>Sent:</B> Saturday, February 26, 2000 3:35
PM<BR><B>To:</B> 'vnc-list "at" uk.research.att.com'<BR><B>Subject:</B> RE:
Surviving a Win NT reboot<BR><BR></DIV></FONT>
<P><FONT size=2>That is not surprising if you see this behavior on an 9x
machine. the local redir is not loaded until the login process
starts. In Nt the network is independant of the user context, in 9x
they are the same. Because of that the machines will not be listening
on the VNS ports because the machine does not even have VNC loaded yet (not
even networking VxDs) until user logon. This can be verified by using
TweakUI or a null windows login password to have the machine get to the
desktop automagically and the VNC will work. If the machine is
displaying the login prompt or a username/password challange the VNC
"Service" has not been started.</FONT></P><BR><BR>
<P><FONT size=2>-----Original Message-----</FONT> <BR><FONT size=2>From:
Jacob_Cherian "at" Dell.com [<A
href="mailto:Jacob_Cherian "at" Dell.com">mailto:Jacob_Cherian "at" Dell.com</A>]</FONT>
<BR><FONT size=2>Sent: Friday, February 18, 2000 8:48 AM</FONT> <BR><FONT
size=2>To: vnc-list "at" uk.research.att.com</FONT> <BR><FONT size=2>Subject:
Surviving a Win NT reboot</FONT> </P><BR>
<P><FONT size=2>I have the same problem listed below. Does someone have a
fix/workaound for</FONT> <BR><FONT size=2>this.</FONT> </P><BR>
<P><FONT size=2>Problem 1: This is the worst of the bunch. Even though VNC
is installed as </FONT><BR><FONT size=2>a service (verifiably so), a
connection cannot be made to a machine the </FONT><BR><FONT size=2>first
time after it has been rebooted. If someone logs on to the NT domain
</FONT><BR><FONT size=2>and the machine is never rebooted, VNC automatically
starts as it should </FONT><BR><FONT size=2>and can be reached from there on
out. The problem is that VNC is not </FONT><BR><FONT size=2>starting until
AFTER the machine has been logged on to the network the </FONT><BR><FONT
size=2>first time. As long as the machine is not rebooted and "close all
programs </FONT><BR><FONT size=2>and log on as a different user" is
selected... VNC can be used to log onto </FONT><BR><FONT size=2>the machine.
This problem is reproducible on many machines here with new </FONT><BR><FONT
size=2>VNC 3.3.3r2 installs and also those that have been upgraded from
earlier </FONT><BR><FONT size=2>versions that worked correctly. The error
message that displays if you try </FONT><BR><FONT size=2>to connect to a
machine that has been rebooted and not yet been logged on </FONT><BR><FONT
size=2>is "Failed to connect to server" (the same one you get when VNC is
simply </FONT><BR><FONT size=2>not running). The machine is pingable by host
name. Again... these are </FONT><BR><FONT size=2>Windows 95 machines that
exhibit the problem.</FONT> </P><BR>
<P><FONT size=2>Jacob Cherian</FONT> <BR><FONT size=2>Enterprise Storage
Developement I</FONT> <BR><FONT size=2>Dell Computer Corporation</FONT>
<BR><FONT size=2>Ph: (512) 723 3247</FONT> <BR><FONT size=2>Email:
Jacob_Cherian "at" dell.com</FONT> </P><BR><BR>
<P><FONT
size=2>---------------------------------------------------------------------</FONT>
<BR><FONT size=2>To unsubscribe, send a message with the line: unsubscribe
vnc-list</FONT> <BR><FONT size=2>to majordomo "at" uk.research.att.com</FONT>
<BR><FONT size=2>See also: <A
href="http://www.uk.research.att.com/vnc/intouch.html"
target=_blank>http://www.uk.research.att.com/vnc/intouch.html</A></FONT>
<BR><FONT
size=2>---------------------------------------------------------------------</FONT>
</P></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01BF8358.860404D0--
---------------------------------------------------------------------
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
---------------------------------------------------------------------