So, I was sitting using my Win7 Home laptop, and I was wondering...can I remote desktop into my Win7 Ultimate desktop at home at my discretion? I did some Googling and found out the remote desktop software doesn't exist in Win7 home. So, I'm assuming I'm going to have to resort to third party software. Any suggestions? I mean, it'd be neat to be able to go into my desktop from my laptop anywhere I am. I'm sure there's a way.
-
jackluo923 Notebook Virtuoso
I think you got your fact wrong. I use remote desktop on my netbook to stream 720P movies from my desktop computer without lag along with superb sound.
-
To the OP you should try LogMeIn. -
Home premium don't RDP mate
but win7 ultimate do
type this in start menu search bar or in Run windows
Code:mstsc
-
Oh, that works. I was able to connect while on the LAN. IF I'm behind a router though at home, how do I connect from wireless hotspots to my desktop at home?
-
Are you talking about doing this with LogMeIn or RDesktop?
-
Port forwarding and know your external IP address
everything you need to know except for the specifics on your router
http://www.sevenforums.com/tutorials/3922-remote-desktop-connection-rdc-network.html
giant website for setting up port forwarding on almost any router
http://www.portforward.com/ -
All the Win7 versions have Remote Desktop Client, that can connect to other computers. From Pro upwards also Remote Desktop Server is included, so those can be used remotely.
So in this OP's case, he can connect from 7 Basic (client) to 7 Ultimate (server) but not the other way round. -
You can only connect to (host) Pro and Ultimate versions. Any version can be used to connect from (client).
-
Trying to get the port forwarding setup right. I tried setting it up to port 50000, but it wouldn't connect. I setup the port forwarding to 3389 and reset the portnumber for RDP to 3389, and I was able to connect with the LAN IP and internet IP addresses. This is a little funky.
-
it is because you were on YOUR lan, try someone elses internet connection
-
The port has to be 3389, unless you specifically change it.
That's why when you port forwarded to 5000, RDP didn't work, because the RDP service, by default, only listens in to 3389. Changing the rule in Windows Firewall will not change the listening port that the RDP service listens to, rather it just opens that port in the firewall.
To change the listening port on the host computer, you gotta do a registry change.
http://support.microsoft.com/default.aspx?scid=kb;en-us;306759
Then log onto the host computer by typing, from the client computer, ComputerName : PortNumber -
I did the registry change and it still didn't work. Maybe I should try a diff port than 50000. I just wanted to use something other than the default RDP port.
-
Sometime back I tried the Registry hack as well to change the default 3389 port for RDP but like you I never had any luck with it. So, I just use the default. I think that change would be good security wise though!
-
I have old Linksys WRT54G with DD-WRT installed, I use the OpenVPN version. I can securely connect to my home network, no need to make any open holes in my firewall
-
Well as I was suggesting to the OP in post# 3, LogMeIn gets the job done as well. And you don't need to worry about forwarding ports or all that mess. Just log in and connect.
-
-
I can't seem to get a port other than 3389 to work, even with the registry change. This is frustrating.
Remote desktop Win7 Ultimate -> Home
Discussion in 'Windows OS and Software' started by raz1337, Nov 18, 2009.