Robert:
Bah, sorry, my mistake: the 1.31 version is a very small
bugfix over the 1.30 release.
There does appear to be a problem with EchoVNC in how
it *disconnects* from the echoServer -- it doesn't seem to
"assertively" disconnect -- it waits for the echoServer to "time
out" the connection. This can make the echoServer think it has
multiple connections to the same client, so when you try to
re-connect to said client, the echoServer cannot distinguish
between the two duplicate entries, and so the connection fails
to establish.
The workaround right now is to either:
1. Completely quit and restart EchoVNC on both ends of the
connection before a session is initiated.
2. Restart the echoServer before a session is initiated.
Both of these are very ugly workarounds. I'm working on
a quick-fix patch release of EchoVNC 1.32 right now. More news
as I have it...
thanks,
Scott
On Jun 5, 2005, at 11:45 PM, Scott Best wrote:
Robert:
Wow, that's annoying...the CNET sites have version 1.30 on
them, not the very latest 1.31. I'll update that now.
In the meanwhile, please try using the software here:
http://prdownloads.sourceforge.net/echovnc/EchoVNC_1.31_Setup.exe?
download
Also, to fully utilize UltraVNC, be sure to browse to your
UltraVNC Viewer in EchoVNC's "Veiwer" tab.
Finally, you shouldn't have to adjust any firewall settings
on WinXP-SP2.
-Scott
On Jun 5, 2005, at 9:47 PM, Robert Burdge wrote:
Scott,
I was able to attempt a connection from the XP Pro PC on my LAN to a
pair of other PCs on another LAN. One of the PC's is running Windows
2000 and the other is running XP Pro. Both machines are behind an
ISP-supplied router. I was able to connect all machines to the Demo
EchoServer. When I initiated a connection from my XP Pro machine to
the remote machine running Windows 2000 (and an UltraVNC Server) the
Partner was found and I received an UltraVNC Password request. I
supplied the password and the login pop-up disappeared, but the
UltraVNC Viewer never appeared. The second and subsequent times I
attempted to create a connection I received a connection failure
pop-up without ever getting a login pop-up for the remote PC.
I then attempted the connection in the opposite direction. I started
an UltraVNC Server on my PC and had my wife attempted to login from
the remote PC running Windows 2000. This connection was successful
the first time. On subsequent attempts a connection failure was
reported prior to getting the login/password screen.
Finally I attempted to establish a connection with the remote XP Pro
PC from my XP Pro PC. This behaved the same as the connection
attempts to the remote Windows 2000 PC, with a connection failure
reported prior to the login screen.
I have included the connection log that was recorded during my
various connection attempts (very long - sorry). Hopefully this will
give you some information to help debug this problem. I am running
the latest EchoVNC Ver. 1.3 (from Download.com) and Ver 1.0 RC18 of
UltraVNC (downloaded from SourceForge). My installation of XP Pro
came with a new computer about 1 month ago and came with SP2 factory
installed. The remote PC running XP Pro has been upgraded with SP2.
I attempted connections after disabling Firewalls on all of the
involved machines without any effect. Assuming that EchoVNC and
UltraVNC work for most users, I must have a configuration setting in
one of these programs or a system setting in XP Pro that is
incorrect. Any help would be greatly appreciated.
<snip>
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
Echovnc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/echovnc-users
