Hi James: Let me restate my problem rather than to refer to another thread. My machine runs WinXP Home. 3 users are defined and have profiles on that machine. I want to have winVNC server started as a service as soon as I turn on the machine. In other words, I want it to respond to a remote viewer without any user having first to log on. Now, a user has to log on, stop, then start again the (or restart) the already running winvnc server service. When the machine starts, the winVNC service is already tagged as started and automatic.
James, you asked why I run the VNC server on display 4? Because my machine is assigned IP=192.168.2.4 on my home network. The network is behind a router and I want to be able to access it from a remote viewer elsewhere on the internet, specifically, from work. So I followed the suggestions given to me on the ''java.net:NoRouteTohost Operation timed out' problem (again)" thread, and it works. I think your question is really: Why did I telnet to port 5900 when this machine is on port 5904? Agreed. So I ran "telnet localhost 5904" from the Run window in the start menu, instead of stop/starting the winVNC service. But I got strange results: 1. I get the string "RFB 003.003" in the telnet window, but I have to close it mannually. 2. The desktop wallpaper is removed (and stays removed) 3. The service is not really turned on. Running the script at www.gotomyvnc.com gives negative results, ie no server detected. If it worked, doing "telnet localhost 5904" may be a substitute for stopping/starting the winVNCservice, but what's the point? Unless I can somehow activate the service before anybody logs in, I am not better off. And putting the telnet command in autoexec.bat is useless under WinXP (or is it ?). Thank you for your help, and hopefully this problem will be resolved. gc ----- Original Message ----- From: "James Weatherall" <[EMAIL PROTECTED]> To: "'George Cordahi'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Cc: "'Seak, Teng-Fong'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Friday, May 21, 2004 7:05 AM Subject: RE: can't connect to win2K server until service is stop/started George, Why are you running your VNC server on "display" 4? You refer to an earlier post regarding java.net exceptions, but that actually relates to port forwarding through firewalls/routers. If you are running your server on display 4 then you'll find that port 5900 won't be open but port 5904 will. "I have the same problem as described in this thread" is not, I'm afraid very helpful. A complete description of what you're seeing yourself is more helpful, since often the problems referred to are actually different in some important detail. 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
