Rolf:
That's a really good point, thanks. We're working on the GUI of the
1.2 release, and I'll be sure to test if this "Okay" button is
required or
just "nice to use".
thanks,
Scott
On Feb 15, 2006, at 8:51 AM, Rolf Heelas wrote:
Scott,
Not sure if the problem has gone away or this is another issue, but
I think
user error might have been an issue
When you run the echowinvnc enduser sider and the miniwinVNC
dialogue box
pops up I has assume it is all ready for a connection as the text
seems to
say, If I run the echoVNC client I can pair up to the other user
fine, but
the VNC window never pops up and I can not connect.
But if the end user click OK and program goes into the system tray
and then
try to connect in echovnc it works a treat
It is slighly confusing as on the user side it says it is conencted
and
ready when it is not, and on the admin side it pairs up and goes no
further.
I would have expected users to click on the OK button, but on the
test sites
I tried 2 of 3 did not.
Apart from that issue I am loving it :)
Regards,
Rolf Heelas
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
Scott C.
Best
Sent: 13 February 2006 20:46
To: Scott Mize
Cc: Rolf Heelas; [email protected]
Subject: RE: [Echovnc-users] Problem with server
Scott:
Good call, that seemed to work. :) I'll make sure to get the
pre-release into the major release this week. We're finalizing the
1.80 DLL, which is the reason for the delay at all...
-Scott
On Mon, 13 Feb 2006, Scott Mize wrote:
127.0.0.1 is a local host address, this is normal behavior. I would
suggest
trying the pre-release client software.
Scott Mize
Technology Specialists LLC
Phone: 503-504-7748
Fax: 503-643-8279
Email: [EMAIL PROTECTED]
Website: www.technology-specialists.net
Not everything that can be counted counts, and not everything that
counts
can
be counted. -- Albert Einstein
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rolf
Heelas
Sent: Monday, February 13, 2006 9:07 AM
To: [email protected]
Subject: [Echovnc-users] Problem with server
Hi,
Wonder if you clever people can help a newbie out
I am having major problems with echoserver, I can get user servers to
connect
but the client just flakes out, it can partner with another user
but when
the
viewer should pop up it does not. I get the impression it is
trying to but
is
failing quickly.
Some details
The server is on a linux server running centos inside my firewall
on ip
192.0.0.130 the vnc server is outside on the net and connects
fine, the
client is also inside the firewall on 192.0.0.4
what is odd is when I look at the logs for the client it has
messages like
[02/13/06-11:10:23] New socket : 496 added to complete socket
pair : 580
in
list [02/13/06-11:10:23] ENDC Dll : Accepted Client socket for Data
Proxying
:
127.0.0.1:1450
which is an ip which is not on my network
also if I run the viewer on its on it is also in the history it is
trying
to
access a machine 127.0.0.0::port num
What is odd is that this worked once. I have started and restarted
the
server
many time, I even copied the the software on to Xandros box with same
problems
Any ideas anyone? as you have guessed I am not a linux expert.
Would the
PC
version work any better, The only reason I did use linux was
because I did
not want to buy an xp license for just a trial run
Regards,
Rolf
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Echovnc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/echovnc-users
