So, it only took me about 50 million trial-and-errors, but finally I got Remote Assistance via email to work successfully between two WinXP users who are both behind routers/firewalls.
Just in case anyone needs it (because once you can get it working, it’s REALLY neat, mind-bogglingly useful, and surprisingly fast), here are the required steps.
1. Fat-fingering of some sort occurs.*
*: Now, this isn’t *totally* required, of course. You may be the type of person that just enjoys having people come and play with your computer, but for the most part, usually some sort of breakage happens before someone else feels the need to come in and fix it for you.
2. The end-user MUST make sure the following two buttons have check marks next to them:
Right-click My Computer and scroll to Properties.
Click the Remote tab.
Make sure “Allow Remote Assistance Invitations to be sent from this computer” is checked.
Click Advanced.
Make sure “Allow this computer to be controlled remotely” is checked.
3. The end user, if using a router, must set up port forwarding.
The end user must log into their router’s web-based administration panel* and enable Port forwarding for the Remote Assistance request:
Port 3389 should be routed to the internal IP address of the end users system, ie. 192.168.x.x.
The end user can perform the following steps to find out what their internal IP address is if they don’t know:
Go to Start->Run
At the command prompt, type cmd.
Type ipconfig and hit enter.
Write down what is written on the IP Address line.
*: most router models have online instructions on their respective manufacturer’s website as how to login via browser and find the Port Fowarding section. I mean, who keeps instruction manuals after the initial setup? Okay, guilty as charged. But it’s still quicker to go online and get it anyway.
4. The end-user must send a Remote Assistance invitation via email.
Go to Start->Help and Support.
Click on Remote Assistance.
Click Invite someone to help you.
Type the Invitee’s email address, and click Invite this person.
Send a message if necessary* and click Continue.
Enter a password if necessary, and communicate that password with the invitee.
Click Send Invitation.
The email will pop open in the default email program (such as Lotus Notes), and the end user still needs to hit the Send button.
*: Since you are, in fact, asking someone to help you, it might be nice to take this time to ask them how they are? If they’ve read any good books lately? Have they done anything fun lately? If they are the geek type like I am, the answer will most likely still be no, but hey, it was nice that someone thought to ask anyway.
5. The Invitee gets the external IP address/hostname from the end-user.
The end user can visit the following sites and easily tell you that information:
http://www.whatsmyipaddress.com
http://www.whatismyhostname.com
6. The Invitee receives the email invitation, and tweaks the contents.
Once the invitee gets the email, save the attachment to the desktop.
Open it with Notepad.
There will be two entries one after another of the end user’s internal IP address followed by the port, ie:
<UPLOADDATA USERNAME=”Jess” RCTICKET=”65538,1,192.168.10.3:3389;192.168.10.3:3389;D40S4F21:3389,*,etc.
The first entry needs to be changed to the external IP address, and the second entry needs to be changed to the hostname of the end user, leaving you with this:
%LTUPLOADDATA USERNAME=”Jess” RCTICKET=”65538,1,209.67.3.105:3389;my.hostname.isp.com:3389;D40S4F21:3389,*,etc.
7. Save the invitation, and NOW you are ready to click it*.
*If it hasn’t expired already from all this preparation.
After that, the Port Forwarding can be disabled/re-enabled as fat-fingering occurs. Or unless you like that sort of thing (see 1).
PS. That site does not belong to me. Don’t know what I’m talking about? You’ll figure it out eventually.