Hmm. Try this: activate logging on your echoServer, restart it,
then reproduce the error. There should be a "echoserver_port####.log"
file generated (in the echoServer install folder) that will be helpful
for
me.
thanks,
Scott
On Aug 12, 2008, at 1:03 PM, Peter White wrote:
> 1.64
>
> -----Original Message-----
> From: Scott Best [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, August 12, 2008 3:37 PM
> To: Peter White
> Cc: echovnc-users@lists.sourceforge.net
> Subject: Re: [Echovnc-users] Can't connect to 2.35
>
> Peter:
>
> Hello! What version echoServer are you running to connect the
> two side together?
>
> cheers,
> Scott
>
> On Aug 12, 2008, at 11:43 AM, Peter White wrote:
>
>> Hi,
>> We have installed two sites with 2.35 and can't reliably connect
>> to either of them. One ijs 2003 server. One is 2000 server. Both
>> sites show up in the partner ID list but when we click to connect we
>> get an error that the remote partner can not be found.
>> What to do?
>> Thanks
>> pw
>>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Echovnc-users mailing list
Echovnc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/echovnc-users
