Remote Assistance Troubleshooting

F

FrankW

Of all the Vista technologies, Remote Assitance (RA) SHOULD be one of the
Vista technologies which is so simple to use and troubleshoot that even my
Gandmother can use it. In fact, I have 2 Grandmothers, a Father, and a
Stepfather who would benefit greatly from RA and who are all quite computer
illterate. Microsoft's ability to offer them a vomputer which even they can
use has always been one of Microsoft's strong points. However, Of all the
people in my family who I have TRIED to help with RA, only one of them has
been successful.

In every other case (5 people who I've tried to help remotely), the exact
same thing happens ...
1. I ask them to send me a RA request using Live Messenger. This is one of
the areas I give Microsoft big points. It's soooo much easier in Vista.
It's been easy in Live Messenger/MSN Messenger for a while but now it's easy
in Vista using "Help and Support".
2. I accept and they create a password for our session. Also, another good
improvement over previous versions. In most of these cases I'm citing, we're
Vista to Vista.
3. Here's where it all falls apart. On their end it is waiting for a
connection. On my end, the RA software runs and attempts to connect. But it
fails to connect and suggests that they may have closed RA.

Now, every one of them has either Cable or DSL internet service and a single
router. They are all wired directly to their router and their router wired
directly to their cable/dsl modem. Very simpel setup. But as far as I can
tell, Microsoft provides me no way whatsoever to determine the problem.
Their router could be blocking the necessary inbound port. Their Windows
firewall could be blocking the app or the port. The really sad thing is that
I have a freeware app that I downloaded for file sharing and it also needs
inbound traffic and it has far better analysis capabilities than Vista's RA.
It will tell me whether or not my Windows Firewall is blocking and it will
tell me if the port is open all the way through, or justopen on my router, or
blocked. That's the most basic of troubleshooting and RA should absoletely
have it.

Think about it. I'm the person they're coming to for support, so you can
assume that I at least know something about computers. When they connection
fails on my end and times out on their end, why not give them the option of
automatically troubleshooting? You could have it check their Windows
Firewall, check to see if the required port is open, check to see if the
required port is open on their router. then you could present them with a
diagnostic report and offer them the ability to send it to me through the
same channel they sent me the RA ticket. The report would contain their
public and private IP addresses so that I could run some additional tests,
which I would do manaully. But at least I would know where to look. And if
the problem was found on their end in the Windows firewall, then RA should
offer to fix it immediately and try again.

But none of that is there. So what happens is I spend 3 - 4 hours helping
someone who doesn't really know what system tray is, how to find a menu, or
what I mean when I say "now minimize that application." I spend an insane
amount of time helping them locate a single file on their hard drive because
they don't understand how to use Windows Explorer comfortably. And all of
this because I have no good built-in option for helping them.

Of course, I'm not that stupid. My company uses Live Meeting and I usualy
resort to that instead of RA. But it just makes me angry every time I try to
use it falls down on the same simple problem. I have also fixed some of
their routers but then the inevitable "reset your router" request comes at
some point from their local ISP and blows that all away. Anyway, I
absolutely see it as Microsoft's responsibiilty to ensure that a technology
designed to be used by someone so helpless for the specific purpuse of
seeking help be designed well enough to give them a fighting chance of
getting that help. I just don't see that here. So please fix it.

Thanks,
Frank

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/communitie...0c0&dg=microsoft.public.windows.vista.general
 
P

Peter

Absolutely Agree. I am absolutely unable to give help through RA. Rather I
have to use teamviewer or another soft, which work 100% perfect.

I was able to run RA only on local network. I tried to help through internet
twice and 100% unsucessfull!!! So finaly I connected through teamviewer to
see if there is not some firewall problem, finally shut down all firewals and
the result? "Can't connect" :) really funny. UPnP on both routers enabled.
And port forwarding? Forgot about that. How I will explain to people who
wants help to open the ports on router :) ha ha ha
 
J

JamesHH

I was having the exact same problem, with both sides using a wireless router.

The solution was to turn off "Block Anonymous Internet Requests" in the
router security setting. This was necessary to receive (but not to send)
assistance.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top