Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Computing > Wireless Networking > Remote Assistance fails to connect, remote remote host name could not be resolved

Reply
Thread Tools

Remote Assistance fails to connect, remote remote host name could not be resolved

 
 
Peter Sale
Guest
Posts: n/a
 
      12-11-2004
I have two Windows XP Pro SP2 computers wirelessly connecting to the internet (Adelphia Powerlink) via a Belkin Pre-N wireless router (F5D8230-4, version 1000), and two wireless network cards. On my notebook I have a Belkin Pre-N wireless network card (F5D8010, version 1000) and on my PC I have some sort wireless PCI network card by Netgear. With only two exceptions, in all other ways that I can see, I enjoy a problem free, very fast (3000up/256 down) connection to the internet.

The two problems, possibly related, are
1. All my attempts to "request" Remote Assistance fail, displaying the following error message:
"Remote Assistance connection could not be established because the remote
host name could not be resolved. Please try again."

2. The appearance in the "System" log of the "Event Viewer" in "System Tools" of "Computer Management (Local)" {Right click My Computer and select "Manage"} displays following error message:
Error 12/11/2004 9:57:55 AM Dhcp None 1002 N/A POWERNOTEBOOK

When I double click on this error, the following explanation is displayed:
The IP address lease 192.168.23.32 for the Network Card with network address 001150203F1D has been denied by the DHCP server 0.0.0.0 (The DHCP Server sent a DHCPNACK message).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I feel my problem initiating a "Remote Assistance" session and this DHCP error message may be related. Perhaps if I can fix the DHCP error, then I will finally be able to get a Remote Assistance session running.

My wireless network is only used to share internet access between multiple computers, no file or printer sharing.
--
Regards,


Peter Sale
Santa Monica, CA USA
To email me, just pull 'my-leg.'

 
Reply With Quote
 
 
 
 
Robin Walker
Guest
Posts: n/a
 
      12-11-2004
Peter Sale <> wrote:

> 1. All my attempts to "request" Remote Assistance fail, displaying
> the following error message:
> "Remote Assistance connection could not be established because the
> remote host name could not be resolved. Please try again."


To request Remote Assisitance from behind a NAT router:

- the router must support UPnP, and UPnP support must be enabled;
- in Windows Firewall, the "UPnP Framework" exception must be enabled.

In the Belkin, enable UPnP on the Utilities page.

--
Robin Walker



 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
ASP.NET - Remote name could not be resolved Shiva Ramani ASP .Net 3 05-01-2008 08:40 PM
Please help - Remot name could not br resolved =?Utf-8?B?Um95?= ASP .Net 0 01-20-2006 08:56 PM
The remote name could not be resolved reda ASP .Net Web Services 1 09-28-2005 06:46 AM
System.Net.WebException: The underlying connection was closed: The remote name could not be resolved. Jeremy Ames ASP .Net Web Services 1 01-08-2004 10:28 PM
The remote name could not be resolved Mark Shaw ASP .Net Web Services 0 07-29-2003 09:09 PM



Advertisments
 



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57