This Computer Cant Connect to the Remote Computer Try Connecting Again Windows 7

Remote users can connect to their Windows x and 11 computers via the Remote Desktop Services (RDP). It is enough to enable RDP in the device settings and connect to the computer using any Remote Desktop client. Just in that location is a restriction on the number of simultaneous RDP sessions – just one remote user can work simultaneously. If you try to open a second RDP session, a warning volition appear request you to disconnect the showtime user's session.

Another user is signed in. If you proceed, they'll be disconnected. Do you lot want to sign in anyway?

All desktop Windows versions (including Win 10 and 11) have a number of restrictions on the Remote Desktop Service usage:

1. Yous can remotely connect via RDP but to higher Windows editions (Professional and Enterprise). In Windows Home and Single Language editions the incoming remote desktop connections are forbidden;
2. Just ane simultaneous RDP connectedness is supported. When y'all try to open up a second RDP session, the user is prompted to close the active connection;
3. If there is a user who works on the console of the calculator (locally), then when you attempt to create a new remote RDP connection, the panel session will be disconnected. A remote RDP session will exist too forcibly disconnected if the user volition endeavor to log in locally.

Really, the number of simultaneous RDP connections on Windows is limited by the license (and not past any technical aspect). Thus, this restriction doesn't allow to create a terminal RDP server based on the workstation that tin can be used past multiple users. Microsoft's logic is simple: if you need a terminal server – buy a Windows Server license, RDS CALs, install and configure the Remote Desktop Session Host (RDSH) role.

Technically, any Windows version with a sufficient corporeality of RAM tin can support the simultaneous operation of several dozens of remote users. On average, 150-200 MB of RAM is required for 1 user session (excluding running apps). Those, the maximum number of simultaneous RDP sessions is theoretically limited only by computer resources.

Let's consider two ways on how to let simultaneous RDP connections on Windows x and 11: using the RDP Wrapper tool or patching the termsrv.dll organization file.

Contents:

• RDP Wrapper: Enable Multiple RDP Sessions on Windows
• RDP Wrapper Not Working on Windows 10
• Modify the Termsrv.dll to Enable Multiple RDP Sessions
• Patching Termsrv.dll on Windows Using PowerShell

Notation. Arrangement modifications described in the commodity are considered as a violation of the Microsoft License Agreement  and you may perform them at your own gamble.

RDP Wrapper: Enable Multiple RDP Sessions on Windows

The RDP Wrapper Library OpenSource projection allows you to enable multiple RDP sessions on Windows 10 without replacing the termsrv.dll file. This tool works as a layer between SCM (Service Control Manager) and the Remote Desktop Services. RDPWrap allows you to enable not only support for multiple simultaneous RDP connections but also to build an RDP server on Windows Home editions. RDP Wrapper doesn't make whatever changes to the termsrv.dll file, it's just loading termsrv library with the changed parameters.

Thus, the RDPWrap volition piece of work even in the example of termsrv.dll file update. It allows y'all not to exist afraid of Windows updates.

Important. Before installing RDP Wrapper, it is of import to brand that you lot are using the original (unpatched) version of the termsrv.dll file. Otherwise, RDP Wrapper may become unstable or not start at all.

You tin download the RDP Wrapper from the GitHub repository https://github.com/binarymaster/rdpwrap/releases (the latest available version of the RDP Wrapper Library is v1.half-dozen.two). The project hasn't been updated since 2017, but it can be used in all new builds of Windows 10 and even Windows xi.

The RDPWrap-v1.half-dozen.2.zip annal contains some files:

• RDPWinst.exe — an RDP Wrapper Library install/uninstall the program;
• RDPConf.exe — an RDP Wrapper configuration tool;
• RDPCheck.exe —an RDP check utility (Local RDP Checker);
• install.bat, uninstall.bat, update.bat — batch files to install, uninstall, and update RDP Wrapper.

