Heya Scott: In the meantime I discovered that when you spell the user name 'Phyliss' in the echoserver and 'Phyllis' when you try to connect it doesn't work.. truly another 'duh moment' for me. I'm having a lot of them today.. No amount of bug fixing or even data validation will fix my inclination to overlook obvious typos..
Also, now I am realizing that echovnc is not recognizing the running (I think it's running) winvnc server on 'phyliss's' machine. I just installed ultravnc rc203 - a brand new release - and I am wondering whether it is the culprit - because I'm still having trouble even after fixing all my typos. And, finally, I am wondering whether having a running listening viewer on my local machine here has any effect - I am connected to another machine on the customer's network that way. And, also, my internet connection is very flaky today. Lots of timeouts and disconnects. This, coupled with my lame typing, and new vnc server makes it difficult to sort out the real problems from the ones I imagine... so sorry to worry you if it turns out to be unnecessarily so. (Actually this (internet connection being flaky) is a serious issue for me, and since my requirements to support clients on demand keep growing I am wondering about how I can insure a more reliable connection. Right now I am on a home based dynamic IP plan from my cable provider - not a business plan - I am wondering whether upgrading to a business plan will increase my uptime or whether that is just marketing hype by the cable providers to sell their business level service, also don't know whether the disconnects are more related to lack of reliability by the ISP, or maybe it's just my cheapo 79 dollar cable modem, in any event, my goal is to greatly increase my uptime and reliability, any feedback on how to accomplish this, hopefully for a reasonable price, is greatly appreciated ) Re: the multiple echoserver bug, that's good to know but I don't think it was my problem as I only had one echoserver entry. Also, good to know about the differences in the versions. 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
