UltraVNC

Sorry, I don't understand. (Also, I've gone off topic, since the OP really was asking about file transfer, which I gather just isn't compatible across VNCs.) Are you suggesting using EchoVNC to establish a connection (presumably using your demo relay) and then essentially tunnelling something like ...

Heyaz. Please note that you can configure both the EchoVNC Viewer and EchoVNC Server to handle just the "firewall-friendly" connection part, and then offload to a different VNC Viewer or VNC Server to handle the actual VNC session. Our app runs alongside other VNC apps just fine. -Scott (EchoVNC guy)

When you ping the server, what's the response time? The demo server to me is less than 30mS. No performance issues, if less than 50.

-Scott

Thor:

Aye, that's it exactly.

-Scott

Thor: Heya. Yes, you have the idea: you create a connection Group, and give that Group a password. Anyone who knows the password can join that connection Group, and anyone in the Group can establish connections to each other. Once the connection is established, of course, there's a VNC password ...

Heyaz. The 2.10 release of EchoVNC is now available, as mentioned in the related UVNC forum [topic=3557]here[/topic].

cheers,
Scott

Just a note that the 2.10 release is now available. You can see the release notes on the Sourceforge project page.

cheers,
Scott

Jack: Heya. Sorry that you got a little confused: once you're connected to the echoServer from both sides of the connection (ie, from both the Viewer and the Server), you won't need to adjust the firewall settings at all. That's the point. :) Before you setup your own echoServer, I suggest ...

Infostrada:

Yup, thanks. All fixed!

-Scott

Heyaz. The RC10 release of UltraVNC-with-echoWare is now available. Installer is here , source is here . In this latest release, we worked on the following: 1. Uses the latest echoWare DLL, with improved latency performance 2. Improved VNC file-transfer reliability 3. Added a "See Who's Available ...

Rob: Heya; sorry for not being clear: the echoWare enhancements to UltraVNC are not (yet?) in the main 1.02 release, but in a modified release, available here . To load the echoServer information into UltraVNC: 1. Once the Server is running in the service tray, right-click on it and choose ...

Rob:

Heya. Yes, there is some addtive latency due to echoWare/echoServer, and that's what causes that delay. We're working on minimizing the latency, which you can try out by updating the echoWare DLL on both sides of the connection to this one.

I hope that helps!

-Scott

MrChris:

No hassle at all. Am eager to see what you come up with.

cheers,
Scott

MrChris: Heya. Sorry, am not seeing the bug you describe. Am doing this: 1. Install UltraVNC with echoWare, register it as a service. 2. Delete all EchoServer keys in ORL\WinVNC3 for both HKCU and HKLM. 2. Restart. 3. In the service tray, right click on UltraVNC, select echoServers. 4. Should be ...

MrChris, Sparad0x: Right, all of the data during the session goes thru the echoServer. We've made a lot of progress in keeping the additive latency to a minumum. Fortunately, VNC doesn't require a very high bandwidth connection. It will be slower than a "direct" connection, but not annoyingly so ...

Sparad0x:

Heya. Sorry for the late reply. Yes, similar to a VNC Repeater, all data between the Viewer and the Server is relayed thru the echoServer. Makes for more reliable connections.

-Scott

MrChris: EchoVNC is really just a "GUI wrapper" built around echoWare -- it helps to create connections, but pretty much leaves it up to VNC after that. So if the VNC viewer that EchoVNC "auto activates" supports screen-scaling...then it should work as requested. Alternatively, don't use EchoVNC at ...

MrChris:

Nope, it's "free" as in beer, with no time limits. It's sort of an ongoing reliability experiment.

cheers,
Scott

Heyaz. We just finished integration of the echoWare DLL with the recent UltraVNC 1.02 release: the result is EchoVNC 2.0 . You can download the installer or download the source from our FTP site. As many of you know...echoWare is the essential component of EchoVNC, allowing firewall-friendly access ...

Just to emphasize: it works fine if the VNC Server is installed as a service, even when the PC is "locked". It just fails to accept sessions when it's running in standalone application mode, once the PC has locked.

Bug or feature?

thanks,
Scott

Heyaz. Am trying to connect UltraVNC Viewer 1.02 to UltraVNC Server 1.02, where the server is running in application mode, but the screen saver has kicked in, and the screen is now locked. The Viewer connects, passes passsword authentication, and is then immediately disconnected. The WinVNC log file ...

US:

Great, thanks! Turns out, it builds from the JavaViewer mk.bat file as well (after I installed the J2SDK). But CVS is easiest.

-Scott

Heya. I grabbed the source for 1.0.2 from CVS last night, but the DH.class file is missing. The winvnc.rc file expects to see res\dh.class, but it's not there. It's also not in previous version source zip files. I Google'd for it, and found a DH.java which I can compile but...does anyone have the ...

Phil:

Sorry for the very late reply: the single-click version of EchoVNC is called EchoWinVNC; they're both part of the Remote Support System you can find here.

Hope that helps!

-Scott

Chris:

Heya. Glad it works for you! We run a free server at "demo.echovnc.com" if you want to simply relay on that one. Otherwise, the echoServer itself is a $25 shareware app (Windows or Linux) to remove the 10-minute connection limit.

cheers,
Scott

Chris: Heya. That's what echoWare does, which is the software behind EchoVNC . With echoWare, any two applications can interact with each other via a 3rd party "relay server" called an "echoServer". EchoVNC isn't much more than a GUI wrapped around echoWare in order to facilitate making VNC ...

EC: Heya. At the risk of self-promoting, EchoVNC is a much easier solution. Just install it alongside your target VNC servers, and use it to login to a common echoServer. Login with names like "PC-1", "PC-2", "PC-99", etc. Then when you login to the same echoServer from anywhere else, you can easily ...

Bill: Heya. Not a dumb question at all. Here's how to think about it: an open-port, by itself, isn't dangerous. What's dangerous is the stability of the software *listening* to network traffic on that port. All the encryption in the world won't help against attacks on a poorly written application ...

Heyaz. This is an announcement of the 1.1 release of echoWinVNC, an echoWare-enabled, zero-configuration VNC Server for remote-desktop control of Windows PC's. http://www.kaboodle.org/images/ewvnc_screen.gif Source and binaries are available here . In this 1.1 release, we've improved the ...

Yes, if an EchoVNC client is behind a restrictive firewall or web-proxy setup (not "most cases", but pretty common), EchoVNC clients will most likely be unable to connect with echoServers on their default port, TCP 1328. If you are running your own echoServer, you can set it up to run on TCP 443 ...