Scott, I'm also trying to use TightVNC (simply because I'd like a hidden icon and ability to register vnc as a service) and I seem to have the same sort of issue.
You should know that my echoServer is on another IP altogether and I RDP into it in order to check out the connection status while I'm testing. When I run WinVNC from the TightVNC_ew1.82 distribution (using v1.83 of Echoware.dll as per another suggestion of yours recently), I can configure and use an echoServer and it connects just fine. I verify that the connection is made by refreshing the status on the echoServer itself. Here's the problem, once I close the WinVNC.exe from the tray and restart it, my settings for the echoServer are still there just fine. They even show that it's connected! However, when I check on the echoServer itself, there is no connection. It doesn't reconnect ever again regardless of how many times I shut it down and restart unless I remove that server from TightVNC and re-add it back. It's a strange problem indeed. ________________________________ I've stopped 64,336 spam and fraud messages. You can too! Free trial of spam and fraud protection at http://www.cloudmark.com/sig/?rc=f9r9z -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Best Sent: Sunday, May 21, 2006 4:07 PM To: Ken Molnar Cc: [email protected] Subject: Re: [Echovnc-users] Problems with EchoVNC and TightVNC with Echoware Mr.Molnar: Hello! I'm trying to reproduce "Problem 1" below. Can you tell me: 1. Exactly what version of echoWare DLL is running? 2. Exactly what flavor of Windows OS are you using where the problem can re-appear? 3. When you reboot the machine (and it fails to reconnect), is there a connection from your PC to your echoServer established (i.e., if you run "netstat -an", can you see an established connection)? 4. When you reboot the machine (and it fails to reconnect), do you reboot to the login prompt, or directly into a default user? thanks, Scott On May 20, 2006, at 4:11 PM, Ken Molnar wrote: > Hello, > > I am having a couple of issues getting an echoware-enabled VNC > application to work exactly as I need. It seems that each variant I > have tried using has an issue that prevents it from entirely suiting > my needs. I need to be able to access a machine whether it is logged > in or not and then be able to log back out of it after I am done doing > what I needed to do. I guess I have no choice but to run whatever > program I use as a service. > > Problem 1: > I decided to try running TightVNC with the echoware version overlayed. > It works great except for one weird issue. It connects to the > echoserver just fine, even through logins and logouts...until you > reboot the machine. Once the machine is rebooted, it does not connect > back up to the echoserver until you log back into the machine locally. > The problem must lie within the echoware portion of the TightVNC > distribution because I can still access the machine directly via port > forwarding in the same situation. I tried the beta version of the > echoware-tightVNC and that did not resolve the issue. I have tried it > on more than one machine so that does not appear to be the issue > either. I have also mixed and matched various base versions of > TightVNC and that didn't seem to help either (though it seems each > version of TightVNC has its own weird little bugs, varying from > failure to replace the wallpaper after disconnect to the inability to > properly associate the locations of desktop and my documents during > file transfers). After many attempts at getting this solution to > work, I decided to try something else. This brings me to problem 2. > > Problem 2: > I read something in the archived mailing list here that suggested > running echoVNC as a service using Microsoft's srvany utility. > This seemed like a great solution because I prefer UltraVNC over > TightVNC anyways, and this method would let me choose. I got > everything up and running and it was free of ALL the bugs I was > experiencing in the TightVNC variation. I ran into a new bug, > however. This one is a little weird, though I am pretty sure it has > something to do with running the application as a service when it > wasn't designed to do so. I can log into a logged off machine the > first time, no problem. After I am done, I log the machine out and > disconnect. Now, I log back into the logged-off machine again. No > problems here. Now I try to log off the machine before I disconnect > again. It won't let me. You can't restart, shut down, log off, > nothin. The only way to get it to log off or restart is to hit ctrl > alt delete and terminate echovnc.exe. Once you terminate it, you can > log off or reboot as normal. Only problem with this is that now if > you log off, you will not be able to connect again because the service > isn't running. > > Does anyone have any idea how to a.) fix the problem with one of > the two solution methods or b.)know another method that I can try? > I would really appreciate any help anyone has to offer. This > echoserver based VNC thing is absolutely awesome. It is wonderful not > having to configure ports and not having to worry about dynamic IPs. > Thanks in advance, and sorry for the long read. If you need any more > information please ask. > > Thanks again, > Ken Molnar ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Echovnc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/echovnc-users _______________________________________________ Echovnc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/echovnc-users
