Код ошибки 1104

  • Remove From My Forums

locked

because of a protocol error detected at the client(code 0x1104), this session will be disconnected — only for particular connections from desktop to server

  • Question

  • I meet this error only on my laptop connecting to 2 particular Windows 2008 server. Below is the scenario

    1. I used my laptop Windows 7

    2. I am trying to connect to Windows 2008 R2 server via Remote Desktop Connection.

    I got this error:

    because of a protocol error detected at the client(code 0x1104), this session will be disconnected

    Important thing:

    1. I can connect to other Windows 2008 R2 servers with Remote Desktop Connection successfully. Only 2 servers cannot connect.

    2. For those 2 servers, if I use another Windows 7 to connect, this also has no issue

    That means:

    Only my laptop connecting to 2 particular Windows 2008 servers have this problem

    So my RDP client side is working -because it can connect other Windows VMs

    The 2 servers are also working — because it can be connected via another client

    Please help me! Thank you very much

Answers

    • Proposed as answer by

      Friday, May 20, 2016 4:38 AM

    • Marked as answer by
      Kate LiMicrosoft employee
      Friday, May 20, 2016 4:38 AM

  • Hi,

    I want to confirm that were there any changes made on the computer prior to the issue? Is the computer on a Domain?

    The reason you may be receiving this error might be due to a protocol error of conflicting Visual styles between the computers having Remote Desktop Connection.

    On the remote computer you will have to find a compatible visual style that works with RDP in case of a custom style set or conflict.

    Please try unchecking the option Visual Styles and check if you are able to use the Remote Desktop Connection:

    a. Click Start.

    b. Launch Remote Desktop Connection (RDP).

    c. Click on Options on the RDP window.

    d. Click on the Experience tab.

    e. Uncheck the Visual Styles option.

    f. Try starting the RDP process and check if you are able to connect.

    Best Regards,

    Tao

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    • Proposed as answer by
      Tony_Tao
      Tuesday, May 17, 2016 7:48 AM
    • Marked as answer by
      Kate LiMicrosoft employee
      Friday, May 20, 2016 4:38 AM

