I have little reason to ever use the Ctrl-alt-del drop down while in an
NT/2000 enviroment. The only time I use the drop down is when I'm in a
Win9x on the client side (since pressing ctrl-alt-del causes the system to
halt). On my W2k machine when I want to do a ctrl-alt-del to an NT server
or another workstation, I press Shift-Ctrl-Alt-Del. This accomplishes the
same thing and the local workstation doesn't see it as a Ctrl-Alt-Del, but
the machine running the VNC server does. That never really made sense to
me, but hey, whatever works. Other than that, I've never had a problem with
the drop down.
John
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 14, 2001 3:33 PM
To: [EMAIL PROTECTED]
Subject: Re: W2K problems....
I have been having problems in a W2K environment sending the "ctl-alt-del"
sequence from the drop-down menu. Nothing seems to happen. No firewall
issue, as far as I have been able to deduce. Has anyone else ran into a
similar problem with W2K (Workstation to server, or workstation to
workstation)
"Waltner, Steve"
<[EMAIL PROTECTED]> To:
"'[EMAIL PROTECTED]'"
Sent by:
<[EMAIL PROTECTED]>
[EMAIL PROTECTED] cc:
ch.att.com Subject: Screen
Artifacts on W2K vncviewer
03/14/2001 08:50 AM
Please respond to
vnc-list
I've been using VNC to access our Solaris servers with good
success.
We have also used it to connect to Windows servers with slightly less
success. The problems are slower screen updates and screen artifacts left
on
all clients (Solaris, Windows, MacOS). The artifacts are from the client
not
getting the full screen update. This hasn't been a real problem since we
only have a few Windows systems that we are serving with VNC.
Today, one of our users started experiencing the same problem
when
attached to our Solaris servers. The only real difference between this
person and all of our other users is that he is running on Windows 2000.
The
screen artifacts are usually left when a window is unhidden and moved in a
single step. Selecting the "request screen update" fixes the problem, but
this happens often enough to make that workaround annoying. Any idea on
what
to try. We see the same problem with both the AT&T 3.3.3r7 and TridiaVNC
1.4
releases of the viewer. We are running the AT&T 3.3.3r2 server on the
Solaris system.
--
Steve Waltner
LSI Logic
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
