Windows 10: RDP port 3389 stopped listening.

Discus and support RDP port 3389 stopped listening. in Windows 10 Network and Sharing to solve the problem; RDP port 3389 just stopped listening after some of the updates, netstat -an command doesn't list it. Remote Desktop Service is displayed as Running,... Discussion in 'Windows 10 Network and Sharing' started by Gwynbleidd, Mar 9, 2016.

  1. GWYNBLEIDD
    Gwynbleidd Win User

    RDP port 3389 stopped listening.


    RDP port 3389 just stopped listening after some of the updates, netstat -an command doesn't list it.
    Remote Desktop Service is displayed as Running, but Event Viewer has following error:

    Remote Desktop Service start failed. The relevant status code was 0x80070721.

    :)
     
    Gwynbleidd, Mar 9, 2016
    #1
  2. IBAKEDPOTATO
    IBakedPotato Win User

    RDP Not working with port 3389

    So I have a tp-link router and I port forwarded port 3389 to my ip address. I port forwarded the ipv4 found in network and sharing center. I checked to see if the port was open at canyouseeme.org but it said the port was closed and I was not able to change
    the ip it was looking for to the one in network and sharing center. I opened port 3389 in Kaspersky and enabled RDP in Windows Firewall.

    Anyone have any suggestions?
     
    IBakedPotato, Mar 9, 2016
    #2
  3. ALEXZ1981
    AlexZ1981 Win User
    RDP stopped working after Windows 10 upgrade

    Hello, I have upgraded to Windows 10 Pro from 8.1 Pro some days ago. And Remote Desktop connection stoppped working. I have checked all firewall rules. But figured out, that RDP port 3389 just not listened. netstat command show nothing. Remote Desktop
    service shows it's running, but port is closed.

    I'd appreciate for any help.
     
    AlexZ1981, Mar 9, 2016
    #3
Thema:

RDP port 3389 stopped listening.

Loading...

  1. RDP port 3389 stopped listening. - Similar Threads - RDP port 3389

  2. RDP Self Signed Certificate 3389 Remote Desktop Protocol

    in Windows 10 Gaming
    RDP Self Signed Certificate 3389 Remote Desktop Protocol: Tenable Nessus Scans showing self signed cert used for RDP on port 3389.Done my due diligence - 1. Cert is located in certlm.msc > Remote Desktop2. You can create a custom template and generate a cert to be used for RDP and put in that folder3. Deleting the self signed - it...

  3. RDP Self Signed Certificate 3389 Remote Desktop Protocol

    in Windows 10 Software and Apps
    RDP Self Signed Certificate 3389 Remote Desktop Protocol: Tenable Nessus Scans showing self signed cert used for RDP on port 3389.Done my due diligence - 1. Cert is located in certlm.msc > Remote Desktop2. You can create a custom template and generate a cert to be used for RDP and put in that folder3. Deleting the self signed - it...

  4. Configure winrm on multiple port listeners

    in Windows 10 Gaming
    Configure winrm on multiple port listeners: Configure winrm on multiple port listeners https://answers.microsoft.com/en-us/windows/forum/all/configure-winrm-on-multiple-port-listeners/3083ad09-5c46-44b1-96c3-109f5ec709cd

  5. Cortana stops listening

    in Cortana
    Cortana stops listening: Hi, I have a Dell Inspiron laptop with Windows 10 64 bit. All Windows updates are in place. Problem is that Cortana stops listening after a fraction of a second and says that she did not hear anything. Microphone works OK with Zoom and other programs. Regards, Barry...

  6. Remote Desktop not working - Not listening to port 3389

    in Windows 10 Network and Sharing
    Remote Desktop not working - Not listening to port 3389: I have a PC that is a host to our database. It has Windows 10 Pro on it. I am attempting to use Remote Desktop RD. I have disabled firewall and configured router for port 3389. When I use a port checker, it times out. Appears that the PC is not listening to the port. I...

  7. Port 3389 Process Cloning Malware Turned off Defender

    in AntiVirus, Firewalls and System Security
    Port 3389 Process Cloning Malware Turned off Defender: Whatever I have is using the Terminal Services RDP vulnerability. When NLA was activated the malware tried sending a MS fax with the Authentication credentials. It clones and replaces legitimate Windows processes and it was running as System 32. Copies your windows folder,...

  8. Block TCP Port 3389

    in Windows 10 Network and Sharing
    Block TCP Port 3389: How Block Port 3389 ? Thanks https://answers.microsoft.com/en-us/windows/forum/all/block-tcp-port-3389/de6fb848-5a1b-4c07-bc59-28f1ddb2341b

  9. Cannot open Port 3389 RDP

    in AntiVirus, Firewalls and System Security
    Cannot open Port 3389 RDP: I have a new Win10 Home edition, McAfee LiveSafe V16. I have opened Port 3389 within McAfee, added check to Port 3389 and Port 135 as well as added add'l Port 3390 and 3389 to it. When I use netstat -an. I do NOT see Port 3389 listed. I have added to Control Panel,...

  10. How to change RDP Port

    in Windows 10 Network and Sharing
    How to change RDP Port: How to change RDP Port, from 3389 to another port. https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/how-to-change-rdp-port/43fbb04d-6191-4bcb-beb9-75dc4d27f1ee

Users found this page by searching for:

  1. rdp not listening on 3389 windows 2016

    ,

  2. service running but 3389 not listened

    ,

  3. RDP not listening 3389 windows 2016

    ,
  4. windows 10 1803 rdp stops listening