Re: confused on how to set up remote assistance

just to add. i added the DNS entries on the XP PRO pc because AT&T was adding
a 69.DNS entry as the primary EVEN AFTER i hardcoded the OPENDNS.ORG entries
in the router DNS values. after i added the DNS on the PRO pc then IPCONFIG
showed that indeed the OPENDNS.ORG servers were now being used as directed
and desired.

"Shenan Stanley" wrote:

basschakra wrote:
i'm getting the 'could not resolve DNS on remote computer' (close
verbage). i
am trying to test sending and receiving a remote assistance request within
the pc's in my home.

here's my setup...

1) requesting pc on XP Home SP2, receiving request is pc on XP Pro SP3
2) no problem creating the request via email
3) no problem receiving the req
4) all my pc's sit behind Linksys router
5) tried forwarding port 3389 for both pc's in router
6) viewed 'invitation' in notepad to check IP addresses
7) enabled all (i think) services and Firewall exceptions
8) no matter what changes i tried this is the message ALWAYS rec'd...
A Remote Assistance connection could not be established because the DNS
name
of the remote computer could not be resolved

i have also tried Remote Desktop to no avail also from the XP Pro pc to
the
Home pc. i would truly appreciate if someone could turn on the lights for
me!!! ;-) thanks much...

Sooner Al [MVP] wrote:
Over a local LAN use the file method for the invitation for RA.
This may help...

http://theillustratednetwork.mvps.org/RemoteAssistance/RemoteAssistance.html

TeamViewer also can be used IP to IP over a local LAN. Run
TeamViewer on the PC, the so called Novice PC (RA parlance), you
want to remotely control and go to "Extras > Options > General" and
check the "Accept incoming LAN connections" checkbox at the bottom.
If you want that PC to only accept LAN connections (and not
connections from the public internet) go to the "Advanced" tab and
check the "LAN connections only" checkbox. Call the PC by its LAN
IP from the so called Expert PC (RA parlance).

FYI, you can *NOT* use Remote Desktop to remotely access/control a
XP Home PC. You can use Remote Desktop to remotely access/control a
XP Pro/MCE PC.

http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTroubleshooting.html

basschakra wrote:
Al, thanks for the post and fyi.

at this point, i'm thinking that the fact i have both of pc's
sitting behind the same router is what is creating the problem.
even tho each pc has its' own ip address the router has one ip
address and i think that is my point on contention. but as
witnessed by the success of TeamViewer software i know there has to
be a way to succesfully test RA within my home config. i think
there might have to be a mod in the RA incident ticket or something
i'm still not doing correctly in my router setup.

Still trying tho...

Sooner Al [MVP] wrote:
When I use the procedure from the page I pointed you to on my
wife's XP Pro desktop the resulting invitation file looks like this.

<?xml version="1.0" encoding="Unicode" ?><UPLOADINFO
TYPE="Escalated"><UPLOADDATA USERNAME="Linda"
RCTICKET="65538,1,192.168.1.33:3389;norman:3389,*,TQp+Od3cqZlhJaESr/8eOx5jVAzSEvoh6sq9ylmx2G4=,*,*,fK9Nyod0pGddhbKpl5MD82MnerQ="
RCTICKETENCRYPTED="0" DtStart="1239449414" DtLength="60"
PassStub="" L="0" /></UPLOADINFO>

The RCTICKET field contains the LAN IP address of her PC (the
Novice) that is used by my RA client (the Expert) to call. So if
the RCTICKET field does not contain the corrrect IP you can modify
it manually. See this for more information about the invitation
file format.

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q300692

In my case both the expert and novice PCs are behind my NAT router.
http://tinyurl.com/CurrentHomeLAN

basschakra wrote:
thanks again Al. yeah the only difference that i see in your tix
from mine is that you do not have a 'single' IP address for your
router followed by the unique IP address from that particular PC.
so i wonder why that is when we both share similiarly designed home
networks. the only other thing that comes to mine is i'm using
OPENDNS.ORG as my static DNS 1 and 2.

question...if you got to www.whatismyip.com do you get the exact
same address for each of the PC's behind your router? this is what
i get and this is also the first IP address listed in my RA ticket
followed by the unique address and then the unique name of the pc
(as i posted earlier).

i'm really curious as to why our RA tix are different? thanks...

Shenan Stanley wrote:
You would see the external IP address of the router for every
machine sharing that Internet connection through that router.

basschakra wrote:
exactly. so why is this external/router address included in my RA
tix and not Al's?

Sooner Al clearly stated both machines (in the given example) were behind
the NAT router. ;-)

An old post of Sooner Al's...
http://groups.google.com/group/microsoft.public.windowsxp.work_remotely/browse_frm/thread/740b8e9586f4f8b9

You are editing the invitation so it contains the private LAN IP, correct?
And your DNS for each computer is automatic (or set to) the NAT router?
(I see the second is not true.)

Set the DNS on the NAT router (if you must) and pass all the machines to it
for DNS searches.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html



.

Relevant Pages

  • Re: Session terminated
    ... There is not as far as I know a site available to facilitate the connection, but you can still do it with an IP address. ... The IP Address is your PC, the Gateway is your router. ... All of the docs I have specifically state that XP Pro and XP home can use remote assistance. ... This link states that the Home versions and Pro versions cannot use RA between them, which means you can only have home assisting home, or pro to pro. ...
    (microsoft.public.windows.mediacenter)
  • Re: Redirect to VPN tunnel?
    ... The first point that comes to mind is that the remote machines need the SBS as DNS and also WINS server. ... You should be able to configure the DHCP server in the remote router to give out the SBS address as DNS server. ...
    (microsoft.public.windows.server.sbs)
  • Re: lets start at the beginning...
    ... Remote Desktop implements Terminal Services in XP Pro... ... >>>>I have a router which is connected to DSL. ... >>>> third computer is at home and uses a cable connection to ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: external wireless connection to SBS
    ... third octet to 16 on your inside NIC as point all DNS to your server's ... > Gateway points to router 192.168.0.1 ... I am able to connect to the wireless access ... > connect to Exchange as if I was in a Remote location. ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Desktop Stopped Working
    ... Well as far as the hack for Vista Home Premium is concerned I suggest you check with the folks that provided that hack for help. ... If you can't connect from a local PC on the same LAN using the XP Pro machines private LAN IP you will never connect from a remote site. ... When trying to connect from a remote location make sure TCP Port 3389 is forwarded through the Linksys router to the XP Pro machines private static LAN IP address. ...
    (microsoft.public.windows.vista.networking_sharing)
Loading