Re: TightVNC 2.8.8 on Updated Win10

Hi

it turns out this probably had nothing to do with Windows Updates.

Today, I discovered that IP had not been configured properly ..
For some unknown reason (probably me meddling) I found that the
default gateway had two entries ?
First, the IP of the interface
Second, the correct IP of the gateway

Removing the first entry appears to have completely resolved the
problem (obviously) .. strange that only tightvnc was effected.
(At least the only effected app I noticed)

Thanks for all your feedback and sorry for the noise, regards
Frag



On 31/01/18 15:37, fragmentux wrote:
> Hi
> 
> I used tightvnc 2.8.8 (server) on Windows 10 (pre anniversary update)
> and it worked flawlessly.
> 
> I connect from a Linux desktop to a Windows 10 machine.
> 
> This Win10 machine has been left OFF the Internet to avoid being 
> updated.  Unfortunately, unforeseen circumstances have now forced
> the update and there is nothing I can do about it.
> 
> Since the Win10 is now fully up to date with Microsoft's disaster
> patches for Meltdown/Spectyre, tightVNC crashes after a seconds of use.
> 
> I doubt there is much I can do except wait for an update for tightvnc.
> 
> I am posting this message to ask if anybody else has seen similar
> problems with Windows 10 (upto date) and  tightvnc 2.8.8
> 
> Thanks for reading, regards
> Frag

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___________________________________________________________
TightVNC mailing list, [email protected]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list