You will see the System Properties dialog box once more. To see the full name of the computer, click on the Computer Name tab. Write down the full name of the computer, so that you can remember it later. Close the dialog box. Now you should be ready to make the remote connection. To do so, follow these steps from the client computer the one you are connecting from that is running Windows Vista:. Type your User name in the User name field and click the Connect button at the bottom of the dialog box.
A Windows Security dialog box will appear. Type in your password and then click the OK button. A connection will be made, and you will be able to work on the remote computer just as if you were sitting in front of it. In addition, the remote computer must have an always-on Internet connection for this process to work, and you cannot connect to a computer that is sleeping or hibernating, so settings will have to be adjusted accordingly.
Furthermore, if your remote computer is on a network, your settings may be locked so that you cannot change them. If so, you may have to ask your system administrator for assistance. When you are done working remotely, make sure that you log off completely, so the connection will be shut down.
To do so:. I have 2 laptops each with Vista Home Edition. I think this is misleading because I had help from HP one time and they remote logged into my laptop. So I am confused.
Your explanation is very complete but you must be using a higher version of Vista because my System Properties window does not look like yours.
You have 3 options plus Users info to complete under the Remote tab. I do not. So, am I wasting my time trying to do the impossible with Home Edition? How did HP connect to me? Details required :. Cancel Submit. Entegy Volunteer Moderator. In reply to Marsorbit's post on February 13, It's not an "idea", it's cold hard fact that has existed for at least 12 years. How satisfied are you with this reply? Something else must be wrong. Do it from wherever suits you. On home premium you can only use an administrator account to log in to a remote desktop session.
If you have trouble setting up a session from another computer, then a firewall is blocking it and you will have to investigate that. Good luck! Audio works fine here, whether left at the remote computer, switched off or transported to the local machine. I read somewhere that this is one of those terrific security features in windows.
For security reasons. Anybody seen a version that works in windows 7 yet? Is there any way to connect A vista premium to another premium using the hacked dll because it does not work. With this patch your desktop will support multiple simultaneous RDP sessions. Without rebooting. I installed premium. I was getting authentication error error code: 0x I had to modify rdp file default. Now its working like a charm! If I connect how does it know to make a new session or use an existing one?
After lot of googling I got the info from microsoft website. So I changed authentication level to 0 and enable credsupport to 0 in the rdp file on xp machine. In the vista it was logging off my admin account. So I created one more standard account. Couldnt remote with the new account privileges problem so had to promote new account to admin account.
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. These authorized users can connect from any computer by using an Internet connection.
Earlier versions of RDC cannot connect to remote computers across firewalls and across network address translators.
This is because port is typically blocked to improve network security. Port is the port that is used for Remote Desktop connections. However, a TS Gateway server uses port A TS Gateway server has the following benefits:.
It enables Remote Desktop connections to a corporate network from the Internet without requiring a virtual private network VPN connection. It helps you share a network connection with other programs that are running on the computer. This enables you to use the Internet service provider ISP connection instead of the corporate network to send and to receive data over the remote connection. Click Options , click the Advanced tab, and then click Settings.
Click Use these TS Gateway server settings , type the server name in the Server name box, and then select one of the following logon methods from the Logon methods list:.
Allow me to select later This option lets you select a logon method when you connect. Ask for password This option prompts you for a password when you connect. Smart card This option prompts you to insert a smart card when you connect. Select or clear the Bypass TS Gateway server for local addresses check box. By selecting this check box, you prevent the traffic that is moving to and from local network addresses from being routed through the TS Gateway server.
This option makes the connection faster. TS RemoteApp is a feature of Windows Server Terminal Services that lets users on client computers connect to a remote computer and run programs that are installed on the remote computer. For example, employees may be able to connect to a remote computer at a workplace, and they may be able to run Microsoft Word on that computer.
An administrator must publish the programs for users to be able to access the programs. The experience is the same as running a program that is installed on the local computer. TS RemoteApp makes system administration easier because there is only one copy of a program to upgrade and to maintain instead of many copies that are installed on individual computers.
0コメント