socket error (or something else?) after authentication

[Adam Pavelec]

On Wednesday, June 11, 2003 10:46 PM [GMT-5=EST], william wei
<wwei@harvard.edu> wrote:

> Thank you. Knowing someone out there have had same problem at least
> tells me that it's probably not an obvious configuration or user
> error. Let's hope someone else has a solution...

Well, a temporary solution is to set the "Virtual Network Computing"
service to restart itself upon failure.  It'll take at least a minute
for it to do so, but it might be a little easier than restarting the
service manually (which you can do through remote computer management,
as long as you have admin privileges).

Just out of curiosity, does your server automatically lock itself with
the screensaver (ie. do you use a password-protected screensaver); or do
you manually lock the computer when you're finished using it?

I have mine set to use a password-protected Logon Screen Saver after 5
minutes.  Sometimes I also manually lock the computer when I am finished
using it either via CTRL-ALT-DEL>Lock Computer or by a shortcut I
created [ %windir%\System32\rundll32.exe user32.dll,LockWorkStation ].

Just looking for any commonality.

--Adam