Ravi:
I'm glad it worked, even if only temporarily. :) I've only seen the
10061 error
with RealVNC 4.x. when I run an earlier version of EchoVNC. Whenever
I've
used 1.40 of EchoVNC with RealVNC 4.x, I've seen it work.
Keep in mind: the 10061 error originates on the *far* side of the
connection,
on the PC being remote controlled, running the VNC Server. It's not
caused by
the VNC Viewer.
hope that helps,
Scott
On Oct 28, 2005, at 4:16 PM, Ravi Teja wrote:
In the beginning I was using EchoVNC 1.3x and UltraVNC Win32 version
1.0.1.
When you provided me with EchoVNC 1.40, I changed to the same and
changed server to Real VNC Free Edition 4.1.1.
After numerous attempts to fail to connect to the host, by
disappointing, I stopped working on this for the last two days.
Today when I am back to my usual work and when I am cleaning up my
desktop I saw the EchoVNC icon and as a last try I just gave a click
on "connect via echoserver" with the partner-ID.
Do you know what happened ?
Hurrah ! :-D
I got connected. I do not know what happened.
No windows updates installed.
No firewall configuration.
No router configuration.
No configuration from host side.
I am really confused what it made to connect.
When I gave a click on "connect via echoserver" again, the same story
continues " Unable to connect to host: Connection refused (10061)" and
sometimes it is
"connection closed unexpectedly"
Any ideas ?
----RT
[EMAIL PROTECTED]
----- Original Message ----- From: "Scott C. Best" <[EMAIL PROTECTED]>
To: "Ravi Teja" <[EMAIL PROTECTED]>
Cc: <echovnc-users@lists.sourceforge.net>
Sent: Wednesday, October 26, 2005 6:37 PM
Subject: Re: [Echovnc-users] Unknown 3.3 security type
Right, the 10061 is due to an incompatibility with RealVNC
that we fixed with the 1.40 release of EchoVNC. Please make sure you
have 1.40 on both sides of the connection.
And no bother. :)
-Scott
On Wed, 26 Oct 2005, Ravi Teja wrote:
I am sorry to keep you disturbing, but i have no other source to get
help.
I changed it to default viewer. This time it says
The connection closed unexpectedly
Do you wish to attempt to reconnect to 127.0.0.1::4292 ?
If i click yest it ends up with "Unable to connect to host:
Connection refused (10061)
But, this is not happening when i try connecting my own system from
the host side using EchoVNC. I am able to connect from one side but
the viceversa is not happening.
---RT
[EMAIL PROTECTED]
[EMAIL PROTECTED]
----- Original Message ----- From: "Scott C. Best" <[EMAIL PROTECTED]>
To: "Ravi Teja" <[EMAIL PROTECTED]>
Cc: <echovnc-users@lists.sourceforge.net>
Sent: Wednesday, October 26, 2005 5:54 PM
Subject: Re: [Echovnc-users] Unknown 3.3 security type
On your EchoVNC side, please re-select the VNC Viewer that
came with EchoVNC; the one in the EchoVNC installation folder.
thanks,
Scott
On Wed, 26 Oct 2005, Ravi Teja wrote:
I tried with your solution.
I stopped UltraVNC server at the host and started RealVNC in
service mode.
When i connect to the host, the viewer displayed "connecting...."
message approximately 10-15 minutes and then ended up with this
diaglog box.
-------------------------------------------------------------------
-------------------
Connection Failed - Error reading protocol Version
Possible causes:
- You have forgotten to select a DSMPlugin and the server uses
a DSMPlugin
- Viewer and server are not compatible (they use different RFB
protocols)
- Bad connection
-------------------------------------------------------------------
------------------
PS: I am not using any Plugins either at the viewer side or
server side.
-- RT
[EMAIL PROTECTED]
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Echovnc-users mailing list
Echovnc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/echovnc-users
