ADDENDUM: After writing this note I discovered something else. I a use a software firewall called winproxy on the vnc server machine. I set up a mapped port to be able to contact the vnc server from home. When I have this mapped port running I can connect to the server from home but I cannot connect to it from the internal network. Its like the firewall tells vnc to stop listening. If I make the vnc server listen on another port number other then the port that I have mapped in the firewall then I can connect to it from the internal network.
STRANGE??? Any advise? I am running eSVNC or ATTVNC on a win2k server machine. I would be glad if either on worked right now. Here is the problem WinVNC will not listen for a socket connection. This just started happening today and it has not bee shut down at all for the last 24 hours.I I tried ticking the allow sockect connection box and clicking apply. I have tried doing the same thing and clicking ok. I have tried directly editing the registry setting for WNC. But no matter what I do winvnc sudden now will not accept a socket connection. Ever time I tick the box and either click apply or ok and send it to the system tray then click the systems tray icon to bring it back up the allow socket connection box is unticked again. As I said I even tried editing the HKCU and HKLM registry keys directly it still would not keep that setting. As I said this happens with both the eSVNC server and the ATT Server __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
