Fix rdp windows 7

Applies ToWindows 7 Service Pack 1 Windows 7 Enterprise Windows 7 Home Premium Windows 7 Professional Windows 7 Starter Windows 7 Ultimate Windows Server 2008 R2 Service Pack 1 Windows Server 2008 R2 Datacenter Windows Server 2008 R2 Enterprise Windows Server 2008 R2 for Itanium-Based Systems Windows Server 2008 R2 Foundation Windows Server 2008 R2 Standard Windows Server 2008 R2 Web Edition

Not sure if this is the right fix? We’ve added this issue to our memory dump diagnostic which can confirm.

Symptoms

Assume that you want to establish a remote connection from a computer that is running Windows 7 or Windows Server 2008 R2. You open a Remote Desktop Protocol (RDP) tool to connect to a remote desktop server, and you provide your credentials when prompted. In this situation, you intermittently cannot connect to the remote desktop server. Additionally, you receive an «Access Denied» error message.

Note Network-related applications such as the System Center Configuration Manager console and Active Directory Users and Computers encounter a similar issue when they connect to their respective remote servers.

Cause

This issue occurs because of a timing issue that is caused by an infinite loop in the Lsass.exe process.

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a «Hotfix download available» section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:

http://support.microsoft.com/contactus/?ws=supportNote The «Hotfix download available» form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 7 and Windows Server 2008 R2 file information notesImportant Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under «Windows 7/Windows Server 2008 R2» on the page. Always refer to the «Applies To» section in articles to determine the actual operating system that each hotfix applies to.

• The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

  Version	Product	Milestone	Service branch
  6.1.760 1.22xxx	Windows 7 and Windows Server 2008 R2	SP1	LDR

• The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the «Additional file information for Windows 7 and for Windows Server 2008 R2» section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows 7

File name	File version	File size	Date	Time	Platform
Cng.sys	6.1.7601.22099	369,856	28-Nov-2012	23:02	x86
Ksecdd.sys	6.1.7601.22176	67,416	29-Nov-2012	05:41	x86
Ksecpkg.sys	6.1.7601.22176	136,536	29-Nov-2012	05:41	x86
Lsasrv.dll	6.1.7601.22176	1,040,384	29-Nov-2012	05:33	x86
Lsasrv.mof	Not applicable	13,780	12-Nov-2010	23:53	Not applicable
Lsass.exe	6.1.7601.22176	22,528	29-Nov-2012	05:30	x86
Secur32.dll	6.1.7601.22176	22,016	29-Nov-2012	05:36	x86
Sspicli.dll	6.1.7601.22176	100,352	29-Nov-2012	05:36	x86
Sspisrv.dll	6.1.7601.22176	15,872	29-Nov-2012	05:36	x86
Ncrypt.dll	6.1.7601.22153	220,160	05-Nov-2012	15:29	x86
Schannel.dll	6.1.7601.22153	247,808	05-Nov-2012	15:30	x86

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name	File version	File size	Date	Time	Platform
Cng.sys	6.1.7601.22099	458,712	28-Nov-2012	23:02	x64
Ksecdd.sys	6.1.7601.22176	95,576	29-Nov-2012	06:08	x64
Ksecpkg.sys	6.1.7601.22176	154,472	29-Nov-2012	06:08	x64
Lsasrv.dll	6.1.7601.22176	1,448,448	29-Nov-2012	06:00	x64
Lsasrv.mof	Not applicable	13,780	12-Nov-2010	23:50	Not applicable
Lsass.exe	6.1.7601.22176	31,232	29-Nov-2012	05:56	x64
Secur32.dll	6.1.7601.22176	28,160	29-Nov-2012	06:03	x64
Sspicli.dll	6.1.7601.22176	136,192	29-Nov-2012	06:04	x64
Sspisrv.dll	6.1.7601.22176	29,184	29-Nov-2012	06:04	x64
Ncrypt.dll	6.1.7601.22153	307,200	05-Nov-2012	17:23	x64
Schannel.dll	6.1.7601.22153	341,504	05-Nov-2012	17:25	x64

For all supported IA-64-based versions of Windows Server 2008 R2

File name	File version	File size	Date	Time	Platform
Cng.sys	6.1.7601.22099	789,032	28-Nov-2012	22:54	IA-64
Ksecdd.sys	6.1.7601.22176	179,560	29-Nov-2012	04:55	IA-64
Ksecpkg.sys	6.1.7601.22176	316,264	29-Nov-2012	04:55	IA-64
Lsasrv.dll	6.1.7601.22176	2,657,792	29-Nov-2012	04:50	IA-64
Lsasrv.mof	Not applicable	13,780	12-Nov-2010	23:52	Not applicable
Lsass.exe	6.1.7601.22176	56,320	29-Nov-2012	04:46	IA-64
Secur32.dll	6.1.7601.22176	48,640	29-Nov-2012	04:53	IA-64
Sspicli.dll	6.1.7601.22176	275,456	29-Nov-2012	04:53	IA-64
Sspisrv.dll	6.1.7601.22176	46,080	29-Nov-2012	04:53	IA-64
Ncrypt.dll	6.1.7601.22153	551,424	05-Nov-2012	15:24	IA-64
Schannel.dll	6.1.7601.22153	711,680	05-Nov-2012	15:26	IA-64

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7

