I can not explain it, but I can add to the mystery - which may give someone who understands this better an idea.
Normally I have no problem connecting to my Win2K server. However if the server has been inactive long enough to powered down the HD it fails. VNC seems to connect & gives the message that it is loading the screen. I hear the HD spinning up, but VNC apparently times out because it never comes up. When I try again, I find the VNC service on the server has stopped, and if I try to re-start VNC, it hangs the Win2K server to the point of needing a hard reset. Any way to extend the wait time? Or is there another problem I am missing? On 1 Jul 2002 at 9:22, Alex Morris wrote: > That doesn't affect W2K Server. It's XP which comes with a > censor^H^H^H^H^H^H firewall built-in. > > For what it's worth, I regularly use TightVNC on Windows 2000 > Professional and Windows 2000 Advanced Server with no problems at all. > I used Fastpush (http://www.darkage.co.uk/index.htm) to install it on > each box I control. Much easier than logging on to each one in turn, > and it makes sure each one is standard. :-) > > If Windows 2000 Server is dropping VNC connections then I'm afraid I > can't explain why. Sorry. > > In message <[EMAIL PROTECTED]>, "Beerse, Corni" > <[EMAIL PROTECTED]> writes >It's Micro$oft software. (sorry, it's > monday morning and it rains >outside...) > >Current M$Windows comes > with build in firewall which is closed by default. >It's most likely > the firewall that restricts you -- Alex Morris > _______________________________________________ VNC-List mailing list > [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list Bruce W. Malcolm Phone 805 452 1622 Fax 805 683 5331 _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
