Heya Scott: Re: below, you say that version of echovnc should not make a difference. However today I have been having lots of problems, most attributable to my typos, internet connectivity, etc. NEVERTHLESS, I can now tell you with a fair degree of certainty that when I went back to the pre-release version of echovnc on my customer's machine, just now, all my connection problems went away! I was consistently getting 'connection refused', which previously I only got when local loopback wasn't enabled.
I wonder if my success is due to a)versions on connecting machines must 'match', b) bug with 1.0 release not in pre-release c) simply the fact that I reinstalled?? But, I'm finally connected. Just FYI, throughout my vacation, I successfully used echovnc in a whole bunch of settings. My problems only started today when I downloaded the new release. Can you shed any light? Thanks! David -----Original Message----- From: Scott C. Best [mailto:[EMAIL PROTECTED] Sent: Monday, April 04, 2005 4:56 PM To: David Schlesinger Cc: [email protected] Subject: Re: [Echovnc-users] Problem today connecting to echoserver? David: Heya. Quick thought for you: > I had grand visions of all sorts of functionality that I wanted to discuss > today, but, my short term goal today is much simpler: Why can't I connect to > the echoserver from my client? > > I downloaded the 1.0 release from source forge to a customer's machine. > Can't connect to my echoserver.. same stuff I've been doing for the past 10 > days.. the only difference.. as best as I can tell.. is that I initially > used the 'pre release' that Scott emailed to me. Now using 1.0 release from > SF on the customer's site. Any major differences between the two? Nope, it shouldn't make a difference which version of EchoVNC you're running. The echoWare DLL version will make a difference, but nothing that should prevent you from connecting. I have seen some connection difficulties, but only when I have two or more echoservers, and then one goes down. The DLL doesn't seem to recover very nicely when this happens. In this case, I usually delete all of the echoserver entries, restart EchoVNC, and then re-enter the echoserver entry I want. For EchoVNC users with only one echoServer entry, this bug shouldn't be noticable. But for 2 or more...it's a known issue that we'll have fixed in the next DLL release. cheers, Scott ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Echovnc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/echovnc-users