Источник
  • Remove From My Forums

  • Question

  • Hi,

    Have a Windows Server 2003 SP2 with latest patches and updates. The remote access to the server no longer works.

    I noticed that the PortNumber value of the HKLM\SYSTEM\ControlSet001\Control\Terminal Server\WinStations\RDP-Tcp had been changed from 3389 to 3399.

    I changed it back to 3389 and rebooted the machine. It worked for a day os so then stopped working.

    I then noticed that the port number had been changed to 2288.

    I changed it back to 3389 and even though this value remains unchanged, a remote connection no longer works and I get a messge (Beacuse od protocol error detected on the remote client (code 0x1104), this session was disconnected. (Roughly ttranslated from
    French).

    Have the same error from different PCs on the LAN or via a VPN connection.

    If I do a «telnet servername 3389» I get a message [hieroglyphics..
    http://www.youngzsoft.com/cn/.

    A «netstat -no» indicates that the server is connected to 117.26.176.35, 117.26.180.162 and 120.40.251.213 via different ports.

    I suspect there is trojan installed but how do I go about detecting it and removing it.

    An antivirus scan did not detect anything.

    • Moved by

      Tuesday, February 15, 2011 4:54 PM
      (From:Windows Server 2003 (et versions anterieures: Windows Server 2000, Windows NT Server))

Answers

  • Hi,

    Here are some other reasons that may apply:

    Case 1: The terminal server is running an application that using the same port as the TS.

    Case 2: The server comes with two NICs and each of them has default gateway. That messes the routing table. No computer should have two default gates.

    Case 3: The client has XP\Win 7 as Remote Host with DHCP setup. The remote client may receive this error when the Remote host IP changes.

    Case 4: I had this problem when I moved a server from a location to another.
    My 2003 server has got two NIC and I used one for the first location and the
    other for the second location. When I tried to connect with RDP to this server I found this problem. Looking for a solution in Terminal Services Configuration, I’ve founded it by authorizing the second Nic to be used for RDP.

    Case 5: Some software may changes the port #. You can disable the antivirus software and change the port to 3389 to see whether the issue still exists.

    • Proposed as answer by
      Yuan WangMicrosoft employee
      Wednesday, February 16, 2011 7:46 AM
    • Marked as answer by
      Yuan WangMicrosoft employee
      Saturday, February 19, 2011 9:46 AM

  • I had to reinstall the server. Not even Microsoft could find a solution. The server just go worse and worse as a result of the viral attack.

    • Marked as answer by
      lenmor
      Thursday, May 24, 2012 6:38 PM

Источник

How to fix the issue reported by error code «Error 1104»

Special Offer

Outbyte PC Repair

Windows 11, 10, 8, 7

Trusted and Monitored

The following steps should fix the Error 1104 issue:

  • Step 1.


    Download Outbyte PC Repair application


    See more information about Outbyte; uninstall instructions; EULA; Privacy Policy.
  • Step 2.
    Install and launch the application
  • Step 3.
    Click the Scan Now button to detect issues and abnormalities
  • Step 4.
    Click the Repair All button to fix the issues
Compatibility Win 11, 10, 8, 7
Download Size 21.2 MB
Requirements 300 MHz Processor, 256 MB RAM, 50 MB HDD space

Limitations: trial version offers an unlimited number of scans, backups and restores of your Windows system elements for free. Registration for the full version starts from USD 29.95.

A malfunction reported by error code «Error 1104» may happen due to a number of different factors. Common causes include incorrectly configured system settings or irregular entries in the system elements, to name a few. Such issues may be resolved with special software that repairs system elements and tunes system settings to restore stability.

The article provides details on what the issue means, potential causes, and ways to resolve the issue.

  • 1
    Ways to repair error code «Error 1104»

  • 2
    Meaning of error code «Error 1104»

  • 3
    Causes of error code «Error 1104»

Ways to repair error code «Error 1104»

Advanced PC users may be able to repair the issue with this code by manually editing system elements, while other users may want to hire a technician to do it for them. However, since any manipulations with Windows system elements carry a risk of rendering the operating system unbootable, whenever a user is in any doubt of their technical skills or knowledge, they should use a special type of software that is meant to repair Windows system elements without requiring any special skills from the user.

The following steps should help fix the issue:

  • Download Outbyte PC Repair application

    Special offer. See more information about Outbyte; uninstall instructions; EULA; Privacy Policy.
  • Install and launch the application
  • Click the Scan Now button to detect potential issue causes
  • Click the Repair All button to fix detected abnormalities

The same application can be used to run preventative measures to reduce the chance of this or other system issues appearing in the future.

Meaning of error code «Error 1104»

Error code «Error 1104» is an issue name that contains details of the malfunction, including why it occurred, which system component or application malfunctioned, along with some other information. The numerical code in the issue name usually contains data that can be deciphered by the manufacturer of the component or application that malfunctioned. The issue with this code may occur in different locations within the system, so even though it carries some details in its name, it is still difficult for a user to pinpoint and fix the issue cause without specific technical knowledge or appropriate software.

Causes of error code «Error 1104»

If you have received this warning on your PC, it means that there was a malfunction in your system operation. Error code «Error 1104» is one of the issues that users may get as a result of incorrect or failed installation or uninstallation of software that may have left invalid entries in system elements. Other potential causes may include improper system shutdown, such as due to a power failure, someone with little technical knowledge accidentally deleting a necessary system file or system element entry, as well as a number of other factors.

Источник

Updated on 2022-08-14 GMT+08:00

Symptom

The system displays an error message indicating that a protocol error (code: 0x1104) is detected when you use MSTSC to access an ECS running Windows Server 2008.

Figure 1 Protocol error (code: 0x1104)

Possible Causes

  • Port 3389 of the security group on the ECS is disabled.
  • The firewall on the ECS is disabled.
  • Port 3389 on the ECS is used by other processes.
  • The Remote Desktop Session Host is incorrectly configured.

Solution

  1. Check security group settings.

    Check whether port 3389 is allowed in inbound direction. If it is allowed, go to 2.

  2. Check whether the firewall is disabled:
    1. Log in to the Windows ECS.
    2. Click the Windows icon in the lower left corner of the desktop and choose Control Panel > Windows Firewall.

    3. Click Turn Windows Firewall on or off.

      View and set the firewall status.

    If the firewall is enabled, go to 3.

  3. Log in to the ECS using VNC and check the port.
    1. Open the cmd window and run the following command:

      netstat -ano |findstr: 3389

      Figure 2 Checking port 3389

      As shown in Figure 2, port 3389 is used by the process with ID of 4.

    2. Open Task Manager and find the process with ID of 4 is the System process.
    3. Generally, the IIS and SQL Server run as the System process. Run the following HTTP command for further check.

      netsh http show servicestate

      Figure 3 Checking System process

    4. If port 3389 is used by HTTP protocols, it indicates that the port is used by IIS.
    5. Enter http://127.0.0.1:3389 in the address box of the browser and press Enter. Check whether the website can be visited normally.
    6. Change the port used by IIS and restart IIS.
  4. If no error occurs during the preceding steps, go to step 5 to check whether error 0x1104 is caused by the configuration of Remote Desktop Session Host.
  5. Check the remote desktop session host configuration.
    1. Log in to the ECS using VNC.
    2. Open the cmd window and enter gpedit.msc.
    3. Click OK to start Local Group Policy Editor.
    4. Choose Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services.

      Figure 4 Remote Desktop Services

    5. Remote Desktop Session Host > Security.

      Figure 5 Remote (RDP) Connection requires the use of the specified security layer

    6. Set Require use of specific security layer for remote (RDP) connections to Enabled and Security layer to RDP.

      Figure 6 Setting security layer

    7. Click OK.
    8. After the configuration is complete, open the cmd window.
    9. Run the following command to update the group policy:

      gpupdate

      Figure 7 Updating the group policy

Remote Login Errors on Windows
FAQs

more

Источник

Search code, repositories, users, issues, pull requests…

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Источник

Понравилась статья? Поделить с друзьями:
  • Код ошибки 11036
  • Код ошибки 1100 агробанк
  • Код ошибки 1102 при проверке оперативной памяти
  • Код ошибки 1102 хонда
  • Код ошибки 11001 lost ark