To install RDPWrap, run the install.bat file every bit an ambassador. The program volition be installed to the C:\Program Files\RDP Wrapper directory.

Subsequently the installation is consummate, run the RDPConfig.exe. Most likely, immediately later on installation, the tool will testify that the RDP wrapper is running (Installed, Running, Listening), but non working. Note the blood-red warning [not supported]. It reports that this version of Windows 10 (ver. 10.0.19041.1320) is not supported by the RDPWrapper.

The fact is that for each version of Windows 10 there must be a description in the rdpwrap.ini configuration file. Your config file simply doesn't have any settings for your Windows 10 build.

The current version of the rdpwrap.ini file can be downloaded here https://raw.githubusercontent.com/sebaxakerhtc/rdpwrap.ini/master/rdpwrap.ini

Manually copy the contents of this folio to the "C:\Programme Files\RDP Wrapper\rdpwrap.ini" file. Or download the file using the PowerShell cmdlet Invoke-WebRequest (you must beginning stop the Remote Desktop service):

Stop-Service termservice -Force
Invoke-WebRequest https://raw.githubusercontent.com/sebaxakerhtc/rdpwrap.ini/primary/rdpwrap.ini -outfile "C:\Programme Files\RDP Wrapper\rdpwrap.ini"

Restart your computer, run the RDPConfig.exe tool. Check that all items are green in the Diagnostics department and the caption [Fully supported] appears. The screenshot below shows that the RDP Wrapper with this new config works fine on Windows 11 as well.

