"reading version failed"

[Craig Musgrove]

Bit of an update.
Checking out one of these locations, I discover the service-mode starts VNC
listening on port 4900 (?!)
I change to 5900 on both service and user mode and it sticks.. Till I
restart the computer, then back to 4900.
This is why I am getting the no connection issue, but why is this happening.
I have uninstalled and reinstalled the app, deleted realvnc folders, but
still it installs with the same 4900 port
Specifying 4900 from the viewer on another computer in the same network only
occasionally connects to the VNC server... Haven't figured out the pattern
there.

?





Craig Musgrove 

--------------------------------------------------------

From: "James Weatherall" <jnw "at" realvnc.com>
To: "'Craig Musgrove'" <craig "at" sunokacomputers.com>,
  <vnc-list "at" realvnc.com>
Subject: RE: "reading version failed"
Date: Tue, 17 Oct 2006 14:56:05 +0100
Organization: RealVNC Ltd.

Craig,

Have you change the port number VNC Server is set to listen on?  Are you
specifying a port number when you use VNC Viewer to connect?

Regards,

Wez @ RealVNC Ltd.
 

> -----Original Message-----
> From: vnc-list-admin "at" realvnc.com
> [mailto:vnc-list-admin "at" realvnc.com] On Behalf Of Craig Musgrove
> Sent: 17 October 2006 00:43
> To: vnc-list "at" realvnc.com
> Subject: "reading version failed"
> 
> I have 2 locations which we upgraded from Version 4.1.1 to 4.1.2
>  
> Neither of these locations accept connections now
>  
> VNC viewer:question
> reading version failed: not an RFB server?
> Do you wish to attempt to reconnect to ....?
>  
> My research seems to uncover the server is not running the software.
> I know this is not so.
>  
> ?
>  
> 
> 
> 
> 
> 
> Craig Musgrove