Remote Desktop Setup

[Shoot2ill]

So I just recently got a pretty nifty job on my college campus working as an Academic Computing Help Desk assistant. I have a lot of free time just staring at a computer screen and have been trying to figure out how to connect to my computer at home. Right now I'm using a web-based application called "Log Me In", but it's a little funky. I'd like to be able to use the integrated Remote Desktop Connection program that comes with Windows.

I'm running XP SP2. I have a wireless router and my ISP is Verizon DSL. I'm pretty sure I've already forwarded port 3389 correctly to my router, but other than that I'm at a loss as what to do. Are there any other settings I need to change on the host computer?

I have no idea what information to enter in to the Remote Desktop connection window when I'm at work.

For instance, what do I enter for "Computer"? My IP? What IP? The one listed in ipconfig? No idea.

What about username/password and Domain?

Help would be greatly appreciated.

[Puggsley]

On the host computer you need to go to Control PanelSystem Properties>Remote, then tick the box to alllow remote desktop. (You must be running XP Pro - NOT Home). Make sure you user account has a password or this wont work.

If port forwarding is set up then all you need to do is enter your ip address. To find this go to this address on your host computer:

http://whatsmyip.org/

At the top of the page you will see your IP address, make a note of this, then go to the remote computer and try to login to your home PC.

Your username and password is the smae as your windows user account, and on a home network you should not need to worry about the domain.

[Shoot2ill]

Thank you very much. I will try this out the next time I get the chance.

[bibutteryboy]

The only problem you may encounter is I believe with DSL, you're IP will change from time to time.

[Skiver Veteran]

one way around the IP changing is to enable remote desktop, but then use a program called hamachi to create a vpn link between the two machines, once connected you can then use that for remote desktop using the IP hamachi gives you on the VPN

really simple to use and works fantastically :)

if you need any more info cont be afraid to ask but since your help desk im sure you can figure it out quite easily :p

[Turge]

To work around your IP changing, I would recommend using a free service such as NOIP.COM or DYNDNS.ORG

Once you setup an account, you download a client which can run as a service on your home PC. This client monitors your public IP and update your dns entry if the IP changes. This means that you will only need to use something like "myserver.noip.com" in the RDP client instead of entering your IP.

[Shoot2ill]

Cool thanks guys.

[Shoot2ill]

OK so I've done all the things you guys mentioned, still no luck. I can even ping my NO-IP domain from my work computer, but can't connect.

When I go to http://www.utorrent.com/testport.php?port=3389 it says that the port is not open, but I specifically opened it in my router settings.

I can't figure out what else might be stopping port 3389 from opening correctly. I've already tried disabling Windows Firewall, no luck.

Any more ideas? :blink:

Edit: Interestingly enough, when I select Status>LAN Devices in my router, the fields for IP Address, MAC Address, etc. are blank, as if the router wasn't recognizing any devices...

Edited April 10, 2007 by Shoot2ill

[Turge]

OK so I've done all the things you guys mentioned, still no luck. I can even ping my NO-IP domain from my work computer, but can't connect.

When I go to http://www.utorrent.com/testport.php?port=3389 it says that the port is not open, but I specifically opened it in my router settings.

I can't figure out what else might be stopping port 3389 from opening correctly. I've already tried disabling Windows Firewall, no luck.

Any more ideas? :blink:

Edit: Interestingly enough, when I select Status>LAN Devices in my router, the fields for IP Address, MAC Address, etc. are blank, as if the router wasn't recognizing any devices...

From the command prompt, type "netstat -a" and ensure port 3389 is listening:

TCP 0.0.0.0:3389 MAIN:0 LISTENING

when you do an ipconfig on that same machine, it should show you the IP address of the machine you're forwarding port 3389 to.

[Shoot2ill]

TCP laptop:3389(local) laptop:0(foreign) LISTENING

Should it have an actual IP instead of "laptop"?

And yes I have the correct IP forwarded in my router settings.

[Turge]

I take it you can RDP from a different machine on your network, assuming you have one?

Your ISP could always be blocking the port, although this would be a first. You can try changing the listening port for RDP to 443 for example by following this guide: http://support.microsoft.com/kb/306759

You could then connect using your machine.noip.com:443 once you forward port 443 on your router.

[Menge]

yes you should have the ip on the router. i have never seen a router recognize WINS names

[Jeston Veteran]

Not sure why this hasn't been mentioned yet, but are you using XP Home or Pro? You can only Remote Desktop into a computer with XP Pro installed.

[Shoot2ill]

I take it you can RDP from a different machine on your network, assuming you have one?

Your ISP could always be blocking the port, although this would be a first. You can try changing the listening port for RDP to 443 for example by following this guide: http://support.microsoft.com/kb/306759

You could then connect using your machine.noip.com:443 once you forward port 443 on your router.

Yea but my problem is I can't forward ports correctly, so it wouldn't even matter if I changed my RDP port.

