George, Thanks for the clarification, but some details are still missing.
You state that "Now, a user has to log on, stop, then start again the (or restart) the already running winvnc server service". You don't specify *why* they have to do this. What is the effect if they don't? In particular, can you use telnet to the server port before any users have logged in? Can you telnet to the port after a user has logged in but before the server has been restarted? I'm still not clear on why you are using display number 4 - your NAT router can almost certainly redirect requests for display 4 externally to display 0 locally, so that different machines externally appear as different display numbers while locally they all use the default port/display settings. Remember to provide equivalent forwarding of port 5804, etc in order for the Java viewer to be available. The string "RFB 003.00x" (where x is 3, 7 or 8) is what you should see when connecting to a server via telnet. This indicates that the server is indeed listening for connections, indicating that if you are unable to connect then the problem is somewhere else in your system's setup. The script at www.gotomyvnc.com is not authoritative - it simply tried to connect back to your server on a set of VNC ports. That might fail because of network configuration issues even though your VNC Server is working perfectly. My first recommendation is to upgrade to VNC 4.0 Beta 5 at the server, since it is more stable and easier to configure than VNC 3 series servers. Cheers, Wez @ RealVNC Ltd. _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
