Hi.
I have 3 machines for testing: 1 Linux (the echoServer) and 2 WinXP (1-the echoVNC viewer, 2-the echoWinVNC VNC-Server (named asus))
I downloaded echoserver-1.4rc02 on linux and started it using the default config file like this:
./echoserver-1.4rc02 -p 1328 -l ./echoserver.log
This successfully creates 4 processes.
I then connect using the WinXP (asus) echoWinVNC.exe 1.1 program and use my server-fqdn, the password test2005 (per default config file) and a username (defaults to name of computer, in this case asus). This works.
Seperately and on a different windows computer, I add an echoServer within echoVNC 1.4 and use the same username/password asus/test2005 and connect to the same domain name. This works. I then "Start a VNC Connection" from the Main tab and enter asus as the partner-id and click connect via echoServer. I then can control the asus machine. Great!
Also, I am able to properly issue -q and/or -u on the linux server and get the expected response.
Now, for the problem:
I change the existing echoServer instance within echoVNC 1.4 and use the default username/password admin/nosecret and connect to the same domain name. This works. But when I "Start a VNC Connection" from the Main tab and enter asus as the partner-id and click connect via echoServer, it fails. Additionally. the -u and -q parameters no longer work on the linux server and an additional 4 processes are created for a total of 8.
I am interested in purchasing the Commercial version, but not until everything works as expected. Please advise.
Stefan Adams, president
Cogent Innovators, LLC