Endeavour to plant several RDP sessions to your estimator (use any RDP customer: mstsc.exe, rdcman, etc.). It worked out well (y'all can fifty-fifty utilize saved RDP credentials)! Now your Windows 10 allows two (and more) remote users to use different RDP sessions simultaneously.

The RDPWrap tool is supported in all Windows editions, so you can build your own final (RDS) server on any Windows device.

Likewise, RDP Wrapper allows to:

• Enable Remote Desktop;
• The option Hide users on logon screen allows you to hide the listing of users from the Windows Logon Screen;
• If y'all disable the Unmarried session per user selection, multiple simultaneous RDP sessions will be allowed nether the same user account (the registry parameter fSingleSessionPerUser =  0 is fix under the reg fundamental HKLM\Arrangement\ CurrentControlSet\Control\Terminal Server\fSingleSessionPerUser);
• RDP Port — you lot can change the Remote Desktop port number from TCP 3389 to any other;
• In the Session Shadowing Style section, you lot can configure the remote control (shadow) connexion mode to RDP sessions.

RDP Wrapper Not Working on Windows x

In some cases, the RDP Wrapper tool doesn't piece of work equally expected and yous cannot to your Windows host using multiple RDP sessions.

If the utility showed [not supported] in the status section, then the rdpwrap.ini file doesn't contain configuration for your Windows build. Update the rdpwrap.ini file equally described above.

If the RDP Wrapper doesn't piece of work after updating the rdpwrap.ini file, endeavor opening the rdpwrap.ini file and looking for a clarification section for your Windows version. How to know if there is back up for your version of Windows in the rdpwrapper config file?

The screenshot below shows that for my version of Windows x (x.0.19041.1320) there are two clarification sections:

[ten.0.19041.1320] …..  [10.0.19041.1320-SLInit]  …..

If in that location is no section in the config file for your version of Windows, effort using Google to search for the rdpwrap.ini strings for your Windows build. Add together the lines you lot find to the terminate of the file.

If after installing security updates or upgrading the Windows 10 build, RDP Wrapper doesn't work correctly, check if the "Listener state: Not listening" is displayed in the Diagnostics section.

Try updating the rdpwrap.ini file, and and then reinstalling the service:

rdpwinst.exe -u
rdpwinst.exe -i

Information technology happens that when you try to constitute a second RDP connection under a dissimilar user business relationship, you run into a warning:

The number of connections to this estimator is limited and all connections are in use right now. Endeavour connecting later or contact your system administrator.

In this instance, you can utilize the Local Group Policy Editor (gpedit.msc) to enable the policy "Limit number of connections" under Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Connections department. Change its value to 999999.

Restart your computer to update the GPO and employ the settings.

Modify the Termsrv.dll to Enable Multiple RDP Sessions

To remove the brake on the number of concurrent RDP user connections in Windows 10 without using rdpwrapper, you lot can replace the original termsrv.dll file. This is the main library file used past the Remote Desktop Service. The file is located in C:\Windows\System32 directory.

Before yous edit or supersede the termsrv.dll file, it is advisable to create its backup re-create. This will help you to revert to the original version of the file if necessary. Open the elevated control prompt and run the command:

copy c:\Windows\System32\termsrv.dll termsrv.dll_backup

Then you need to have ownership of the file. To modify the possessor of a file from TrustedInstaller to the local Administrators grouping using the control:

takeown /F c:\Windows\System32\termsrv.dll /A

SUCCESS: The file (or binder): c:\Windows\System32\termsrv.dll at present owned by the administrators grouping

Now grant the local administrators group Full Control permissions on the termsrv.dll file using the icacls.exe:

icacls c:\Windows\System32\termsrv.dll /grant Administrators:F

processed file: c:\Windows\System32\termsrv.dll Successfully candy 1 files; Failed processing 0 files.

After that, stop the Remote Desktop service (TermService) using the services.msc console or from the control prompt:

Net cease TermService

The Remote Desktop Services UserMode Port Redirector service stops with it.

Earlier moving on, you lot need to find out your version (build number) of Windows x. Open the PowerShell console and run the command:

Go-ComputerInfo | select WindowsProductName, WindowsVersion

In my case, Windows 10 build 21H1 is installed.

Then open the termsrv.dll file using whatever HEX editor (for example, Tiny Hexer). Depending on your Windows build, you lot need to find and replace the cord co-ordinate to the tabular array below:

Windows build	Discover the string	Supervene upon with
Windows 11 RTM ( 21H2 – 22000.258)	39 81 3C 06 00 00 0F 84 4F 68 01 00	B8 00 01 00 00 89 81 38 06 00 00 90
Windows 10 x64 21H2	39 81 3C 06 00 00 0F 84 DB 61 01 00
Windows 10 x64 21H1	39 81 3C 06 00 00 0F 84 2B 5F 01 00
Windows 10 x64 20H2	39 81 3C 06 00 00 0F 84 21 68 01 00
Windows 10 x64 2004	39 81 3C 06 00 00 0F 84 D9 51 01 00
Windows 10 x64 1909	39 81 3C 06 00 00 0F 84 5D 61 01 00
Windows 10 x64 1903	39 81 3C 06 00 00 0F 84 5D 61 01 00
Windows x x64 1809	39 81 3C 06 00 00 0F 84 3B 2B 01 00
Windows 10 x64 1803	8B 99 3C 06 00 00 8B B9 38 06 00 00
Windows 10 x64 1709	39 81 3C 06 00 00 0F 84 B1 7D 02 00

Tiny Hexer editor cannot edit termsvr.dll file directly from system32 folder. Copy it to your desktop, and after modification supersede the original file.

For instance, my build of Windows 10 x64 is 21H1 (19043.1320) with the termsrv.dll file version x.0.19041.1320. Open up the termsrv.dll file in Tiny Hexer, then detect the text:

39 81 3C 06 00 00 0F 84 2B 5F 01 00

and replace it with:

B8 00 01 00 00 89 81 38 06 00 00 90

Save the file and run the TermService.

If something goes wrong and y'all experience some problems with the Remote Desktop service, stop the service and replace the modified termsrv.dll file with the original version:

re-create termsrv.dll_backup c:\Windows\System32\termsrv.dll

Patching Termsrv.dll on Windows Using PowerShell

In order not to modify the termsrv.dll file manually using a HEX editor, you can employ the following PowerShell script to apply the patch automatically. This script is based on the Windows PowerShell version and doesn't work on modern PowerShell Core. The script is universal and can exist used to patch the termsrv.dll file on all editions of Windows 10 (1809+) and Windows 11.

# Stop RDP service, make a fill-in of the termsrv.dllfile and change the permissions
End-Service UmRdpService -Forcefulness
Stop-Service TermService -Force
$termsrv_dll_acl = Get-Acl c:\windows\system32\termsrv.dll
Copy-Item c:\windows\system32\termsrv.dll c:\windows\system32\termsrv.dll.copy
takeown /f c:\windows\system32\termsrv.dll
$new_termsrv_dll_owner = (Become-Acl c:\windows\system32\termsrv.dll).owner
cmd /c "icacls c:\windows\system32\termsrv.dll /Grant $($new_termsrv_dll_owner):F /C"
# search for a design in termsrv.dll file
$dll_as_bytes = Go-Content c:\windows\system32\termsrv.dll -Raw -Encoding byte
$dll_as_text = $dll_as_bytes.forEach('ToString', 'X2') -join ' '
$patternregex = ([regex]'39 81 3C 06 00 00(\s\S\S){6}')
$patch = 'B8 00 01 00 00 89 81 38 06 00 00 90'
$checkPattern=Select-String -Pattern $patternregex -InputObject $dll_as_text
If ($checkPattern -ne $naught) {
$dll_as_text_replaced = $dll_as_text -replace $patternregex, $patch
}
Elseif (Select-Cord -Pattern $patch -InputObject $dll_as_text) {
Write-Output 'The termsrv.dll file is already patch, exitting'
Exit
}
else {
Write-Output "Design non found "
}
# patching termsrv.dll
[byte[]] $dll_as_bytes_replaced = -split $dll_as_text_replaced -supercede '^', '0x'
Set-Content c:\windows\system32\termsrv.dll.patched -Encoding Byte -Value $dll_as_bytes_replaced
# comparing 2 files
fc.exe /b c:\windows\system32\termsrv.dll.patched c:\windows\system32\termsrv.dll
# replacing the original termsrv.dll file
Re-create-Item c:\windows\system32\termsrv.dll.patched c:\windows\system32\termsrv.dll -Force
Set-Acl c:\windows\system32\termsrv.dll $termsrv_dll_acl
Outset-Service UmRdpService
Start-Service TermService

The complete script code is available in my GitHub repository at https://github.com/maxbakhub/winposh/hulk/chief/termsrv_rdp_patch.ps1

To execute the script, download information technology to your computer. Modify the PowerShell execution policy settings for the electric current session:

Fix-ExecutionPolicy Bypass -Scope Process -Force

And run the script:

C:\users\root\desktop\termsrv_rdp_patch.ps1

The script can be run afterward installing Windows updates to immediately make changes to the termsrv.dll file (you don't have to modify the termsrv.dll file in the HEX editor subsequently each update installation).

The advantage of the method of enabling multiple RDP sessions in Windows ten or 11 past replacing the termsrv.dll file is that antiviruses exercise not respond to it (unlike the RDPWrap, which is detected by many antiviruses as a Malware/HackTool/Trojan).

The principal drawback is that yous will take to manually edit the termsrv.dll file each time you upgrade the Windows 10 build (or when updating the version of the termsrv.dll file during the installation of monthly cumulative updates). And if you are using RDPWrapper, you volition also need to update the rdpwrap.ini file after installing Windows updates.

In this article, we looked at how to remove the restriction on the number of simultaneous RDP user connections and run a costless terminal server on desktop versions of Windows.

blossevillecoutiek.blogspot.com

Source: http://woshub.com/how-to-allow-multiple-rdp-sessions-in-windows-10/

Share :