VNC 1.4.3 remote problem 10054

[James Weatherall]

Bill,

VNC Free Edition is not compatible with Remote Desktop nor Fast User
Switching, in general - once you've used either on a server computer you won't
in general be able to access it via VNC Free Edition, because of the way RD &
FUS affect the console "session".  If you don't use RD or FUS then VNC Free
Edition server should work fine.

VNC Enterprise and Personal Edition servers have better support for systems on
which Remote Desktop & Fast User Switching are used.

Regards,

--
Wez @ RealVNC Ltd


> -----Original Message-----
> From: vnc-list-admin "at" realvnc.com [mailto:vnc-list-admin "at" realvnc.com] On
> Behalf Of Bill Schlossberg
> Sent: 14 January 2009 13:59
> To: vnc-list "at" realvnc.com
> Cc: rh56 "at" optonline.net
> Subject: VNC 1.4.3 remote problem 10054
>
> Hello, when attempting to VNC (ver 4.1.3) from machine-A to machine-B,
> both
> inside my home Linksys router I get Connection reset by peer [10054]
> after I
> am prompted for my password.  When I do the reverse (with machine-A as
> server); no problem, goes right in.  Same behavior whether I use
> hostname or
> IP.
>
> I can RDC with no problem between the two machines (both ways with host
> or
> IP), and each can ping the other.  In fact I was able to VNC from
> machine-A
> to machine-B until I forgot I was RDC'd back to machine-B when I
> connected
> the VNC from machine-B to machine-A where I was sitting (I am
> experimenting
> with different remote solutions) which, to my surprise, worked, but
> then
> worked never again (gave me a kind of affect like when two mirrors face
> each
> other at slight angle-continuous reflection).  Prior to this incident
> it had
> worked several times as well.
>
> The two machines are configured the same except machine-A is Windows XP
> and
> machine-B is Windows VISTA (Home Premium) laptop.  Both have been
> restarted,
> and all the basic troubleshooting multiple times. I turned windows
> firewall
> off on machine-B but no luck.  I also reloaded VNC on both but no luck.
>
> The only thing odd I found in the event logs was on machine-B
> reporting:
> "The terminal server security layer detected an error in the protocol
> stream
> and has disconnected the client."
>
>
>
>
>
> Thanks for any help,
>
>    Bill Schlossberg
>    wschloss "at" optonline.net
>    203-961-0363 Stamford, CT
>    203-979-5217 - cell
>
>
>
> Addressee:
>
>
>
> [demime 1.01d removed an attachment of type image/gif which had a name
> of image001.gif]
>
> [demime 1.01d removed an attachment of type image/jpeg which had a name
> of image002.jpg]
>
> [demime 1.01d removed an attachment of type image/jpeg which had a name
> of image003.jpg]
> _______________________________________________
> VNC-List mailing list
> VNC-List "at" realvnc.com
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list