Installing remote desktop vista home premium
Quick access. Search related threads. Remove From My Forums. Asked by:. Archived Forums. Windows Home Server. Sign in to vote. I recently deployed a windows home server clap clap clap and am beginning to play and have some fun. I think it is not supported but why? So now I have two admin accounts in vista. Bottomline is we both use the same pc simultaneously, one locally and other remotely.
Since both the accounts are admin accounts there is no problem of accessing drives, folders and programs. If you need any other info let me know. MPG What happens when you attempt to create a new session using an account that already has a session depends on the value of that key.
If the value of fSinglesessionperuser is zero a new session is created every time so multiple sessions using one username can exist.
The downside is you cannot take over an existing session. If the value of the key is zero and you switch user from your current user session to a different one instead of logging out, there is no way of switching back to your original session. If you try to, a new session will created instead. How does one get an RDP connection to just the second monitor ie not the primary, not both spanned into one?
What I said above is not correct. If fsingelsession is set to 1 and there already is a session, disconnected or not, you will connect to that session.
If the existing session is connected to a display it will be disconnected from that display first. I have the incoming port set at what should the destination port be? It depends. You could forward it to any port you like but most likely you want to forward it to port to enable RDP through your router to a local computer. Works well with ftp but it might not be that simple with RDP.
If you go into the Windows registry you can change the port number the RDP server listens to. I am having trouble with FTP over the internet. I cannot connect to my FTP server even though I forwarded ports 20 and 21….
MPG, what kind of a problem? I use the filezilla FTP server and a friend suggested specifying some random high numbered ports, say to on the FTP server to be used for passive mode FTP and forwarding those ports on the router too. It just connects to the server on port 21 and the server tells it which port s to use I think.
In my case the outside client has to connect to port , the router forwards that to port 21 on the FTP server and the server starts chatting with the outside client with those other ports. It is possible to use a different port for RDP. Change the above mentioned registry key, restart the server or reboot the machine and let the client connect with the command. You can add the command to your startmenu if you like, configure your router to forward the port and you should be able to RDP over the internet without opening port Just use a port number higher than , afaik they are never blocked.
Rob When you make registry changes in xp it is normally done in currentcontrolset In Vista somebody advises to do it in controlset and others suggest to do it in currentcontrolset. Where should changes be done in currentcurrentset or in controlset? For changing port nr if I do it in currentcontrolset its not changing in controlset I dont know after rebooting it changes port nr.
Otherwise there will be conflicting different port nrs. Your adivise needed. I did it in currentcontrolset the other day. Maybe the numbered controlsets are just copies with currentcontrolset being a the same set as the highest numbered controlset.
Or currentcontrolset is renamed to a numbered set and a new copy is made when a system restore point is created. In my previous post I made the impression that modifying the registry is necessary but this might not be the case:.
If you want use a different port number for the sole reason of not using for incoming connections from internet going through a NAT router at home it might be easier and certainly safer to first try changing the port forwarding on your router only, so that incoming connections from outside to port xxx on your router are forwarded to port on your computer.
My only advice is: make a restore point before editting the registry on a computer you use for anything other than just testing. If i configure my router to forward incoming port xxxx request to my IP then I guess my registry should have new xxxx port nr..? Secondly my router dosnt provide any option of forwarding port xxxx to So in my case I guess if i want to use new port then I have to modify registry first..?
In that case you will have change the port number that the rdp server on your computer listens to match the value you choose for x. The only way I know how to that is by editting in the registry.
Maybe it can be done with group policy in ultimate. Good old editting the registry is much easier then that policy crap. How do I fix this? What do you want to achieve with this? The laptop already can do that. RDP runs on 1 desk not the other or the lap. Maybe I can help than. I followed the instructions and nothing so I went back to a restore point and tried again and still the same. Vista home premium has a built in RDP client.
Just go back to that restore again. This forum is about RDP server on vista home premium, not client. Big shit for brains. The problems that others have came to this forum for were relevant to this forum.
The rdp client on your laptop is supported. Just type this in Google: mstsc and please go away. Rob, fuck you and your wanna be holier than thou attitude. I can formulate a sentence quite well especially with a journalism and lit degree. I abbreviated terms as to not waste time you asshole. Open Registry Editor regedit. Reboot the system.
Windows XP will start up as usual. Then download and install DevCon direct download link to devcon. Open a command prompt window Cmd , and the change directory into the i folder extracted by DevCon. Then run the following command to reinstall rdpdr driver :. Reboot after patching the registry. After reboot, the Terminal Services is running and ready to accept incoming Remote Desktop Connection session.
If the service is not started, start it manually. Wow, thats a ton of useless shit to do there as advice. Get a VNC proggy for what you need to do. No dicking around with dll patches and such. At least get it for the Vista machine to connect to your XP box. VNC is very good. No way I would be able to reconnect without flying to Antarctica first, just to log in.
Go figure! Have you tried 9. Go figure …. If all else fails: — system restore, that should completely remove the patch and registry changes. Can someone help? What do I need to do next? However, does not work with any of the user accounts which is good , but will not work with the Admin account that installed the changes. Am I missing something here?
I never experienced this problem before but that might be caused by the fact that I never actually tried to connect to a TS without specifiying one. Very surprising. I simply never thought of trying it that way.
I connected to my Vista desktop from an XP computer. But how can I connect to the XP desktop from my Vista computer? Thank you, I found the Remote Desktop interface. So, I have to run the batch file every time I boot and want to have the remote desktop available, right? To reach the desktop over the internet, I have to set up my router with a firewall rule to forward port to the ip address of my desktop computer running Vista Home Premium?
Once I do that, I just leave it that way, assuming the ip address is made permanent? Once is enough to install evrything and you should be able to use RD anytime after that. Good luck. The only option in this circumstance is a hard reboot. If your remote session drops, you will need to do a soft reboot on your home machine to get things going again.
Unfortunately, this allows my computer to be accessed by anyone in the World, as my router is incapable of restricting inbound IP addresses. If anyone also has the problem I use a Linksys router, by the way , I would highly recommend going into the Windows firewall and restricting IP addresses to Port in your Remote Desktop exception list. Normally the router itself would block incoming access to all ports with the forwarded ports being the exceptions.
The installation procedure here enables de remote desktop service which automatically port only that port in the Windows firewall afaik. In a sense doing what you suggest should already be done automatically. To obfusticate things for unwanted outsiders you could use a different port than for RDP. It seems that Linksys routers do not support this port number translation scheme when it comes to forwarding however.
You could however try this: 1 On the router: forward some port, say to the same port number on your machine. Windows Firewall has an option to filter incoming by the outside IP. I only access my home computer which I am doing right now from work, so I setup Windows firewall to only accept incoming traffic from my IP address here at work.
I wish that the router would do that, but all my testing indicates that it does work. I used to use a D-link wired router, which provided incoming IP filtering. Now I understand your point about the Windows firewall and it is indeed a very good one. Holy cow. I have been struggling with this for hours. I used your fix… well I tried a couple of times unsuccessfully.
It turns out that I needed to copy the file over manually. I have Vista Home Premium. RD now works!!! Thank you so much! I can now get some sleep. This worked perfectly! My thanks to the original guy who created the patch! Most of the patches seem to still work in SP2. The amount of information found here is mind boggling. Thank you all.
Someone ought to clean up this place. By now nobody seeing this page for the first time is going to read it all anyway. Right click the corresponding batch file for your Vista edition and Run as administrator. Test by opening a session to If that succeeds, go to step 9 8.
Restore the system using the restore point created in step 1, then call us back here and describe the situation as fully as possible. Skip step 9. You can now investigate the firewall stuff. Check your Windows version. Hey Guys This would be realy greatfull if it would work for me. But I cant connect with RDP. I have to add i tried to copy termsrv.
Great, thanks to every one. Wow…2 yrs after this posting, and the solution still works! But when I tried the same from outside i. I changed my Belkin router settings to forward the port to the IP of my laptop not of the router. But no success. Give it a shot…. Noob question here. Ive got the patch installed and the ip address for the pc I want to connect to, but what I do use for my user and pass when I open RD on my mac?
I put in the ip address and it wont let me connect. What do i do from finishing the patch to actually creating an account for me to connect with?
Then download, unpack, make restore point, right-click on the premium. Thanks Corey. I concur that a re-install using the above steps is necessary.
I found the following video that shows the step by step process for the install very helpful:. When does it require a reboot? I must have installed the thing over times by now and not once did it require a reboot. Not once. It probably would have required a reboot if it had been a Microsoft add on though. I made did once after finishing serious vLiting just to see how much could be removed before vista would break. In a Sun VirtualBox that is, I never used it on a real machine.
The rdp hack here also still enables concurrent rdp sessions to the virtual machine. To use Vista 95 do you have to so a fresh install or do you run it over an existing installation? Install fresh. Only check whether there are new updates necessary. Once the original image is up to date you can then start removing unnecessary stuff crap from it and reinstalling. You keep removing crap from the image and installing it until it fails to install. Hi folks! I was stuck at port forward in Belkin router.
Follow these steps-. Go to System Settings 3. Next, go to Virtual Servers 5. Click radio button Custom Server, put any name 6. Both External Port Start and End — input port number Click add 9.
Enter Vista username, password I tried applying the patch directly but the Terminal Service was live and the. Stop the service and set the service to Manual. Unzip the file, copy the right.
This patch is so buggy.. Just stop, copy and start should do the trick. Although the script claims it only works on it actually works on anything from onwards until now. Seemed like it was working fine.
Seems like after set time period after reboot RDP stops working. Also, I always have Scandisk primed and ready to go after the unexpected shutdown via the scheduler prompt that you get when trying to run it from Vista.
I do not have a Guest account at the moment but will definatly create one, per your suggestion in an earlier post; I just want to make sure RDP is working remotely first.
I am not familar with this setup, could you direct me or explain a bit more about this? Make sure you installed the patch using your Admin account. As for Scandisk, left click on the Windows icon on the lower left of your screen, then left click on the Computer icon, right click on Local Disk, select Properties, select Tools, then select Error-Checking and Check Now, etc.
You order it and the computer does it. Exactly the same command is executed when doing it via the start menu. Unplugging the power is an unexpected shutdown that might require scandisk being run after the power is reapplied. I installed the termsrv patch several months ago back in March or so , and in fact, am using it right now!
The patch works great, except for the following problems:. I can get to the login screen, but cannot reestablish my original session. Likewise, if the connection drops, Windows is unable to reconnect the session. After 20 attempts, the remote session quits. Usually, however, this is not a problem for them. It will just sit there, for hours, with minimal hard drive activity.
On a few occasions, I have been unable to logon to my primary Admin account but have been able to logon to my backup Admin account. Usually, however, if my primary Admin account does not work, neither will my backup account. Otherwise, the patch works great! As for Scandisk, I like to enable that just in case I have to hit the reset button on my home PC, which I have to do in about a quarter of the time. Don I tried the shutdown -r and low and behold I was able to successfully login remotely router included.
I did run into that issue about closing out off my remote connection versus logging off; I was not able to reconnect. So basically what I did is boot up my PC, then run the shutdown -r command. I did this routine again this morning; and I was unable to login remotely… Right now its hit and miss for me. It almost seems like the stars and moon have to be aligned in order for me to get one successful remote login, but with parameters, or else I will be locked out again.
If the value already is 1 just leave it that way and forget about this suggestion. None of us came out of the womb knowing this stuff.
Till now the patch has been working great…but the latest version of windows security updates messed it up for good in my version of windows home premium…i tried a bunch of things but there is no way I was able to get this back to working…any thoughts? Basically just reinstalling the patch should do the trick anytime.
After trying to reboot, RDP no longer connects. I am assuming that is the same patch Sam tried. I will try using the patch again once I get home.
I have a friend who did the same thing. SP2 seems to have broken the unit. I had him re-run the SP1 hack, but still no worky. Proud Owner of 3 Sticky Kids Follow me on twitter. Hope this is not a previously answered query. Is there a way to allow mouse control from either computer so both machines can be used at the same time using the screen contents of the remote laptop?
I suppose microsoft finally fixed it then. You might want to try Server which you can download from microsoft along with an explanation on how you can use for 8 months without activation. After 8 months you reinstall which should be done twice a year with Windows anyway. Did you only have to add an exception for port ? I added the exception there, still no luck. Then run the corresponding bat file from the zip as administrator.
Everything works fine after that. The script makes the backup file with a copy, takes ownership of the. Just right-clicking the script and running as admin really should be enough. Adding a check for that only takes a couple lines extra, something as simple as:. I was running the script as administrator. When I renamed the file myself, the service finally stopped and once I ran the script again, it worked like a charm.
I have the termsrv patch installed, also. As I have mentioned in my previous posts, if the remote session drops, then I cannot reconnect a second time. One solution that I have tried to get around this problem is to setup a telnet server under Vista go into Control Panel, Programs, select Turn Windows features on or off , etc.
Anyone know how to run a telnet session with an elevated command prompt? This is necessary to reinitialize the Terminal Services process via a reboot, which will allow me to login remotely after a dropped session.
Is the patch supposed to work both ways? You have to enable remote desktop in XP. In XP Pro you goto the remote tab of system properties. Have I missed something? At least as long as I have waited I am running AVG antivirus and Zone Alarm on both machines, and have tried with them off on both machines with same results.
Same error message. Computer B has XP Pro. Vista is SP1. Seem to be hogging the blog, not intentional. Found problem with Zone Alarm on computer B. I was able to run everything without an error. And I am able to get into my vista machine from XP.
However, when I open remote desktop and type in the name of my 2nd computer I get an error. I need some help. The only other details about my computer is that its on my school network but that didnt effect XP. It reads:. Remote Desktop cannot find the remote computer. Type the computer name or IP address again, and then try connecting.
If problem continues, contact the owner of the remote computer or network. Try connecting again If this promblem continues please contact……. Yes, it was a problem with box B! Terminal Services was not running on box B! BBR, check the box you are trying to connect to. Bet TS is off on it, too! Thanks again to the folks that developed the fix for Vista Home Premium. It was running.
When I view remote properties on the system menu in Vista…I still only have the top box for remote assistance. Does this need to change? I found a work-around for my issue above. If you, like me, are unable to connect to your remote desktop session a second time after a dropped session, you can reboot your home PC via Telnet using the following process:. See the following website for more details:. Same user id, same password. I connect to my home Vista machine from my work XP machine.
How safe is this? That will keep your computer safe! Restart no help. Vista home premium SP2. Any thoughts? Also, not that anyone would ever want to undo this miracle? But if i wanted to go about setting everything back how would i do that? When installing this, is the service supposed to be listening? I dont see the option for remote desktop in my options.
How can I solve this issue? What am I doing wrong? I am a complete newbie Im told to say that so i can get easier directions. I know I can use other methods, but Im curious on how to use the remote connection.
I have it on both computers, but Im not sure what to type in for the computer name. I tried the ip, the computer name, and the workgroup. It said I need a domain or something but I cant find it anywhere. And no its not in sys properties under change domain. Ive looked up help and found something on the Microsoft site that said you cant connect To a Vista Home Premium, which I have on both computers, but other help pages mention nothing about it.
Run command in admin mode. Installs OK but when I go into the registry, I dont see the registry patches applied. Even manually dbl click the. So registry imported fine in safe mode. Now, when I try to connect to this vista SP2 x86 host, i even see a login dialog box but it still cant connect. I dont see an error on either side — event log is clean. I dont know what is going on. Used to work fine. I did not change any settings on either computer.
It had been a really good time being here and helping some people. But anyway, this is a really really good article from frans.. It rocks, and has better Remote Desktop than Windows. Due to technical reasons server no longer responding correctly to such a long list of comments , commenting on this thread is unfortunately now closed — my apologies.
Hopefully the information above in all the existing comments is still useful for some. Done See: TonyChan. Like this: Like Loading You have saved me. I was wondering how the hell am I going to do now.. Thank you! I used an administrative account. HTH Mal. Apart from that it works fine, there is one for XP as well, you can get it from antiwpa. Any updates for Vista SP1. Since this hack does not work anymore on Vista with SP1. Props to you frans! I really needed RDC for my desktop!
Step 2. Thanks very much! Thanks, R. Home Basic…. The batch file should run fine. This was tested on Vista Premium Home. Got remote desktop to work but how do I move files between computers. Hope it works…Lemme Know…. Thank you very much for letting me know!! Much appreciated! Thanks for your help. I thought i couldnt use RD with Vista premium. This fixed my problem. A system error has occurred.
System error has occurred. Good luck…. Thanks to everyone here! Thanks again to everyone here! I hope this helps other people that have this problem! Hello, Is it possible to connect to my main account, rather than having to create an entire new account for remote desktop to connect to?
Hi Shantanu, I found out that the problem was caused by the fact that my main account did not have a password on it. However, the same error prompt after i restart the laptop… Hope expert could help me on this….. Because you won't be there at your home or office to turn on your computer and establish an Internet connection, you have to set things up so that your computer and connection are always working.
If the power goes out at your home or office and your computer doesn't start itself up again automatically, you won't be able to connect. Your computer must start up automatically. To set this up on a desktop computer, you need to get to the BIOS setup screen. You can get there when you first power up the computer, or by restarting Windows and waiting for the screen to go black.
The screen tells you what key to press; it's usually the Del or F2 key. Find an entry titled AC Power Recovery, or something similar. Change the setting so that your computer turns itself on when the AC power comes on.
On some computers, there is also an option that turns on the computer only if it was on when the power failed. That works, too. Automatic startup is generally not an option with a laptop computer. If you want remote access to your laptop, you just have to leave it on and hope that the battery takes it through any brief power outages. Besides a 24x7 computer, you need a 24x7 Internet connection.
If you have cable Internet service or a type of DSL service that does not require you to enter a username or password, you have an always-on Internet connection already and can skip ahead to the next section. For DSL service that requires sign-on, you need some means of automatically reestablishing the connection whenever your computer starts up or the connection goes down. Microsoft's built-in Broadband connection sign-on software does not provide a reliable way by itself to keep the Internet connection permanently open.
You can work around this in three ways:. You can use a hardware connection-sharing router. The router connects to your DSL modem and your computer s to the router. The router makes the DSL connection for you, and you can configure it to keep it going all the time.
If you don't have a router already, it's a worthwhile investment to buy one. Be sure to enable the router's "keepalive" feature so that your connection is kept going all the time. Otherwise, the connection might be allowed to close when there is no activity from inside your LAN, and you might not be able to connect later.
All Internet connections are established on the basis of a number called an IP address, which is to your Internet connection as your telephone number is to your phone. Your IP address uniquely identifies your computer among all the millions of connected computers worldwide.
If you use a shared connection, all your network's computers share one public IP address, much as the phone extensions in an office share one outside telephone number. The question is, when you're somewhere else, how do you find your computer's IP address so that Remote Desktop can establish a connection to it?
It has four sets of numbers separated by periods and looks something like this: This will always be your computer's number. You can simply type this in when using the Remote Desktop client to connect to your computer. However, static addresses are relatively hard to get and usually carry a monthly surcharge; in some cases, ISPs simply cannot or will not provide them. So although this is worth looking into, it might not be an option.
My home ISP is sonic. In most cases, dial-up, DSL, and cable Internet connections use dynamic addressing, in which a different IP address is assigned to you every time you or your router connects to your ISP or, in the case of cable service, whenever your cable modem is reset.
Thus, your computer's IP address can change at any time, and you won't necessarily know what it is when you want to connect from somewhere else. The solution to this problem is to use a free dynamic domain name service DDNS. It has two parts: First, on a DDNS provider's website, you register a host name , a name of your own choice, attached to one of several domain names that the provider makes available.
For example, you might register the host name mycomputer in the domain homedns. Some Internet connection-sharing routers have a DDNS client built in, or you can download and install a software version on your computer. When this is all set up, you can use the name mycomputer. Many DDNS providers exist, most of which are free services. Here I give you step-by-step instructions for setting up service with dyndns. Now your DDNS service is set up. Your router's setup screen will likely differ from this, but it will generally look something like the one in Figure Figure Type the command ipconfig and press Enter.
Note the gateway address for the local area connection entry, which will be something like Close this window and open Internet Explorer. If your router doesn't have a DDNS client built in, or if you are not using a hardware router, you have to install a software DDNS client to do the job. You want one that doesn't require any manual intervention to get started and that always runs even when nobody is logged on.
This means that you need one that operates as a Windows service rather than as a regular desktop application. Here's how to set it up.
If you use Windows Internet Connection Sharing, perform this procedure on the computer that shares its connection with the Internet, whether or not it's the computer that you're enabling for Remote Desktop access. Otherwise, do this on the computer that you're enabling for Remote Desktop access. Follow the wizard's instructions, clicking Next after you fill in any required information on each page.
On the first page, if you have dial-up or DSL service that requires a logon and password and the connection is made directly from your computer , click Dial-Up.
If you have cable Internet service or you have a router that establishes the connection for you, select Local Area Network. Now your registered host name will always point to your computer, even when your IP address changes.
0コメント