-->

First published on CloudBlogs on Jan, 10 2011 NOTE: This is an old post. To learn about RDS in Windows Server 2016, please visit our documentation page One of the recurring issues seen in product support is why a client cannot connect. Specifically, errors such as “Unable to RDP,” “Remote Desktop.
The Fix for 0x4 Errors on Mac RDP Remote Desktop Connection. For us the solution came when we went into the system preferences of the Remote Desktop Connection. And you will notice the default preferences look something like this. We simply unticked the “Use hardware acceleration when possible” check box.

As it turns out, Microsoft provides a Windows service specifically for the purpose of proxying Kerberos requests from an unsecure network to domain controllers. This is called the KDC Proxy Service (KPS), and it was introduced as a supporting service for Direct Access and Remote Desktop Gateway deployments, but it can be used without any of those.

This article provides a solution to an error that occurs when you try to connect to the Terminal service running on one of the affected products.

Applies to: Windows Server 2003
Original KB number: 555382

Symptoms

When you try to connect to the Terminal service running on one of the affected products, you receive the following error message:

Remote Desktop Disconnected
The client could not connect to the remote computer.
Remote connections might not be enabled or the computer might be too busy to accept new connections.
It is also possible that network problems are preventing your connection.
Please try connecting again later. If the problem continues to occur, contact your administrator.
OK Help

Additionally, when you view System Event log on the affected server you see the following event:

Resolution

To resolve the problem, make sure that the correct network adapter is bound to RDP-TCP connection. To do it, follow these steps:

On the server, sign in to the server locally (not using Remote Desktop/Terminal Client).
Select Start, Run, type tscc.msc /s (without quotation marks and select OK).
In the Terminal Services Configuration snap-in, double-click Connections, then RDP-Tcp in the right pane.
Select the Network Adapter tab, select the correct network adapter, and select OK.
Make sure that you can establish an RDP connection to the server.

Alternative resolution steps.Use these steps only if you can't do local sign-in to the affected server.

Warning

Using Registry Editor incorrectly may cause serious problems that may require you to reinstall your operating system. Use Registry Editor at your own risk and only after making backup of full Registry and the keys you are going to change.

Start Registry Editor (Regedt32.exe).
Select FileConnect network Registry. Enter computer name or IP address and select OK. Firewalls between your computer and the affected server may prevent successful connection. Remote Registry service should be running on the server.
Navigate to the following registry key (path may wrap):HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlNetwork{4D36E972-E325-11CE-BFC1-08002BE10318}
Under this key are one or more keys for the globally unique identifiers (GUIDs) corresponding to the installed LAN connections. Each of these GUID keys has a Connection subkey. Open each of theGUIDConnection keys and look for the Name value. Choose the connection you want Terminal Services to use.
When you have found the GUIDConnection key that contains the Name setting that matches the name of your LAN connection, write down or otherwise note the GUID value.
Then navigate to the following key:HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal Serverlanatable. Using the GUID you noted in step 5 select subkey. It's LanaId.
Navigate to the following value:HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerWinStationsRDP-TcpLanAdapter.
Change it's data to the value you noted in step 6. Epc 4 opel software download. If you want RDP to listen on all LAN adapters enter value of 0.

Community Solutions Content Disclaimer

Microsoft corporation and/or its respective suppliers make no representations about the suitability, reliability, or accuracy of the information and related graphics contained herein. All such information and related graphics are provided 'as is' without warranty of any kind. Microsoft and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information and related graphics, including all implied warranties and conditions of merchantability, fitness for a particular purpose, workmanlike effort, title and non-infringement. You specifically agree that in no event shall Microsoft and/or its suppliers be liable for any direct, indirect, punitive, incidental, special, consequential damages or any damages whatsoever including, without limitation, damages for loss of use, data or profits, arising out of or in any way connected with the use of or inability to use the information and related graphics contained herein, whether based on contract, tort, negligence, strict liability or otherwise, even if Microsoft or any of its suppliers has been advised of the possibility of damages.

What is the Trojan Spyware Alert scam?

Scammers behind this tech support scam attempt to trick unsuspecting visitors into believing that their computers are infected with a Trojan and/or Spyware and calling the provided number. In most cases, users who contact scammers behind these sites are encouraged to pay for unnecessary services and/or software, or even to provide remote access to their computers.

You should avoid these websites. This particular web page is hosted using Amazon AWS, a legitimate service provided by Amazon. This is not the first case whereby cyber criminals/scammers have employed this service for malicious purposes.

Like many tech support scam web pages, this one looks very similar to the official Microsoft website. In fact, Microsoft has nothing to do with this or other websites of this kind.

This particular page displays two deceptive pop-up windows notifying visitors that it has detected 'Trojan Spyware', found error code '#0x898778', and blocked access to the computer for security reasons. This page also claims that data such as email credentials, banking passwords, Facebook login credentials, pictures and documents have been compromised.

Visitors are instructed to resolve the problem with the help of 'Windows Support' by calling the +1-(877)-570-9733 number immediately.

In most cases, scammers behind such pages attempt to trick users into paying for supposedly legitimate technical support services and software, or allowing them to access and control their computers remotely via a Remote Access/Administration Tool (RAT).

Note that granting such access to cyber criminals/scammers could infect your computer with malware (e.g., ransomware, Trojan-type malware), and they might steal personal information or perform other malicious actions.

Threat Summary:
Name	Trojan Spyware Alert tech support scam
Threat Type	Phishing, Scam, Social Engineering, Fraud.
Fake Claim	The computer is infected and blocked for security reasons.
Tech Support Scammer Phone Number	+1-(877)-570-9733, +1-(888)-531-1238, +1-844-264-1242, 1-888-308-5705
Symptoms	Fake error messages, fake system warnings, pop-up errors, hoax computer scan.
Distribution methods	Compromised websites, rogue online pop-up ads, potentially unwanted applications.
Damage	Loss of sensitive private information, monetary loss, identity theft

Microsoft Remote Desktop Error Code 0x7