The response RFB 003.003 just indicates that the machine in question is running an old VNC server.
How does this relate to your original problem? Cheers, Wez @ RealVNC Ltd. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Sergio Del Pino > Sent: 23 September 2004 23:09 > To: [EMAIL PROTECTED] > Subject: server closed connection unexpectedly > > I tried to run telnet to the machine running the vnc server > at port 5901 and I got RFB 003.003 instead of RFB 003.008. > The VNC server is running on a Win2K pro On the other hand I > can see a Win 2003 server running VNC Server 4 and a Win XP > pro running VNC Server 3.3.7, both from the same machine Win > XP Pro SP2 running VNC Server Service 4 and VNC Viewer 4. > > Thanks in advance, > > Sergio Del Pino > Argentina > server closed connection unexpectedly > James Weatherall jnw "at" realvnc.com > Thu Sep 9 10:04:00 2004 > > a.. Previous message: > =?iso-8859-1?Q?server_closed_connection_unexpectedly?= > b.. Next message: > =?iso-8859-1?Q?VNC4_Does_not_work_on_Windows_XP_but_VNC_3=2E3= > 2E7_Works_Fine?= > c.. Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] > > -------------------------------------------------------------- > --------------- > --- > > Hi, > > Assuming there isn't something fundamentally broken in your > Windows XP installation's TCP stack, there will be messages > other than "unknown network event for listener" in the > application log. They will be flagged as errors. > This also assumes that you are connecting to the correct port > in the first place. Can you use telnet to check that you're > connecting to the right port? (You should see "RFB 003.008") > > Your assertion that "it's definitely a software problem in > VNC 4" is bogus. > It's almost certainly a configuration issue, although it > could also be a problem with the host system. Reminder - > this is software we've tested extenensively and wouldn't have > released if it "just didn't work"... > > Wez @ RealVNC Ltd. > > > > -----Original Message----- > > From: vnc-list-admin "at" realvnc.com > > [mailto:vnc-list-admin "at" realvnc.com] On Behalf Of vnc "at" > > frifra.de > > Sent: 09 September 2004 07:22 > > To: vnc-list "at" realvnc.com > > Subject: server closed connection unexpectedly > > > > > > Hi, > > it's NOT e firewall issue! If i deinstall VNC 4.0 and reinstall 3.3 > > all works fine... both 3.3 and 4.0 are using Port 5900. > > It's definitly a software problem in 4.0, but it seems to > noone knows > > about... > > > > Remember: > > > At the application log i found many errors: > > > "SocketManager: unknown > > > network event for listener". > > > There is no firewall on this machines, also the XP firewall is > > > inactive. > > > > > > All previous versions worked fine, whithout of any > trouble... Now im > > trying for 3 days and nothing works! > > > > I don't understand, why they made a stable application such a crap > > (remind - it's a final, not a beatversion). > > _______________________________________________ > > VNC-List mailing list > > VNC-List "at" realvnc.com > > To remove yourself from the list visit: > > http://www.realvnc.com/mailman/listinfo/vnc-list > _______________________________________________ > VNC-List mailing list > [EMAIL PROTECTED] > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
