Stan,
TightVNC and UltraVNC are the two distros supporting single window
broadcast. TightVNC has much better single window feature implementation
comparing to UltraVNC.
UltraVNC's implementation of this feature is half broken.
Kindest regards,
Yury Averkiev
SmartCode Solutions - Network Manageme
Any idea how they work ?
Since VNC intercepts signal at "Device Layer" level, how do they
reconstruct the Windows semantics ?
Bests,
-stan
On Sep 13, 2007, at 12:12 AM, Yury Averkiev wrote:
Stan,
TightVNC and UltraVNC are the two distros supporting single window
broadcast. TightVNC has mu
The principle how they work is quite simple. In the single window mode,
instead of broadcasting the whole desktop, the VNC server just broadcast the
part of the desktop occupied by the window. Basically what VNC server does
is figures out the window coordinates with GetWindowRect WIN32 call and
bro
Hello everyone,
when connecting to an host behind NATs (Networks Address Translators),
theres to do port forwarding from/to every NAT in the route; i know it
is possible to address this problem with the "Listening VNC viewer"
feature which makes the viewer to bind a port and get called by a rem
https://www.copilot.com/
made with wholesome "Joel on Software" goodness.
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
Abi:
Heya. Similar to the Yoics solution is EchoVNC:
http://www.echovnc.com
The idea is that both sides of the VNC connection (server
and viewer) make an independant "login connection" to publically
available server. This new server then acts as a "relay point"
between the two
We can not connect to one of our VNC Servers. This is the error message we get:
---
VNC Viewer : Question
---
The connection closed unexpectedly
Do you wish to attempt to reconnect to a3-0042?
---
Yes No
---
