Pete:
Thanks for the very detailed message. Before I digest it entirely,
I wanted to quickly suggest you try the pre-release of an improved version
of TightVNC-ew:
ftp://ftp.echogent.com/TightVNC/beta/TightVNC-ew1.82.zip
Since you seem so methodical in your testing, I would very much
appreciate your perspective on the new software.
thanks,
Scott
On Fri, 14 Apr 2006, Pete Givens wrote:
I am evaluating EchoVNC for use as a support tool in my network consulting
business. The product looks wonderful, and I'm very excited about it, except
for *one* problem: I cannot get the TightVNC servers to re-connect to the
echoserver after they reboot.
I cannot find anything exactly relating to this in the list archive. Does
anyone have any ideas?
Here's my setup:
- Echoserver: Windows version 1.41, running on XP Pro sp2, fully updated, Zone
Alarm 6.1, Norton AV 2003
- sitting on a static IP, behind a Linksys router which has only port 1328
forwarded
- this is a non-registered copy
- Client PC: EchoVNC for Windows, v.1.40, running on XP Pro sp2, fully updated,
Zone Alarm 6.1, Norton AV 2005
- Host PC #1: TightVNC 1.2.9, overlaid w/ TightVNC 1.3dev5-ew, running on XP
Pro sp2, fully updated, Norton AV 2005
- Host PC #2: TIghtVNC 1.3dev7, overlaid w/ TIghtVNC 1.3dev5-ew, running on
Win2k sp4, Norton AV 2005
Here's the scenario:
1. On either Host PC, Install either TightVNC 1.2.9 or TightVNC 1.3dev7, then
copy over files from TightVNC 1.3dev5-ew. Set default password. Set to allow
loopback connections. Set to use echo server connections if available.
2. On either Host PC, set up connection to my Echoserver. Connection is
successful.
3. I am able to connect via my Client PC, running EchoVNC. I can log off & log
back in at will. I can connect multiple times.
4. If I reboot, however, the trouble starts:
a) I cannot connect to the Host PC. The only solution I have found is to
delete the echoserver entry in the table, and
recreate it. Once that has been done, I can once again log in and out
at will, as long as I don't reboot.
b) After a reboot, I note the following:
1) I cannot connect to Host PC.
2) A check of VNC's control panel shows "Connected" on the line for
my echoserver.
3) The Host PC does not show up in the status panel of my echoserver.
5. This behavior does NOT occur when I use demo.echovnc.com
Questions:
1. What accounts for the different behavior of demo.echovnc.com, and my
Echoserver?
2. How do I correct it? It looks to me like this is a Echoserver issue? Did I
do something wrong when I set up my Echoserver?
I have attached a log from one of the client machines, with liberal comments
added. This log walks thru the process of setting up a connection with both my
echoserver and the demo echoserver. If more information is needed, please let
me know.
Thanks,
Pete Givens
Kadan Systems, LLC
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Echovnc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/echovnc-users
