tfseak "at" futurmaster.com
Mon Jan 26 15:04:00 2004
I don't know the reason :) but have you tried to uninstall VNC, remove all VNC related parameters from registry, reboot the machine and install VNC again? Don't forget to register VNC service.
OTOH, I don't understand your reasoning on SSH. If your two machines are connected to the network, and if the network isn't stable (eg, packet loss), I don't see how SSH can resolve it. SSH is just like TCP or UDP which are built on top of IP. If the underlying IP experience problem (in Data Link Layer or Physical Layer), there's no reason why SSH would be saved.
> -----Message d'origine-----
> De : T. Valent [mailto:winsock2 "at" musiker.de]
> Envoyi : lundi 26 janvier 2004 14:46
> @ : vnc-list "at" realvnc.com
> Cc : 'Steve Palocz'; jnw "at" realvnc.com; 'Prevett, Andrew (NOR)'
> Objet : RE: Connection closes
> In late December I've been reporting problems with instable connections to
> some VNC-Servers (2 of 10 in one of the networks I'm administrating) on the
> VNC-ML. The issue was that the connection is being closed immediately after
> a successful login. I have received some answers from people on the
> VNC-list, some just telling me that they have the same problem and yet no
> solution, some guessing that the reason is probably "network related",
> whatever that might mean.
> I installed a SSL-tunnel between the client and the server so that the
> client connects to 127.0.0.1 on a higher port, which establishes a
> SSL-tunnel to the server. The server then sees an incoming connection from
> 127.0.0.1, too. That way I can assure that no "network related issues" can
> cause the problem I'm reporting, because the complete VNC-protocol that
> formerly passed "the network" is now being tunneled into SSL and the various
> network layers assure that every packet is being transmitted properly, even
> if there were problems with the NIC (like inverting a bit or so (which some
> people honestly assumed to be a possible reason for my problem!)). The
> connections from and to 127.0.0.1 do not pass the NIC, so that the nic
> itself cannot be the cause for the problem.
> I'm not expecting anyone to say "Ah, now I know the reason: Do this and
> that!", I'm just reporting that there is a serious problem and that I got
> mails from people telling me they have the same problem.
> Nevertheless I'd be happy to get hints what I could try to solve this
> problem. :-)
> VNC-List mailing list
> VNC-List "at" realvnc.com
> To remove yourself from the list visit: