Alexander:
Hello! I've seen this before, but not on a 2k3 server. Try this: the
echoWinVNC server is based on the UltraVNC server. But the default
Viewer in EchoVNC is based on RealVNC. So try installing UltraVNC
on your Viewer PC, and use EchoVNC's GUI to choose the UltraVNC
Viewer as the default viewer. Then try to connect, and see if you get
the same problem.
cheers,
Scott
On Dec 7, 2005, at 10:27 PM, Alexander Alekseev wrote:
I have a client with echowinvnc working on a regular PC and I can
connect from my remote machine that runs echoserver.
I tried putting echowinvnc on their Windows Server 2003, it runs and
when I attempt to connect to it from my remote machine, it seems to
negotiate, the viewer window pops up for a second, and then goes away.
The total number of open relay channels goes up in the server window,
but I can't see the ws2003 running echowinvnc.
The windows firewall is NOT running on the clients 2k3 server, so that
shouldnt be causing a problem.
Any ideas?
-------------------------------------------------------
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://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Echovnc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/echovnc-users
