different TCP stack on win95 boxes?

[James (Wez) Weatherall]

> I've been unable to get the VNC server to send graphics to VNC viewers
> that request it. I can connect to the PCs, and send the correct
> password. But then the client sits there waiting for the initial screen
> draw. This is the same on the Mac and Win95 viewer. On my linux box, I was
> able to get 1/5th of the screen to show up before it froze. Usually the
> VNC server on the other end stops responding and I need to reboot the
> win95 box.
>
> Do the win95 boxes need to be running the default MS TCP/IP stack to get
> the VNC server to work 100%? Or is there something I've overlooked? All
> PCs are running at the same res/depth [1024x768 - 32bit].

Which version of the WinVNC server are you running?  Either your vendor's
TCP stack is completely broken or it doesn't like disabling Nagle's
algorithm (in which case it's still broken, but less so).

The only other possibility is that WinVNC makes an erroneous socket call
that happens not to break Microsoft's TCP stack.  I'm not convinced that
that's likely, though, partly since you'd expect one of NT or 95 to show up
the error because they have different implementations.

Cheers,

James "Wez" Weatherall
--
          "Xenophobes should go back to Xenophobia"
Laboratory for Communications Engineering, Cambridge - Tel : 766513
AT&T Labs Cambridge, UK                              - Tel : 343000




---------------------------------------------------------------------
The VNC mailing list - see http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------