Re: Remote Assistance Feature of XP
From: Richard Urban (richardurbanREMOVETHIS_at_hotmail.com)
Date: 08/31/04
- Next message: Jeffrey Randow (MVP): "Re: No Remote Desktop After SP2 Install"
- Previous message: PA Bear: "Re: Sign in failed: automation server can't create object"
- In reply to: Peter Sale: "Re: Remote Assistance Feature of XP"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 30 Aug 2004 21:41:55 -0400
I do remote assistance on my two grown sons computers whenever they request
it.
I'm game!
Remove the obvious from my e-mail address to contact me. We will set up for
a try (-:
-- Regards: Richard Urban aka Crusty (-: Old B@stard :-) "Peter Sale" <psale@adelphia.my-leg.net> wrote in message news:OfnsdWvjEHA.2412@TK2MSFTNGP15.phx.gbl... > Hi Bill, > You wrote: >>Check the contents of the invitation file itself. See whether it >>contains > the private IP address >behind the router, or the public IP address of the > router. My bet is for the former." > > I know the values for each of these IP addresses. Which address should > appear within the invitation file, the public or private address? > > You wrote: >>In a pinch, you can also test via Telnet: >> http://support.microsoft.com/?kbid=187628 >> >> There's probably a newer version of this article, but it gives the >> basics. >> Substitute your destination hosts IP address for "tserv" in the example. > > Again, which IP address, public or private should I substitute for the > destination host's IP address? > > In any case, the following command seemed to get through > telnet my_public_ip 3389 > while > telnet my_public_ip 3399 > failed, displaying following error message: > "Connecting to my_public_ip... Could not open connection to the host, on > port 3399: Connect failed." > Of course, I substituted my actual public IP address for the variable > "my_public_ip." > > I would love to "request Remote Assistance" from a willing party, who > knows > his/her Remote Assistance is working properly, just to confirm whether the > problem is in my PC or the Remote PC I'm attempting to connect to. Any > takers? > > -- > Regards, > > Peter Sale > Santa Monica, CA USA > To email me, just pull 'my-leg.' > > "Bill Sanderson" <Bill_Sanderson@msn.com.plugh.org> wrote in message > news:O2kTARngEHA.3932@TK2MSFTNGP10.phx.gbl... >> One good way to test whether you've managed the forwarding correctly, if > the >> destination machine is XP Professional, is to use Remote Desktop to test. >> This needs to be enabled on the destination host--it uses the same RDP >> protocol and the same default port, so its a good test. >> >> In a pinch, you can also test via Telnet: > > support.microsoft.com/?kbid=187628 >> >> There's probably a newer version of this article, but it gives the >> basics. >> Substitute your destination hosts IP address for "tserv" in the example. >> >> "Peter Sale" <psale@adelphia.my-leg.net> wrote in message >> news:%23iBXxcpfEHA.3520@TK2MSFTNGP10.phx.gbl... >> > What command (for example, IPCONFIG) can I enter, or what panel can I >> > navigate too that will tell me the identity of these two IP address? >> > "... the private IP address behind the router, or the public IP address > of >> > the router. ..." >> > >> > Once I know the identity of these two IP addresses, how can I >> > configure >> > my >> > D-Link and/or Linksys router to forward the 3389 port for the correct >> > IP >> > (private or public) address so that I can request remote assistance >> > from >> > my >> > PC even though it is behind an NAT router (D-Link DI-624)? >> > >> > Both my PC, and the distant PC I'm requesting Remote Assistance from >> > are >> > running Windows XP Pro. My PC is behind a D-Link DI-624 router, while > the >> > distant PC is behind a Linksys WRT54G Router. These are both wireless >> > routers. An attempt was made to configure both routers so that they > would >> > forward port 3389, although I'm not sure this has be done correctly. >> > That's >> > why I asked my first and second questions. One PC is running Windows >> > Messenger 4.7 or while the other is running 5.0. However, I don't >> > think >> > this is the problem because failure to "resolve host" occurred with >> > both >> > Windows Messengers 4.7-4.7 and 5.0-5.0. >> > >> > Lastly, I'm looking into www.portforward.com to attempt to confirm >> > these >> > two >> > routers are correctly configured to forward port 3389. >> > -- >> > Regards, >> > >> > Peter Sale >> > Santa Monica, CA USA >> > To email me, just pull 'my-leg.' >> > >> > "Bill Sanderson" wrote in message >> > news:uY1I5z7eEHA.2812@tk2msftngp13.phx.gbl... >> >> Check the contents of the invitation file itself. See whether it >> >> contains >> >> the private IP address behind the router, or the public IP address of > the >> >> router. My bet is for the former. >> >> >> >> You can edit the invite file to change this. I'm not sure whether >> > enabling >> >> UPnP functions on your machine and, perhaps, using Windows Messenger >> >> to >> > pass >> >> the invitation, will fix this. Here's a KB that describes the process >> >> involved: >> >> >> >> http://support.microsoft.com/default.aspx?scid=kb;EN-US;306298 >> > >> > >> >> > >
- Next message: Jeffrey Randow (MVP): "Re: No Remote Desktop After SP2 Install"
- Previous message: PA Bear: "Re: Sign in failed: automation server can't create object"
- In reply to: Peter Sale: "Re: Remote Assistance Feature of XP"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading
