Why a dns error when the pcs can clearly find each other?

[tleave2000]

Hello,

I'm trying to get remote desktop assistance set up so someone in another city can help me out on my computer. The annoying thing is that I can remote desktop control his computer, but whenever I invite him to rdp control my pc via msn (or any other method) after he's accepted the request, it waits a while and then he gets a dns error.

I thought dns was used to change human readable names into ip addresses. But if his computer is communicating with my pc already, eg via msn, then the dns resolution system must be working (mustn't it?).

**So does anyone know why he might be getting a dns error?**

I've allowed rdp through my firewalls in case you were wondering. It seems to me that that must be working too else I wouldn't be able to rdp control his computer (or would I?).

When I run netstat -a, I can see that port mypcname:3389 is listening as it should but in the foreign address field it says mypcname:0 as if it's listening to itself on port zero, could this have something to do with the problem?

Sorry for being a bit of a n00b and all that : ). Hope someone can help, thanks for reading!

[Jay]

what happens if he simply trys to connect to your public IP with the RDP client?

[tleave2000]

Hm, that sounds like an interesting question. I'm not sure if he's tried that. So he'd just open Remote Desktop Connection app from start->programs, and then type in the ip address of my computer?

What about NAT and all that? Would he have to type the ip address of my router and then my computer's ip address on my local network or...? If you (or anyone else) could answer that question, it'd be great.

Thanks for your input so far : )

[spoon_]

You need to forward port 3389 from your LAN IP so its accessible externally i.e. when someone hits your WAN IP on certain port it get forwarded to the internal IP...

Best practice to avoid ppl hacking your system is to forward internally port 3389 to a different external port number... like 3389 to 89745 (chance that someone will hit 89745 and figure out that you've got RDP enabled is v. slim)

Start --> Run --> mstsc

Then use external+port to connect (External_IP:3389)

You've got to have local account (member of administrators group or remote desktop users) with password enabled btw. otherwise you won't be able to login...

[Zak33]

http://www.teamviewer.com/index.aspx

free for private use.

Doesn't need installing unless you want it in permanently.. just click the RUN option for one use.

then you both get given a screen with a number on... if YOU want access to THEM get them to tell you their number and their password on the eft box of their screen.. and you'll be in.

Voice comms, file transfer, chat box...

all for free for private use.

I lOVE it.. used it twice this week already for a mate and my mum

[spoon_]

Yep, TeamViewer is pretty good and secure as well

@OP

Anything you do just please don't use VNC as its full of holes and it can be hacked in 10 seconds lol

[Ben Rogers]

I was going to mention don't use VNC as this can be gotten into VERY easily with a hacked viewer that bypasses encryption..it is VERY unsecure.

At least RD needs a windows password to get in and obviously you cannot log in in Windows a password being enabled on the host machine. You could try instant house call:

http://www.instanthousecall.com/

with the above software you don't need to worry about any firewall issues or firewall in router rules etc its easy.