Windows 10: Cannot open Port 3389 RDP

Discus and support Cannot open Port 3389 RDP in AntiVirus, Firewalls and System Security to solve the problem; 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... Discussion in 'AntiVirus, Firewalls and System Security' started by DougWebb1, Mar 16, 2019.

  1. DOUGWEBB1
    DougWebb1 Win User

    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, Advanced Settings, Inbound Rules a Port 3389, Domain, Private, Public are checked.

    But 3389 is NOT visible at CMD prompt.

    What next?

    Need it as this will be a Remote computer, I hope.

    Thanks in advance.

    :)
     
    DougWebb1, Mar 16, 2019
    #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 16, 2019
    #2
  3. 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 16, 2019
    #3
  4. JENNIFER CHA
    Jennifer Cha Win User

    Cannot open Port 3389 RDP

    RDP Not working with port 3389

    Hi,

    Based on the details that you have provided, we'd like to recommend another support channel where you can get best practices and advanced troubleshooting from IT Pros and active community members. To visit the
    Microsoft TechNet forum, click this link.

    Feel free to reach out if you have other concerns.

    Kind regards.
     
    Jennifer Cha, Mar 16, 2019
    #4
Thema:

Cannot open Port 3389 RDP

Loading...

  1. Cannot open Port 3389 RDP - Similar Threads - Cannot open Port

  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. Cannot open ports no matter what.

    in Windows 10 Gaming
    Cannot open ports no matter what.: I am simply trying to open port 21, or any port for that matter on COX cable. I was told by cox that since its business internet, they don't block any ports at all on their end. I set up a simple FTP server, set port 21 in the firewall and forwarded the ports on my linksys...

  5. Cannot open the com port

    in Windows 10 Support
    Cannot open the com port: I am using the program STM32Flasher from this link: FLASHER-STM32 - STM32 Flash loader demonstrator (UM0462) (replaced by STM32CubeProgrammer) - STMicroelectronics When I run it, it correctly finds the only used com port. But when I click Next, I always get the error "cannot...

  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. 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

  10. RDP port 3389 stopped listening.

    in Windows 10 Network and Sharing
    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. 43603