I get the message: 'Remote Assistance connection could not be established because the remote host name could not be resolved.' - What does that mean?
Search First! Then browse:
Categories |
Full Archive |
By Date |
Newsletter
Summary: One common problem connecting with Remote Assistance typically involves a router 'getting in the way'.
I get the message: 'Remote Assistance connection could not be established because the remote host name could not be resolved.' - What does that mean?
•
Essentially it just means that remote assistance didn't get a response from the target computer. The most likely cause in home scenarios is that there's a router in the way at the remote site. For Remote assistance to work, port 3389 must be forwarded on that router to the target computer's internal IP address.
Article C2027 - June 12, 2004
i get the message "Remote Assistance connection could not be established because the remote host name could not be resolved. What can i do to fix problem!! please HELP
Posted by: joe at December 31, 2007 1:50 PMThis page has good explanations for most of the ways Remote Assistance can go wrong (including port forwarding with NAT, connecting behind firewalls, through routers, etc), and solutions: http://www.petri.co.il/what's_remote_assistanc.htm
Posted by: Joe Marty at January 9, 2008 6:47 AMI have followed the information given by Steve in August 07. It did not work, posibly because I am using Vista as is the remote computer. Does anybody know how the format of the invitation Ticket varies between XP and Vista?
Posted by: Barry at March 30, 2008 3:09 AMremote desktop requires 3389 to be open, remote assistance works through upnp...idiots...
Posted by: your mom at August 1, 2008 9:12 PMLeo,
I am attempting Remote Assistance thru Windows Live Messenger - it's a simplified version of XP's method. The message I get is very similar:
DNS Name of the remote computer could not be established
Since all the transacting between PCs and the server happens in the background - how would I resolve this and make a successful connection?
I do have a router - but I've connected with one person with no problem - and then not with another.
Posted by: Robert at September 18, 2008 1:27 PMYou need to make sure you are using you're REAL IP Address, not the one assigned to you by you're router. Go to Whatismyip.com to get your real IP address, then try again. If the IP starts with 192 or 172, then thats is the router assigned IP and it will not work.
Posted by: Joe at December 9, 2008 9:39 AMFinally...all day working on this....but i finally figured it out..i think. While i've gone thru every other step listed on every website and forum out on the web...the trick that finally made this work for me was to ENABLE "TERMINAL SERVICES."
Posted by: claytonpaul at January 2, 2009 5:40 PMfrom a command prompt: services.msc
Under "SERVICES" find TERMINAL SERVICES, rt click it, properties and then choose STARTUP TYPE as AUTOMATIC and then START the service...this finally did it for me...hope this helps!! cpb
Use TeamViewer instead.
Posted by: autoken at May 11, 2009 9:43 AMThis neat little software beats Remote Assistance hands down !!!
The accepting computer has to allow remote access, under control panel, system, remote. Hope this helps. Also, if using vista, you can access an xp installed computer, but not the other way around.
Posted by: mike at May 16, 2009 10:23 AMOn my NAT connection sharing my client is not able to configure Remote Assistance connection .error is that Remote Assistance connection could not be established. try again
Posted by: rajesh at September 7, 2009 3:05 AM