Dennis,

This suggests that the Access Control entries in the VNC Server Properties
->Connections tab is empty.  This would certainly cause the disconnect
behaviour you're seeing.

Regards,

Wez @ RealVNC Ltd.
 

> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Bathory-Kitsz
> Sent: 06 December 2005 13:28
> To: [email protected]
> Subject: Disconnects with 4.1
> 
> Hi all,
> 
> This is my first post. I searched the archives and have found similar
> questions, but no solutions yet. I apologize for dumping this 
> strange combo
> problem in a first post.
> 
> I have five computers on a mixed wired/wireless LAN, and have 
> used WinVNC
> 3.3.3 with four of them for several years. All are Win98SE, 
> and it's been
> very stable with them. I recently added a WinXP Pro laptop, 
> and decided to
> install WinVNC, and downloaded 4.1.
> 
> I was planning on replacing all the 3.3 VNC installations 
> with 4.1 until
> the behavior below happened. There's a little chart below.
> * All 3.3 servers can connect to all 3.3 clients and vice-versa.
> * No 3.3 client can 'see' the 4.1 servers (failed).
> * The 4.1 clients can connect to one of the 3.3 servers.
> * The 4.1 clients are connection-refused at the other servers.
> * The 4.1 client-server pairs connect and then immediately disconnect
> before asking for the password, which was a behavior reported in a few
> other posts.
> 
> Additional points:
> * Machine #4 has both 3.3 and 4.1 in order to test, so I turn 
> them on and
> off as services and reboot.
> * The connect and immediate disconnect behavior also occurs when the
> computer is asked to connect to its own server.
> * Zone Alarm has been uninstalled for testing.
> 
>               98-1    98-2    98-3    98-4(V3)        
> 98-4(V4)      XP-5
> 98-1  VNC3    -       OK      OK      OK      X       X
> 98-2  VNC3    OK      -       OK      OK      X       X
> 98-3  VNC3    OK      OK      -       OK      X       X
> 98-4  VNC3    OK      OK      OK      -       X       X
> 98-4  VNC4    OK      X       X       -       Dis     Dis
> XP-5  VNC4    OK      X       X       X       Dis     Dis
> 
> According to one post from a VNC person (sorry I can't recall 
> the name), I
> would need (1) the Event Viewer from the XP machine and (2) a Telnet
> connection to see what is reported.
> 
> The Event viewer on the XP machine says:
> Date: 12/5/2005       Source: WinVNC4
> Time: 10:04:06 PM     Category: None
> Type: Error   Event ID: 1
> User: N/A
> Computer: Valentino
> Description:
> SocketManager: unknown listener event: 0
> (Note that the results are the same when I use the local IP 
> address or the
> computer name).
> 
> The Telnet connection on the 98SE machine to port 5900 
> activates, shows
> itself connected for a fraction of a second, and then is disconnected.
> 
> Any hints?
> 
> Again, apologies for all this at once, but I'm loathe to 
> wreck the working
> 3.3 quartet just yet!
> 
> Thanks,
> Dennis
> _______________________________________________
> 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

Reply via email to