Heya Scott and all, Thanks for your reply re: where to post.
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? Maybe I'm overlooking something simple, or, maybe it's internet connectivity, although everything else seems to be working. Thanks! David -----Original Message----- From: Scott C. Best [mailto:[EMAIL PROTECTED] Sent: Monday, April 04, 2005 2:17 PM To: David Schlesinger Cc: Subject: Re: [Echovnc-users] Trying to get straightened out on where to post David: Heya. Some answers to your questions: 1. Posting here is probably best. Right now the Email list is acting "restricted" due to some bug at SourceForge, so i have to personally approve every message that's posted before it's accepted. But I'm optimistic that will be fixed soon... 2. I don't regularly check the SoureForge "forums"; usually some emails me to remind me to check the forum for something they posted. :) 3. Email lists and forums are, I believe, seperate entities on SF. So, this is how it'll be. 4. The "DNS bug" is identified and will be fixed in the next release. I am expecting we'll have something by the end of the week. -Scott On Mon, 4 Apr 2005, David Schlesinger wrote: > Heya Scott and all , > > I have lots of feedback to post, issues to discuss on echovnc (mostly > good!), but I'm confused about how where to post: > > 1) see that I can post here: > 1a) see that there is a READ only web interface to read the messages and > threads for echovnc-users > > 2) see that that there are two read-write forums 'open discussion' and > 'help' which I posted to a while back but got no reply. > > 3) why are these all separate and why can't echovnc-users be setup like the > other two forums where I can read the message in thread format, and reply > from the web interface. > > 4) Want to respond in thread format to 'paul perpich's post on dns - the > short of it is that I am also hoping this issue is resolved. I see that > echovnc still shows the dns name, not the ip, but whether it rechecks the > dns name, I guess he is saying no. Kaboodle resolved it once and returned > the ip address name, at least echovnc still shows the dns name. > 4a) hoping to get a timeframe for a fix on that - busy setting up lots of > users with echoserver on my dynamic IP - which, fortunately, hasn't changed > in a month! If fix is coming soon I'll wait, otherwise, have to get a static > ip. ------------------------------------------------------- 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