So it's weird that it says "laptop"? Is there a way to fix that?

[aakash_007]

have you gone to system properties and Remote tab there ? and set xp to allow RDP and select users .

[Angel Blue01]

I'm in the same situation.

"Lab assistant" here too :p.

I have XP Pro, can Remote Desktop in from other computers on the network, forwaded the default port on my router, checked Windows Firewall, and I still can't connect via my IP address!

[Shoot2ill]

Right, I have done all those things. I even have NO-IP installed so as to merge my dynamic IP with a static domain name, which I can ping to.

Like I said, it looks like my main problem is that my ports aren't forwarding correctly. This includes other ports besides 3389.

I have a Westell 327w Wireless Router/Modem that Verizon provided me if anyone can relate. :wacko:

[Turge]

Like I said, it looks like my main problem is that my ports aren't forwarding correctly. This includes other ports besides 3389.

Not sure why you left this out before, but this is obviousdly important information.

Check out http://www.PortForward.com for a step by step guide on forwarding the ports.

For example, if you have the Versalink 327W and want to forward port 3389, check out this page: http://www.portforward.com/english/routers...ote_Desktop.htm

[Shoot2ill]

Not sure why you left this out before, but this is obviousdly important information.

Check out http://www.PortForward.com for a step by step guide on forwarding the ports.

For example, if you have the Versalink 327W and want to forward port 3389, check out this page: http://www.portforward.com/english/routers...ote_Desktop.htm

Yea I've done that. And I've forwarded ports in the past successfully, but when I go to any web site that can confirm if a port is opened or not, it comes back saying the port is NOT open.

So to recap:

Enable Remote Desktop in System Properties - CHECK

Add exception/disable Windows Firewall - CHECK

Forward port 3389 to router - CHECK

And 3389 isn't the only one not working, I've tried several others.

So the issue is no longer a RD issue, but an opening ports issue.

Someone please let me know if I'm missing something... :|

Edited April 11, 2007 by Shoot2ill

[TurboTuna]

Do you have any other network devices before/after your router? Any firewall software?

[raskren]

Does the target machine have a dynamic local IP address?

[Shoot2ill]

No, this is the only machine connected to the router.

The IP address of the router is 192.169.1.1 by default, and the IP for the machine that shows up when I type IPCONFIG in command prompt is 192.168.1.47. I don't know if you'd consider that a "dynamic local IP address" or not, I don't know what the difference is.

The only firewall app. I have is Windows Firewall. I have tried adding port 3389 etc. as an exception AS WELL AS disabling the firewall itself.

If someone could show me real quick how to post SS's, I'd show you the router gui as well as the information provided in command prompt, etc.

P.S. The only app. I've installed that DID have a firewall was the ESET Security Center Beta, which I've already uninstalled.

[TurboTuna]

What router do you have? Is that the only internet device you have?

[+BudMan MVC]

As TT has asked twice already - and I'll make it 3 -- You have NO other devices other than the Westell 327w, no other routers?? No VOIP type device?

Goes from the cable from the wall to your Westell 327w to your PC.. And the IP address on the Internet side of your Westell is a public IP, ie its not 192.168, or 172.16 or 10.x is it??

If this is the only device on your network - and you have setup the forwards correctly.. Ie to yoru IP 192.168.1.47, you sure this did not change from when you did the forwards... You did not setup some IP to be in the DMZ of the Westell 327w did you? Quite often once you setup an IP to be in the DMZ.. the router will not longer forward other ports to other IPs.. Ie if you put 192.168.1.100 in the dmz, even if does not exist.. you might not get any forwards.

if all that is correct - then you must have some software blocking it on your computer then. I would suggest you turn off the firewall service, atleast for testing.

[Shoot2ill]

As TT has asked twice already - and I'll make it 3 -- You have NO other devices other than the Westell 327w, no other routers?? No VOIP type device?

Goes from the cable from the wall to your Westell 327w to your PC.. And the IP address on the Internet side of your Westell is a public IP, ie its not 192.168, or 172.16 or 10.x is it??

If this is the only device on your network - and you have setup the forwards correctly.. Ie to yoru IP 192.168.1.47, you sure this did not change from when you did the forwards... You did not setup some IP to be in the DMZ of the Westell 327w did you? Quite often once you setup an IP to be in the DMZ.. the router will not longer forward other ports to other IPs.. Ie if you put 192.168.1.100 in the dmz, even if does not exist.. you might not get any forwards.

if all that is correct - then you must have some software blocking it on your computer then. I would suggest you turn off the firewall service, atleast for testing.

No other devices, no other routers, no VOIP type device.

And what exactly is the "DMZ" of my router? What is that and what does it stand for. I've reset the router to its factory defaults several times. Would this DMZ still exist after a reset?

And as I've already stated, I can log on to my computer through the LogMeIn service. So some ports must be forwarding properly...right?