Allow connections from computers from computers running any version of Remote Desktop less secure. Allow connections from computers only from computers running Remote Desktop with Network Level Authentication more secure. If you select Don't allow connections to this computer on the Remote tab, no users will be able to connect remotely to this computer, even if they are members of the Remote Desktop Users group.
In the RD Maximum Connections allowed box, type the maximum number of connections that you want to allow, and then click OK.
Under Connections , right-click the name of the connection, and then click Properties. On the Network Adapter tab, click Maximum connections , enter the number of simultaneous remote connections that you want to allow for the connection, and then click OK.
If the Maximum connections option is selected and dimmed, the Limit number of connections Group Policy setting has been enabled and has been applied to the RD Session Host server.
You can add users and groups to the Remote Desktop Users group by using the following tools:. Membership in the local Administrators group, or equivalent, on the RD Session Host server that you plan to configure, is the minimum required to complete this procedure. Start the System tool. If you select the Don't allow connections to this computer option on the Remote tab, no users will be able to connect remotely to this computer, even if they are members of the Remote Desktop Users group.
This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, see How to back up and restore the registry in Windows.
To resolve this problem, determine which application is using the same port as RDP. If the port assignment for that application cannot be changed, change the port assigned to RDP by changing the registry.
After you change the registry, you must restart the Remote Desktop Services service. After you restart the Remote Desktop Services service, you should verify that the RDP port has been changed correctly. The listener component runs on the Remote Desktop server and is responsible for listening for and accepting new Remote Desktop Protocol RDP client connections, thereby allowing users to establish new remote sessions on the Remote Desktop server.
There is a listener for each Remote Desktop Services connection that exists on the Remote Desktop server. Connections can be created and configured by using the Remote Desktop Services Configuration tool.
You can run the netstat tool to determine whether port or the assigned RDP port is being used by another application on the Remote Desktop server:. To determine which application is using port or the assigned RDP port , use the tasklist command-line tool along with the PID information from the netstat tool:.
You should determine whether this application can use a different port. Doing so will allow Remote Desktop through the Windows Firewall.
Go to source. This saves your changes. Part 3. Consider setting a static IP address. This is optional, but recommended. A static IP address won't change when your router disconnects or your computer reconnects to the network, meaning that the IP address you find now will work in the future; failing to do this means you'll need to find the IP address of the target computer whenever you want to connect to it.
Go to your router's IP address in a web browser and log in with your router's credentials if prompted. Find the list of currently connected computers and select your computer. Make the IP address static by clicking the lock icon or similar. Wait for your router to finish rebooting. Open a web browser. On the target computer, click or double-click the app icon for a web browser e. Find your public IP address.
Next to the "Your Public IPv4 is" heading at the top of the page, you'll find your target computer's public IP address. Log out of the target computer. Part 4. Search for Remote Desktop. Type in remote desktop to do so. You should see a list of results appear in the Start window. Click Remote Desktop Connection. This should be the top result in the Start menu. Doing so opens the Remote Desktop window. You may instead just click Remote Desktop here.
Enter the IP address of the target computer. Click the "Computer" text box in the middle of the Remote Desktop window, then type in the target computer's public IP address.
Click Connect. Enter the login credentials for the target computer. When prompted, type in the administrator name and password for the account on which you enabled Remote Desktop. If you added another user to Remote Desktop, you can enter their credentials instead to access their account.
Doing so connects your computer to the target computer, though it may take several minutes for the connection to finalize; once you see the other computer's desktop appear in Remote Desktop, you're free to peruse your remote computer as you please. How do I see the task manager on the remote computer when using remote desktop?
Yes No. All submitted content is subject to our Terms Of Use. Everything is setup correctly on both ends and I have no problems remoting to other computers at the same locations. Anyone else ever experience the problem, and is their a solution to it?
Thanks, Aubrey. Share Flag. All Answers. Collapse -. Same Problem. Janet 0 Votes. Remote Desktop causes remote machine to reboot.
Worked for me! I know with remote desktop with terminal server there is a setting that will log off an inactive connection after a certain time.
A group policy can control this any may be applying to the windows 7 boxes as well. Ours is set to keep the session alive for an indefinite amount of time. What is the operating system of the computer you are remoting into?
I know Microsoft allows up 2 two users to be logged into the same box without have terminal server licensing. It is a Windows 7 box that is being remoted into. From either a Windows 7 or XP machine. I have already tried setting up the session time limits but it hasn't been working. Check your active directory for user properties, under sessions make sure End a disconnected session, Active session limit, and Idle session limit are all set to never.
This keeps sounding like you have a rogue GPO in place somewhere. Have you done a gpresults and see what pops up on the remote PCs? So the problem is only on a few of your Windows 7 boxes. Have you had one of the people this is happening to log into a different machine to see if the results are the same?
Yes I've tried that. I can remote into other machines no problem.
0コメント