I may be misinterpreting what you said, but it appears you're saying that the VNC client connections drop as soon as you stop the VNC service. That's expected; they are no longer connected to anything.
Does NetxXray show you the connected ports? If not, you can go to the server and issue this command in a console prompt: netstat -an this will show you all connections in numeric form. You should see on the lefthand side the server address listing and ports; for example, if the server address is 192.168.1.1 you will see lines like UDP 192.168.1.1:139 yadda-yadda TCP 192.168.1.1:5900 yadda Connections to port 59xx on the server are from *live* VNC connections. If you have connections on port 139, those are Windows clients actually accessing fileshares over the network. See if you are showing clients on port 139. ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday/2002 January 28 15:15 Subject: WinVNC server connecting automatically to clients over WAN : NT Sever SP 6a. running WinVNC sever as a service. After installing Local : LAN user started complaining of slow network response. Using NetXray I saw : Remote clients connecting to the server only clients that are connecting : are the ones with WinVnc. I stop the VNC service on the server and the : connections dropped. Any Ideas why this would be happening. : --------------------------------------------------------------------- : To unsubscribe, mail [EMAIL PROTECTED] with the line: : 'unsubscribe vnc-list' in the message BODY : See also: http://www.uk.research.att.com/vnc/intouch.html : --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
