In this article, I will discuss the fix for Remote Desktop Protocol Error 0x1104 on Windows Server 2012.
Identifying the Protocol Error
If you’re encountering a Protocol Error 0x1104 while using Remote Desktop on Windows Server 2012, here’s how to fix it.
First, check your antivirus software. Some antivirus programs, like AVG AntiVirus, can interfere with Remote Desktop Services. Temporarily disable your antivirus software or add an exception for Remote Desktop to see if it resolves the issue.
Next, make sure the correct port is open on your firewall. The default port for Remote Desktop Protocol is 3389. Ensure that this port is open in your firewall settings to allow communication.
If you’re using a web browser to access Remote Desktop, try clearing your browser cache and restarting the browser. This can help resolve any temporary issues that may be causing the error.
Additionally, check for any updates for your Remote Desktop software and Windows Server 2012. Microsoft regularly releases updates to address known issues and improve compatibility.
If none of these solutions work, you can try using the Sysinternals tool called “Process Monitor” to identify any specific processes or applications causing the error. This tool provides detailed information about the processes running on your server and can help pinpoint the source of the problem.
Enabling Remote Connections
To enable remote connections on Windows Server 2012 and fix the Remote Desktop Protocol Error 0x1104, follow these steps:
1. Open the Start menu and search for “Remote Desktop Services.” Click on the result to open the Remote Desktop Services menu.
2. In the menu, click on “Remote Desktop Session Host Configuration.” This will open a new window.
3. In the new window, click on “Connections” in the left-hand menu. Then, right-click on “RDP-Tcp” and select “Properties.”
4. In the Properties window, go to the “General” tab. Make sure the “Allow connections only from computers running Remote Desktop with Network Level Authentication” option is checked. Click “OK” to save the changes.
5. Next, go to the “Client Settings” tab. Make sure the “Enable Remote Desktop Protocol 8.0” option is checked. Click “OK” to save the changes.
6. Now, open the Windows Firewall settings. Search for “Windows Firewall” in the Start menu and click on the result.
7. In the Windows Firewall menu, click on “Advanced settings” in the left-hand menu.
8. In the Advanced settings menu, click on “Inbound Rules.” Then, scroll down and locate the rule named “Remote Desktop (TCP-In).” Right-click on it and select “Enable Rule.”
9. Lastly, make sure your antivirus or firewall software is not blocking the Remote Desktop connection. If necessary, whitelist the necessary processes or ports in your security software.
Adjusting Experience Settings and Firewall
| Adjusting Experience Settings and Firewall | |
|---|---|
| Article Title | Remote Desktop Protocol Error 0x1104 Fix for Windows Server 2012 |
| Section | Adjusting Experience Settings |
| Step | 1 |
| Description | Open Remote Desktop Connection on your Windows Server 2012. |
| Step | 2 |
| Description | Click on the “Show Options” button. |
| Step | 3 |
| Description | Navigate to the “Experience” tab. |
| Step | 4 |
| Description | Adjust the settings based on your requirements. You can choose between different experience options such as “Modem (56 Kbps)” or “LAN (10 Mbps or higher)”. |
| Section | Firewall Configuration |
| Step | 1 |
| Description | Open the Windows Firewall settings on your Windows Server 2012. |
| Step | 2 |
| Description | Click on the “Advanced settings” option. |
| Step | 3 |
| Description | Navigate to the “Inbound Rules” section. |
| Step | 4 |
| Description | Locate the “Remote Desktop (TCP-In)” rule. |
| Step | 5 |
| Description | Ensure that the rule is enabled. If not, right-click on the rule and select “Enable Rule”. |
Disabling Third-Party Security Software
To fix the Remote Desktop Protocol Error 0x1104 in Windows Server 2012, one potential solution is to disable third-party security software. This can help resolve any conflicts or compatibility issues that may be causing the error.
Here’s how to disable third-party security software on Windows Server 2012:
1. Open the Start menu and search for “Task Manager.”
2. Click on “Task Manager” to open it.
3. In the Task Manager window, click on the “More details” option if it is not already expanded.
4. Go to the “Startup” tab.
5. Look for any third-party security software entries in the list.
6. Right-click on each entry and select “Disable.”
7. Repeat this process for all third-party security software entries.
8. Once you have disabled all third-party security software, close the Task Manager.
By disabling third-party security software, you can eliminate any potential conflicts that may be causing the Remote Desktop Protocol Error 0x1104. Remember to re-enable your security software after resolving the error.
If disabling third-party security software does not fix the error, you may need to explore other solutions such as checking your network settings, updating your RDP client, or troubleshooting any firewall or antivirus configurations.
Frequently Asked Questions
What is Windows Remote Desktop internal error 0x4?
Windows Remote Desktop internal error 0x4 occurs when Remote Desktop is not enabled on the destination computer, the network connection is poor, the firewall blocks the Remote Desktop client, or the Mac computer’s operating system is outdated.
Why is my RDP not connecting?
Your RDP may not be connecting because another program could be using the RDP listener port, preventing your computer from connecting to the remote desktop gateway server. To resolve this, check the PortNumber of the RDP-Tcp of the WinStations.
How do I fix Remote Desktop error?
To fix Remote Desktop error, you can try stopping and restarting the Remote Desktop Services by following these steps:
1. Press the Win+R combination to open the Run command.
2. Type the command Services.msc and press OK.
3. In the Services (Local) console, search for Remote Desktop Services and select it.
4. Stop and then restart the Remote Desktop Services.
5. Finally, try reconnecting the RDP.