File name	X86_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.22176_none_a89c923ed459f33d.manifest
File version	Not applicable
File size	101,124
Date (UTC)	29-Nov-2012
Time (UTC)	06:06
Platform	Not applicable
File name	X86_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.22153_none_6042fc08691d45c3.manifest
File version	Not applicable
File size	2,737
Date (UTC)	05-Nov-2012
Time (UTC)	19:45
Platform	Not applicable
File name	X86_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.22153_none_247af184ccc40de1.manifest
File version	Not applicable
File size	12,919
Date (UTC)	05-Nov-2012
Time (UTC)	19:47
Platform	Not applicable

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name	Amd64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.22176_none_04bb2dc28cb76473.manifest
File version	Not applicable
File size	101,128
Date (UTC)	29-Nov-2012
Time (UTC)	06:53
Platform	Not applicable
File name	Amd64_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.22153_none_bc61978c217ab6f9.manifest
File version	Not applicable
File size	2,741
Date (UTC)	05-Nov-2012
Time (UTC)	20:59
Platform	Not applicable
File name	Amd64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.22153_none_80998d0885217f17.manifest
File version	Not applicable
File size	12,921
Date (UTC)	05-Nov-2012
Time (UTC)	21:03
Platform	Not applicable
File name	Wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.22176_none_0f0fd814c118266e.manifest
File version	Not applicable
File size	87,695
Date (UTC)	29-Nov-2012
Time (UTC)	05:53
Platform	Not applicable
File name	Wow64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.22153_none_8aee375ab9824112.manifest
File version	Not applicable
File size	6,945
Date (UTC)	05-Nov-2012
Time (UTC)	19:35
Platform	Not applicable

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

File name	Ia64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.22176_none_a89e3634d457fc39.manifest
File version	Not applicable
File size	101,126
Date (UTC)	29-Nov-2012
Time (UTC)	06:45
Platform	Not applicable
File name	Ia64_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.22153_none_60449ffe691b4ebf.manifest
File version	Not applicable
File size	2,739
Date (UTC)	05-Nov-2012
Time (UTC)	17:39
Platform	Not applicable
File name	Ia64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.22153_none_247c957accc216dd.manifest
File version	Not applicable
File size	12,920
Date (UTC)	05-Nov-2012
Time (UTC)	17:41
Platform	Not applicable
File name	Wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.22176_none_0f0fd814c118266e.manifest
File version	Not applicable
File size	87,695
Date (UTC)	29-Nov-2012
Time (UTC)	05:53
Platform	Not applicable
File name	Wow64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.22153_none_8aee375ab9824112.manifest
File version	Not applicable
File size	6,945
Date (UTC)	05-Nov-2012
Time (UTC)	19:35
Platform	Not applicable

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Here you will be finding basic and simple troubleshooting tips for Windows Remote Desktop connection problem. You can apply and check every method mentioned below when you can’t connect to a Windows 10 or Windows 7/8.1 computer with RDP client from another computer. Understanding the requirements of RDP (Remote Desktop Protocol) and how it works will solve most of the problems.

The Remote Desktop connection utility helps to take control of other computers over the network and work like you are sitting in front of them. When it comes to Windows 7 and later Operating Systems such as Windows 10 and 8.1, we can’t connect remote desktop easily because of the default security settings. This article explains how to enable remote desktop connection in Windows 10 and Windows 7, so all versions of Windows OS users can connect remotely.

6 Steps to Fix Remote Desktop Connectivity Issue in Windows 10/8.1/7

Before dive deep, make sure you have the active network connection between both computers. If no network communication, obviously, the remote desktop will not work.

Since it uses RDP packets to communicate, your routers and firewalls should not block this packet. The following methods are applicable for server versions such as Windows 2012 R2, 2016 and 2019 also when the remote desktop is not working.

1) Allow Connection for All Versions

By default, remote desktop is disabled in the latest Windows Operating Systems. To Enable it, Right-click ‘My Computer’ and select Properties.

Got go Remote Settings as shown below.

Two options are available to enable remote desktop connection in Windows 10.

Select Allow connections from computers running any version of Remote Desktop to allow people using any versions of Remote Desktop or RemoteApp to connect your computer. This is a good choice if you don’t know the exact version of the client, but it is less secure than the second option and not recommended. Also, you need to use this option if the request comes from older versions of Operating Systems.

