TeamViewer is actually a subset of UltraVNC.
The difference is that UltraVNC being stand-alone needs to be set with port
opening on the Host side.
TeamViewer bypasses the issue by using their own Server as an intermediary.
I.e., like Logmein and others someone else mitigates your traffic.
Remote Desktop/Assistance, and regular UltraVNC are direct connections with
No 3rd party intervention.
My approach is. If someone can set the system on the other side, I would go
with the Direct approach (Remote Desktop/Assistance, or regular UltraVNC).
Otherwise, I default to TeamViwer or logmein. Whichever seems to be more
suitable to the issue at hand.
Control wise, straight UltraVNC provides the highest level of control. http://www.ezlan.net/vnc.html http://www.ezlan.net/myip.html
Jack (MS, MVP-Networking).
"Ed." <Ed@newsgroup> wrote in message
>I no longer mess with Remote Assistant. I now use TeamViewer. It's free
>and much better. I don't install it nor have the other person install it.
>During Setup we just click on run and not install. Have the other person
>give the IP address it shows on their end and the password for you put in
>your end and BINGO.
> Take a look at teamviewer.com
> "Blue Max" <mailrichard@newsgroup> wrote in message
>> We seriously need help making a Remote Assistance connection. We have
>> some senior family members who really need our constant assistance, but
>> we cannot connect. Here is a little background:
>> FIRST, the connection is being made over the internet, with an invitation
>> and password, not within a local network.
>> SECOND, we can successfully make a Remote Desktop connection to each of
>> the computers involved. If we can successfully configure Remote Desktop,
>> then why not Remote Assistance, which uses some of the same
>> communications protocols?
>> THIRD, we can succesfully communicate with Windows Live Messenger.
>> However, if we choose the remote assistance option with the same contact,
>> we cannot connect. Ironically, the connection appears solid in that one
>> contact successfully sends a request and the other accepts the request,
>> but the connection always times out or fails. The dialog suggests that
>> the other user may have closed the Remote Assistance session, but they
>> have not.
>> FOURTH, could this be a subtle firewall issue since we can connect in so
>> many other similar ways, but not with Remote Assistance? Does MSRA.exe
>> have to be allowed through the third-party firewalls? It seems we have
>> even tried this before without much success. I imagine, if we have
>> allowed remote assistance in the 'Remote Settings' dialog, that the
>> Windows firewall is properly configured to run MSRA.exe, correct?
>> We would really appreciate some advanced help in resolving this problem!
>> Remote Assistance is promoted as the friendly lifeline for even the most
>> novice users. Yet, as an advanced user, we have only made one or two
>> successful connections over the last 4 years - not a real confidence
>> builder. If you have any advanced knowledge on configuring Remote
>> Assistance, we would welcome your help!