- 12-03-2012, 08:17 AM #1
I wanted to see if I could remote into my home desktop computer from my surface RT. I have allow remote access enabled on my desktop (computer properties, remote, checked enable) and I know my full computer name as per the original properties window.. I am on the same home network on both (since my desktop is also on wireless) but when I try to connect with the desktop version on the RT it just says it can't connect and either the computer is off or not available. I tried googling it but i can't seem to follow all of the steps as sometimes they tell me to select users or this or that and i don't have those options available to me. If someone would be willing to walk me through the steps or point me in a better direction I would appreciate it.
- 12-03-2012, 10:14 AM #2
1. Go to your router setting page.
2. Find the "Attached devices" section. This name is on a netgear router. If you router is of different brand, the naming can be a little different.
3. Look for the IP address associated with your desktop. It looks something like 192.168.1.x with a netgear router.
After you got the local IP address, just type it directly in remote desktop connection and that should be it.
- 12-03-2012, 12:22 PM #3
I am also having issues getting RDP to work on my surface.
If anyone can help me get remote desktop working on my surface it would be greatly appreciated. If a developer out there could set up an app to get this done easier, could be a moneymaker, I know id pay for it.
After scouring youtube, and the web, I found a lot of different walkthroughs on how to set up a home pc as a remote server. Unfortunately, I really don't know what im doing and cant figure out why it isn't working. Im running WinXP Pro SP3 on a few year old laptop (I bought the thing during the Vista debacle, and down graded to xp for software reasons - I am an architect and needed my AutoCAD and various graphic intensive programs)
These are the steps that I have tried, all to no avail
- I go to control panel, System, Remote, turn on Remote Desktop.
- open Linksys router configuration, and try to set up Port Forwarding
- this is where it really gets confusing for me, and I don't think that I am doing it correct. I know I need to open the port, I go to Applications and Gaming, and enter RDP, Im not sure of the port number, and what else to do here
- cmd, ipconfig - I enter all information - ip address, DNS, Gateway, etc?
I then found out that in order to really get this working, I needed a static IP address - Im not sure how to do this, but I found a couple posts, and a youtube video suggesting using DynDNS to get this working as a host. I signed up, and am still not able to connect.
Any help would be appreciated - Im not great with this stuff.....I never really played with networking, before....Please help me get my Surface working. Its possible im not entering the address correctly in the Surface Remote Desktop App. Which IP address do i enter - the web based, the one from my router, or whats listed in ipconfig? I think this might be what i am doing wrong.
- 12-03-2012, 12:49 PM #4
- 12-03-2012, 01:49 PM #5
First see this video.
-The first step as shown in the video is to find out the local IP address of your desktop, which is the address the router uses to identify each devices in the home network. It has the form 192.168.1.x (see the video).
- The the second step as shown in the video is to go Applications and Gaming then Port Range forwarding. The first field you can enter any name, just so you know what it is later. Then enter 3389 for both "start" and "end". Keep "both" for "protocol". Then IP address is the local IP address you find in step 1. Check "enable" of course. Then "save settings"
- No, you dont necessarily need DynSys for RDC to work. The only thing you need to know is the IP address of your network at the time you want to connect. To do so, go to whatismyip.com and copy that IP address to the RDC client on your surface. Test it and it should work.
- Once you have confirmed that RDC works, you can test out DynSys. The idea of Dynsys is to run a program in background on your desktop, and this program will report to DynSys any change in the IP address of your network. This way, you will always know the current IP address.
- 12-03-2012, 05:07 PM #6
- 12-03-2012, 05:31 PM #7
- 12-03-2012, 05:50 PM #8
ii ran the ping and it did work. and yes the router/modem was provided by the ISP (which in this case is brighthouse).
i downloaded the telnet app (trial version) and connected to 188.8.131.52:3389 and got a connection error, failed to respond.
I am on hold with the ISP now to see if i can get the username / password since im 99.9% sure it's still the default information and i don't have it written down anywhere. (regardless of if i need it for this, i probably should have that handy..) Thanks for the help so far! :)
12-03-2012, 06:00 PM #9
- 23 Posts
- 0 Post(s)
- 0 Thread(s)
I had real trouble getting it to work too. I bought Win 8 Pro on the 24.99 offer especially. In the end I cleared Workgroup settings from all machines and basically went back to basics. Even so, behaviour was odd. Sometimes I could ping the other two machines, sometimes not. Same between them. Sometimes they would show up under Network and other times not. Eventually they could all see each other and I was able to RDP to the Win 8 Pro machine. But I just tried again and this time it failed. Doesn't see it using the saved settings in the Metro RDP app. No idea. Will have another crack tomorrow.
- 12-03-2012, 06:09 PM #10
Ive had issues after updates, of things like file sharing and such not connecting. I know on the last update I had to recreate file shares I had on the RT to get access to them again.
Narv, on the main PC, open a command prompt and type: netstat -ano > C:\Ports.txt
This should list off the ports listening in at text file, open it and search for 3389.
I only use the Metro RDP but havent had any issues, I even RDP to an ubuntu server running xRDP from the RT.
- 12-03-2012, 06:10 PM #11
- 12-03-2012, 06:23 PM #12
Well i seem to have found the problem.. I feel kind of stupid but apparently my version of windows doesn't support remote desktop... Didn't catch that gem earlier it seems.. hmm... well thanks anyway guys! if i decide to upgrade it seems like a pretty straight forward task now, heh.
Are there any other options i could use that would work the same? I know there are many options but idk if they would work with the surface RT.
- 12-03-2012, 06:28 PM #13
- 12-03-2012, 09:25 PM #15
- 12-04-2012, 12:44 AM #16
So - good news - I got remote desktop to work - the desktop version. However, the "Metro" version will not connect when i type the exact same ip address, it tells me "Can't connect to the remote PC There seems to be a problem with the remote PC. Contact technical support or ask your network administrator for help" ..........not sure why - maybe because im connecting to XP.
Now, for some reason, every time i try to enter static IP address, it disconnects my internet connection, and the only way for me to get it back is to restart my modem, and router. I think I am entering the numbers wrong.
Is DynDNS an alternative solution for setting up static ip on router. If so, I'd rather not have to use third party. My goal, is to be able to remote into my computer from wherever, whenever i want. Can anyone who knows what they are doing help me with this. Surface connects fine on home network, but will not out of network.
- 12-04-2012, 03:01 PM #17
-You can connect locally with the local IP to Windows XP
-You are trying via the External IP of your router but it fails.
**DynDNS is a service which allows you to use a friendly name for the address (So www.google.com instead of xxx.xxx.xxx.xxx) As well if you IP changes (As alot of Internet Services do to residential customers) it updates it so you can always access it via the name.
- 12-05-2012, 09:36 AM #18
Any advise would be greatly appreciated.
- 12-05-2012, 10:58 AM #19
Aha, thats why you lose internet.
You cant change your public IP, its given to you by your ISP (you can pay a little more usually to get them to assign you one, that way it never changes) you need to reference it when you are outside your house.
So find out what the Router is using already, then use that in the remote dekstop client to connect.
Example: Your at your friends place. His router gives you a 192.168.0.12 address, you want to connect home, the IP your router has (The public one) is 184.108.40.206.
You dont need to change any IP's, just use 220.127.116.11 as the address in your remote desktop client.
- 12-05-2012, 01:07 PM #21
The only issue i am seeing is - if the ip address is not static (ie, if it can be changed by my ISP), if i am trying to work remotely from outside my network, how do i know the public ip address of my home computer/server from my remote location? Wont this change if not set to static? Is this where DynDNS comes in - it is dynamic, as in it always connects to the computer running the DynDNS plugin?
- 12-05-2012, 01:33 PM #22
- 12-05-2012, 01:49 PM #23
I did a 14 day free trial with DynDNS, but would definitely prefer to not pay them 20$ for the year if there is a free alternative out there. Do you have experience with No-IP.com - Managed DNS - Free Dynamic DNS - Managed Email - 100% Uptime Guaranteed, are they giving me the same service as DynDNS?.........im not hosting anything other than remote access, i assume this is really all i need - something to track my IP so that i can connect all the time.
- 12-05-2012, 03:00 PM #24
- 12-05-2012, 05:56 PM #25
I personally use DynDns and have never had issues. I havent heard bad things about no-ip either though. At the end of the day, its just a connection that gets kept alive and when the ip changes, dyndns/no-ip updates it. Cant really do it wrong lol.
DSL/Fake Fiber changes alot from what I know, Cable/Broadband usually have longer lease life (time before the IP gets re-issued)
If your looking for a new Router, alot of them come with dyndns hook-ins (You get a free account, I think dlink is NAME.dlinkddns.com, etc)
- By laney182 in forum Nokia Lumia 920Replies: 10Last Post: 06-18-2013, 06:38 AM
- By Winfonejunkie in forum Microsoft Surface for Windows RTReplies: 10Last Post: 12-03-2012, 01:49 PM
- By Evin Kaless in forum Windows Phone 7Replies: 1Last Post: 02-16-2012, 05:24 PM