Select Allow connections only from computers running Remote Desktop with Network Level Authentication to allow computers using the Remote Desktop or RemoteApp version which supports Network Level Authentication to connect your computer. This is the most secure choice. Since most of the recent Operating Systems support this authentication method, it is highly recommended to use this option.

Enable RDP in Windows 10

Windows 10 has similar settings to enable RDP connections.

If the Network Level Authentication option is enabled, the older versions of remote desktop clients can’t be used to connect the latest Windows Operating Systems.

2) Allow Remote Desktop Connection in Windows Firewall.

The remote desktop connection uses RDP (Remote Desktop Protocol) that is blocked in Windows firewall by default. But, when we enable Remote desktop connection (as described in step 1), it automatically gets enabled and allows incoming remote desktop connections in the firewall. To confirm it, go to Windows Firewall in control panel.

Click on Allow programs… option as shown below.

In the next screen, you can see which programs are allowed or blocked in Windows Firewall.

In the above example, Remote Desktop is enabled in Private and Public networks in Windows 7. To change any of the options here, first press ‘Change Settings’ button and modify. Similar settings can be found and used in Windows 10 as well.

If you are using third-party firewall protection tools, then you need to enable the incoming RDP protocol to make it work.

Remote Desktop connection works with RDP traffic on TCP 3389 port.

3) Allowed Remote Desktop Users

Here is one more consideration when we can’t connect Remote Desktop to a Windows computer.

Not all users can take the remote desktop connection to other computers. Only the local administrators, administrator group members, and ‘Remote desktop Users’ group have the ability to use remote desktop connectivity. If you are trying a user account which doesn’t have this privilege, then the remote desktop will not work.

If domain (Active directory) setup is in place, the access of remote desktop connectivity works according to the group policy and permissions. Make sure that the user name you are trying to connect a Windows computer is in the appropriate access group.

Read Also: Simple Tip to access the Facebook desktop full site on your smartphone

4) Check the Remote Desktop Services

All services related to Remote desktop connections are disabled by default. Once you enable remote desktop (as mentioned in the first step) access, these three services will start automatically. These services should be up and running all the time to accept the incoming remote desktop connection.  If you can’t connect RDP to a Windows 10, then you must check these services also.

Go to Computer management, then Services. Look for following services and make sure they are running.

5) Try This If Remote Desktop Connection is Slow

Sometimes the RDP connection will be slow and experience the poor display performance due to slow network connectivity. If you use Windows 8.1/10 remote desktop connection through WAN (Wide Area Network) or the Internet, then you will be facing this issue.

Usually, we can use the RDP connection for basic tasks only, and not for any multimedia or high graphical required activities over the network. Therefore the screen resolution and color depth settings can be reduced to have better experience in a slow network. To do that, before making the connection, change a few settings in display properties of RDP client in Windows 10 or 8.1.

Changing the settings to lower color depth (15 bit in Windows 8.1 as marked by 2) in Remote Desktop Connection program will improve the performance by using minimal bandwidth in slow network connections. Also, reducing the display (in pixels as marked 3) resolution can help in seeing the remote computer in smaller/limited screen size which can hugely improve the performance in a slow network.

5) Connect Remote Desktop to Windows 10 from Outside Network – Internet

If you like to take Remote desktop connection to your Windows 10 or 8.1 through the Internet from anywhere in the world, then there are specific configurations need to be done in the Internet router. Here are a few considerations.

1) The port forwarding should be enabled in the Internet router to forward any incoming RDP connection on public IP (or DNS name) to internal Windows 8.1/10 computer which you like to connect via RDP over the internet.

2) Your home/office internet should have public static IP or DynDNS with a dynamic IP address. Because your internet modem gateway should have a valid static IP or name to be able to accept a connection on the internet.

6) Third-Party Free Apps

This can be the ultimate and simple solution with the additional features if you are looking for a product that can replace tradition Windows remote desktop utility.

These programs will work through the Internet without any changes on your home Internet router or firewall. But unlike Microsoft’s built-in RDP client, some of the free programs require someone to install and accept RDP connection from the destination computer.

1) Ammyy Admin

2) AeroAdmin

3)TeamViewer

Conclusion

Hope this guide is helpful in troubleshooting Windows 10, Windows 8.1/7 and MS server remote desktop connection issues on your home or office network. Also, there are few tweaks and other third-party programs mentioned here to overcome the connectivity issues from the Internet and WAN.

В последнее время всё чаще у пользователей Windows 7 возникает ошибка при подключении к удаленному рабочему столу на Windows Server 20162019 через шлюз удаленных рабочих столов.

Ошибка следующая – “Не удалось подключиться к удаленному компьютеру, так как сервер шлюза удаленных рабочих столов временно недоступен. Попробуйте подключиться позже или обратитесь за помощью к администратору сети.”

Рисунок 1 – Ошибка подключения к серверу