Error message when trying to connect remotely

[aclmilelr1215]

both Computers have XP. Comp A saves invitation, attaches it into an email,
sends it to Comp B. Computer B, downloads and opens attachment says yes to
connect to Comp A now and the following error pops up:



A Remote Assistance connection could not be established because the DNS name
of the remote computer could not be resolved.

I don't know what to do! I have check configuration and everything is
selected to allow remote access on both computers. It says nothing to Comp A
when B tries to connect. I have tried and succeeded between my desktop and
laptop, so I know that Comp B is able to use remote assistant properly.
Please help!!

A Remote Assistance connection could not be established because the DNS name
of the remote computer could not be resolved.

 

[Shenan Stanley]

both Computers have XP. Comp A saves invitation, attaches it into
an email, sends it to Comp B. Computer B, downloads and opens
attachment says yes to connect to Comp A now and the following
error pops up:

A Remote Assistance connection could not be established because the
DNS name of the remote computer could not be resolved.

I don't know what to do! I have check configuration and everything
is selected to allow remote access on both computers. It says
nothing to Comp A when B tries to connect. I have tried and
succeeded between my desktop and laptop, so I know that Comp B is
able to use remote assistant properly. Please help!!

A Remote Assistance connection could not be established because the
DNS name of the remote computer could not be resolved.

Either or both machines behind an internet router? Some sort of NAT device?
Like a netgear, linksys, dlink, etc? Something that allows one to use a
single internet connection with multiple computers because it gives out
private IP addresses like 192.168.x.x - thus acting like a network
translation/dhcp server device and which may be blocking your attempt to
connect?

 

[Sigmundur Jonsson]

It won't work because only the internal IP address and HOSTNAME is saved
in that file. Try using it through MSN or just use other types of remote
control like the normal RDP or some VNC programs.

 

[whobeboo]

I repectfuly disagree. If Remote Assistance did not work from behind a NAT firewall, it would be practically useless. I don't know for certain, but I would assume that when you create a Remote Assistance call, you are establishing a "session" on a Microsoft server. When the person responding to the Remote Assistance request begins to assist, their computer probably contacts the Microsoft server, provides some credentials for the session, then the Microsoft Server introduces the Helper to the Helpee's computer. Again, it's just a guess, but I can't see any other way that MS could have designed this service because most of the PCs in the world live behind firewalls. If I'm right about all of this, it could be that the DNS problem is actually a problem contacting the Microsoft Server. It does not make any sense that a DNS lookup is required to access someone's PC. Most likely they have not registered a domain to point to their IP address, and most likely they do not have a fixed IP address anyway. The MS server on the other hand, would have a fixed IP address and a domain name, and establishing a Remote Assistance call would require a DNS lookup. As of right now, my best guess is the there is a problem resolving the IP address of the MS server, hopefully someone will either reboot the server because it's down or fix the DNS to point to the correct IP address.

Having said all of that, I am having this same problem too and I can't find an answer anywhere else on the web. So if anyone knows the answer to this, please post it because it doesn't seem to show up in my Google searches.