> I recently upgraded the machines on my win 2k network to FreeVNC 3.3.6 and > ever since I did that I've noticed that I frequently lose a connection with > a machine when I try to intiate a VNC client session if the target computer > is running windows 2000. when i terminal serve into the same machine and > check the services listing it appears as if the service quit. If I restart > the VNC service, then vnc server is available once again - but using > temrianl services kinda defeats the purpose of using VNC. The NT4 servers > on my network have no such problems - the VNC session to those machines are > always rock solid. I didn't have this problem with the previous release of > FreeVNC. > > Suggestions? > > Craig Cline _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
