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: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] > Sent: 09 September 2004 07:22 > To: [EMAIL PROTECTED] > 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 > [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
