Port 3389 Not Listening

Literally out the box and have enabled RDP for remote admin yet rdp doesn't work and "netstat -an" shows it isn't listening on 3389. Port Neches is bustling with businesses, bursting with community pride and filled with down-home friendliness. I checked the local policy and Allow logon through terminal services had the Administrators and Remote Desktop Users. How to allow TCP port 3389 on Windows Firewall, Networking & Security, Setting up a LAN or WAN, broadband connections, servers, routers and hubs. org) regarding Metasploit Community Edition. Check and even turned off the Firewall, used netstat -a and it seems to be listening on the correct port. How To Change Default Remote Desktop Protocol (RDP) port 3389 in Windows Server 2008? Requirements. For RDP penetration we are also using nmap in order to scan the targeted system (192. Having gotten this far I decided to change the listening port on that machine, which took me. The port should appear in the list and have a status of Listening. Only UDP port 1434. On the Windows 8 System the port 3389 is not listening, so I assume this is the reason. An Active Directory domain controller needs to listen on specific ports to service different client requests. 1480, and Docker version 17. Sometimes port forwarding doesn't work from WAN in iptables list I do not see any listening port number, only target host and target port. The only possible daemon is dnsmasq which is listening on port 0 or not listening on port. Change the Public Port to 8080 then (leave the private port at 3389) click the checkmark. Hi! I'm trying to run VBOX on Centos 5. following message: Connecting To Could not open connection to the host, on port 3389: C onnect failed I expected that because I know that the port is not listening. In some situations, as when you wish to obtain a more secure environment, changing the remote access port can be useful. You can then put this value into the port field when adding the. As we may see above, there were no listening UDP ports found. By default, RDP (Remote Desktop Protocol) uses port 3389 and since it’s a common port, every user has information about this port number which can lead to a security risk. Accessing the Windows 8 PC from another PC via RDC is not possible. I did a P2V in VMWARE on a Windows 2000 server which went fine. How to allow TCP port 3389 on Windows Firewall, Networking & Security, Setting up a LAN or WAN, broadband connections, servers, routers and hubs. I have not heard any compelling reason for that configuration to exist, therefore, I will not waste any further energy enabling it. To change the default port, follow the simple steps below: 1. Once done, you can try to connect to the server. I didn’t have access to vCenter (these were virtual machines) and RDP was obviously not working, which made troubleshooting difficult. Solved: How to check remote port status in windows server 2016 without telnet Telnet was always a security risk as data transfer is not secure on it. First, I have searched the forum to make sure this topic has not been covered. Solved Windows 10 Remote Desktop Mystery. NOTE: By default, RDP load balancing is not available on 3389 port for RAS Secure Client Gateway as this feature is not enabled and thus Gateway is not listening for it. It may take a minute or so for this change to take effect. Now, after a restart, the system listens on the terminal services port and all is well. View uses TCP and UDP ports for network access between its components. I have a laptop on 8. Let's assume we want to check if 3389 port is listening or not on the servers mentioned in the Servers. Situation: The client has enabled Remote Desktop on their 2008 R2 server but remote users cannot login via rdp and netstat doesn't list the port 3389. msc in the search window. I'm not very computer savvy when it comes to remote desktop but I had it working properly on windows 8. When I noticed the issue I initially thought the problem was in my router, but I have double-checked the port-forwarding settings and they are correct. on the dmz box, i can not telnet to any of those ports. Please run netstat -aonp tcp in the container itself. NOTE: By default, RDP load balancing is not available on 3389 port for RAS Secure Client Gateway as this feature is not enabled and thus Gateway is not listening for it. Arris BGW210-700 how to forward port 3389 for remote desktop RDP I set up a custom service in NAT/Gaming to forward port 3389 to my PC. If this does not work, try deleting the HTTP endpoint (80) and changing the RDP endpoint public port to 80. surface pro 4 can not open 3389 port,. 3389 (Change Terminal Server Listening Port)- you'll also need to configure your client to connect to the new port. Change the Public Port to 8080 then (leave the private port at 3389) click the checkmark. As an example, one could configure a rule with iptables that matches via source ports, e. Discover everything you need to know at business. If a component or display protocol is not in use, then the ports associated with it can be omitted. According to the information you provided earlier it is actually listening (as your devices got IP address from 10. (I have verified in the registery that the default terminal server. By default, the Windows Remote Desktop service will automatically listen to TCP port 3389. READ: netstat command not found on CentOS 7 / RHEL 7 – Quick Fix By default, xrdp service won’t start automatically after a system reboot. Home › Forums › Client Operating Systems › Windows 7 › Unable to rdp to W7 client - port not listening This topic contains 7 replies, has 6 voices, and was last updated by babulu 7 years. 1 before, but now that I'm on windows 10 it's not working anymore. on the dmz box, i can not telnet to any of those ports. However even that is not enough dynamic ports for some busy servers, so the range is usually configurable (by an administrator). exe rdesktop -g 80% 192. Here's what to do: Log in to your Sonicwall (obviously). Discussion in 'Windows Vista' started by allenle37, Oct 24, 2009. After running netstat -an, I noticed that port 3389 which is required for remote desktop connection isn’t being listened. Note: This is not a term server, just trying to use RDP. To check what port your RDP is currently listening on, use the netstat command in an elevated command prompt. To see what ports your computer actually communicates with, use netstat -an | find /i "established" d. If does not display you should be okay. The Remote Desktop by default uses TCP/IP port 3389, some people think that they can increase the security of the RDP protocol by changing it too different location. Netstat still does not show it listening on port 1433. Find the port forwarding section. Please perform the following steps: Please go to Start and click on the Search programs and files. I am running Windows Server 2016 Version 1607 OS Build 14393. WagerTalk TV: Sports Betting Picks and Tips Recommended for you. also tried to telnet to desktop2 from desktop1 and had the same result. It's just not listening on port 3389. An attacker may take help of nmap to verify whether port 3389 is activated or not. For additional information about this trio of Internet ports, please see the "Background and Additional Information" for the first port of the trio, port 137. In some situations, as when you wish to obtain a more secure environment, changing the remote access port can be useful. You can then put this value into the port field when adding the. The service you are trying to reach on the instance is not listening on that port or that network interface. You did not open the port in the security group. Rdpwrap is fully updated and says "fully supported", but Listener state is "not listening" for some reason. LocalPort" has the correct port number inside that event, but that the Server is NOT listening? And the “OnListenLost” or the “OnListenStop” event did NOT get triggered, to indicate that the Server was stopped?. Also it is good to note the command I used to list the listening port. Port 3389 won't open. Please run netstat -aonp tcp in the container itself. The service is not listening by default, but it is commonplace to enable it in corporate environments. "Connection refused" is the standard error, if the port is not open. Ensure that you allow these ports when setting up Content Analysis. I use a MacBook as my primary development machine. BTW, just to make a point. What ports need to be open for Samba to communicate with other windows/linux systems? I need to configure Linux firewall so I need the exact port TCP and UDP port numbers for SMB/CIFS networking protocol. Now armed with 2012R2 and more knowledge its simpler but lets say you are trying to connect from a linux box using one of the open source WinRM ports, there are several gotchas. Warning The Remote Assistance feature in Microsoft Windows XP may not work correctly if you change the listening port. I do not have an answer, but I can tell you that ssh port forwarding is working for me under Mavericks. It turns out that there was a problem with the RDP-tcp protocol not working because it was configured to listen on all available network adapters. It's just not listening on port 3389. 13 and there is no PC at 192. These are just a few of the port numbers Oracle uses in networking. So it's highly recommended to change the listening port for Remote Desktop Connection and to do so follow the below-listed steps. While TCP/3389 is the standard RDP port, WHS doesn't use it (at least, not for Console functionality, or for remote RDP. The Port Jefferson Free Library is a Passport Acceptance Facility! We provide the same level of service as other Passport Acceptance Facilities for all U. on the dmz box, i can not telnet to any of those ports. LocalPort" has the correct port number inside that event, but that the Server is NOT listening? And the “OnListenLost” or the “OnListenStop” event did NOT get triggered, to indicate that the Server was stopped?. If you read my post on Netscaler Version 11 you would know I had to close that case after resolving the issue myself. 0 (Note that 0. In addition, SQL Server Express only listens for connection on localhost. Correct Answer: 3389 Question 17 0 out of 1 points When using static IP addressing, software automatically configures the network connection on each device. Windows 10: RDP port 3389 stopped listening. The Remote Desktop protocol (RDP) is a built-in feature in Windows 8 Pro and use standard TCP port 3389 by default. List All Listening Ports. I have checked Terminal. dnsmasq config :. Learn vocabulary, terms, and more with flashcards, games, and other study tools. Use a 4G connection from your phone to get your PC/laptop online. Restarted and I could not connect. 1 and another rule that allows access to TCP port 3389 from everyone, everyone has access to TCP port 3389. How to enable the Telnet Client in Windows 10. Since even with a firewall in place my computer is still listening to the remote desktop port (3389), all we need to do is to configure the firewall to allow that port through. If you can see a device has been discovered and is being counted on the Dashboard Graph and also appears in the Report for that day, but does not show on the Devices list page of Open-AudIT, make sure the "status" of the device has not been set to something other than 'production'. 100) is listening on ports TCP 80, 443 and 3389; My firewall only permits TCP 80, 443, 135 and 445 (not 3389). Port forwarding can also be used to forward a port from an external address of a network card to a virtual machine port running on the same computer. 0/24 network when you disable/ disconnect the other WAN. Ask Question Asked 7 years, 3 months ago. Changing the listening port will help to "hide" Remote Desktop from hackers who are constantly scanning the network for computers listening on the default Remote Desktop port (TCP 3389). To enable RDP on your Windows Server 2012, you can click here for more information. Here I’m sharing the steps. 0:3389 in the Local Address column to make sure the port is open. You should have success. Net and be up in 30 seconds or less. Port scanning is the process of sending packets to TCP and UDP ports on the target system to determine what services are running or are in a LISTENING state. You can change that listening port on Windows computers by modifying the registry. * The Terminal Services service is started. 1, we can’t connect remote desktop easily because of the default security settings. 1 post published by nwleaphart during August 2011. Troubleshooting Remote Desktop connections (or lack thereof) as well as telnet into carious other ports (17, 19, 7, but not 445 or 3389) you've confirmed that the target system is. This is even before installing the connector. I am running Windows Server 2016 Version 1607 OS Build 14393. Just_Curious_Dude. Solved Windows 10 Remote Desktop Mystery. This blog post will. As long as you have the right to use the Remote Desktop client and as long as you do not have firewall blocking the port 3389 to the remote server, you could use this option to connect to a remote server. So I tried putting it back to 3389 and its broken now too. The Windows firewall is turned off. You do not have to open these ports for access by other machines; however, you should be aware that ArcGIS Server is using them in case you run other applications that require the same ports. When it comes to Windows 7 and later Operating Systems such as Windows 10 and 8. -a: Displays all connections and listening ports. Unity is not currently supported. Now, after a restart, the system listens on the terminal services port and all is well. Find the port forwarding section. You can specify a comma-separated list of ports or ranges of ports. the service fails to load properly and the computer is not listening on port 3389 for RDP connections. Attention! TCP guarantees delivery of data packets on port 464 in the same order in which they were sent. If your system has Remote Desktop enabled, it is listening for connections on port 3389. Can you successfully use telnet localhost 3389. Accessing the Windows 8 PC from another PC via RDC is not possible. Accessing the Windows 8 PC from another PC via RDC is not possible. -a: Displays all connections and listening ports. Let's assume we want to check if 3389 port is listening or not on the servers mentioned in the Servers. The port number for RDP was not designed to be changed, and the only way to do so is through editing registry. I wasn't able to make remote desktop connection to my fresh installation of Windows 8. 2 + firewalld + squid. The issue due to some fellow from a different forum is that Autoit network functions use *BLOCKING* ports. Example: Port 3389 is closed / not listening 1. Go to Start, search on services or services. Also, there were cases when in Windows Server 2012 R2 the port forwarding rules worked only until the system was rebooted, and after restart they were reset. Since Host B is not listening. For the sake of this example My host (192. I can telnet to it on 3389 (from my workstation) and it connects. local -Port 3389 -InformationLevel Quiet WARNING: TCP connect to (192. Open regedit on the problem server. 1 and another rule that allows access to TCP port 3389 from everyone, everyone has access to TCP port 3389. The Windows firewall is turned off. Troubleshooting Remote Desktop connections (or lack thereof) as well as telnet into carious other ports (17, 19, 7, but not 445 or 3389) you've confirmed that the target system is. In some situations, as when you wish to obtain a more secure environment, changing the remote access port can be useful. You can specify a comma-separated list of ports or ranges of ports. Just_Curious_Dude. I think you'll want to do TCP, or both. -r [target host] is the our targeted system's IP or hostname. Look for 0. Try the connection from your computer again. The problem with the default was that my office network will not go out on 5900. Thread Status: Not open for further replies. Entered the command netstat -aon on a cmd prompt to verify if the RDP indeed was open and listening on the configured RDP port, TCP port 3389 by default. LocalPort" has the correct port number inside that event, but that the Server is NOT listening? And the “OnListenLost” or the “OnListenStop” event did NOT get triggered, to indicate that the Server was stopped?. Edit2 Found a similar thread here and the suggestion it may be caused by: KB2830477. Warning The Remote Assistance feature in Microsoft Windows XP may not work correctly if you change the listening port. You can also test by telneting to localhost or 127. 1, you won't be able to monitor it with PRTG. "Connection refused" is the standard error, if the port is not open. , this port is not listening on the target system or the access to it is restricted by a firewall or some system settings. Now, after a restart, the system listens on the terminal services port and all is well. I checked the registry on desktop2 and it is set to listen on 3389 can you please suggest what else I can try?. A yellow circle in the bottom right corner of your main Bitcomet interface will confirm this to be the case. The port can be changed either in the Display settings of the graphical user interface or with the --vrdeport option of the VBoxManage modifyvm command. I have two other Windows 7 PC's where RDC is working fine. 1 and another rule that allows access to TCP port 3389 from everyone, everyone has access to TCP port 3389. If you change the default ports after installation, you must manually reconfigure Windows firewall rules to allow access. You should receive a response of LISTENING. exe" on "TermService". I then performed telnet localhost 3389 and noticed that port is not listening. Discussion in 'Windows Vista' started by allenle37, Oct 24, 2009. No firewall running on the server. How to Change MongoDB Default Listening Port (27017) Changing the port in which MongoDB listens is a good way to hide your server from spiders, crawlers and automated attacks. Within the network, each computer uses the default listening port (3389), so all I have to do is type the internal IP address of the computer I wish to co. These days 1024. • If VMware vRealize® Operations for Horizon is not deployed, ports to and from it can be ignored. Windows 10: RDP port 3389 stopped listening. Note: This is not a term server, just trying to use RDP. Connection Tracking. Hello, Thank you for rdpwrap! Unfortunately, on Windows 10 Home edition, it is not working anymore since Insider build 15002. If your firewall doesn't allow you to specify the type of port, configuring one type of port probably configures the other. XP Home Remote Desktop port 3389 not listening. This article provides an overview of ports that are used by Citrix components and must be considered as part of Virtual Computing architecture, especially if communication traffic traverses network components such as firewalls or proxy servers where ports must be opened to ensure communication flow. The issue is that I can connect to the Win 7 computer but not to the Win 10 computer. This does not appear to work for Win 10 version 1809. TCP port 3389 (ms-wbt-server service): NOT LISTENING If it does reconfigure each of your three PCs to use the default listening port, ie. Look for 0. I do see the forwarder listening on port 8089, just no data flowing. Some users are experiencing problems though because this port has been blocked in their firewall or by their ISP. For example, if you have a rule that allows access to TCP port 3389 (RDP) from IP address 203. following message: Connecting To Could not open connection to the host, on port 3389: C onnect failed I expected that because I know that the port is not listening. I can not establish "remote desktop" connection with my desktop computer because the port 3389 on it does not want. Manage Windows Firewall from Command Prompt. If you have ever worked in an environment with multiple Windows servers to manage, you know how useful Microsoft's Remote Desktop, aka Terminal Server client, is. An Active Directory domain controller needs to listen on specific ports to service different client requests. Does it just not listen on that port anymore? How can I make netstat show me if it is listening ?. The default port for SQL Express may not be 1433. LocalPort" has the correct port number inside that event, but that the Server is NOT listening? And the “OnListenLost” or the “OnListenStop” event did NOT get triggered, to indicate that the Server was stopped?. Port forwarding can sometimes be a rather big pain in the butt. Now, tracing back my steps, I figured that the last change I did on the servers was to uninstall XenApp 6. Testing Network Services with netcat. This article explains how to change the RDP port on a Windows Hosting Server. To accomplish this, you need to use the script mentioned below:. Also look at "netstat -an" output for listening port 3389. Unity is not currently supported. I came across an issue with my server not listening on 3389 for terminal server access after the last update bombed the computer. I want to understand why NMAP decides to tell me that a specific port is "FILTERED" when there are technically over 60,000 "filtered" ports. Port 3389 is definitely NOT listening or established. There is no support available natively on Windows Computers or there is no command line tool available to check if a specific port is listening on multiple computers or not. Even after the TermService service is enabled, the system is still not listening to port 3389. It could be blocked by a firewall, listening on another port, etc. Assuming you've got all listeners at 5900, 5901, and 3389, everything should be good to go - you can connect to the VNC servers directly with a VNC client, or you can use an RDP client to connect to xrdp, which will give you a drop-down menu to select Active Local Login or Clean Session. msc in the search window. has the selected port in the registry. Open a command prompt window as Administrator (not PowerShell) Run the following command, pasting your new certificate’s thumbprint into the command (all on one line):. Ports that are left open for no reason are a security risk that can be exploited by malicious programs and viruses. Sometimes the wireless networks only allows 80, and 443 ports to connect and blocks others, or you want to increase the security, the solution is to use different location. Changing the RDP listening port on Windows Server. We can use tasklist and taskkill commands for this. 3389 | 3389 port | 33896 county | 33897 county | 33896 zip code | 33897 zip code | 33897 time | 3389 rdp | 33898 zip code | 338906 flame sensor | 3389rd | 33893. I CAN connect to other PC’s in the network via RD without any problem. If turned off, the services will stop and the ports will be closed. As long as you have the right to use the Remote Desktop client and as long as you do not have firewall blocking the port 3389 to the remote server, you could use this option to connect to a remote server. TCP port 53 (domain service): LISTENING UDP port 53 (domain service): LISTENING. WAP functions as a reverse proxy and an Active Directory Federation Services [AD FS] proxy to pre-authenticate user access. When I run the Config tool everything is green except the listener state which says "not listening". Port numbers range from 0 to 65535, but only port numbers 0 to 1023 are reserved for privileged services and designated as well-known ports. How to Close Port 445 in Windows 10/7/XP? Since it is one of the most dangerous ports on the Internet and made way for WannaCry attack, close it becomes urgent. If you do not have a server already, why not consider a Windows Cloud Hosting from Atlantic. As a last step, we set remote desktop security layer to "negotiate". Citizens at a convenient location. 1-20130713-NIGHTLY-evita. How To Change Default Remote Desktop Protocol (RDP) port 3389 in Windows Server 2008? Requirements. This means the TCP port 445 is opened. In your case where a server not answering on port 3389 is deemed a problem, you may be able to skip the ping. I checked the registry on desktop2 and it is set to listen on 3389 can you please suggest what else I can try?. Situation: The client has enabled Remote Desktop on their 2008 R2 server but remote users cannot login via rdp and netstat doesn't list the port 3389. 67 ()Location: Scottsdale United States ()Registed: 2009-10-16 (10 years, 14 days) Ping: 61 ms; HostName: ip-184-168-221-67. Ensure that you allow these ports when setting up Content Analysis. Find the port forwarding section. I did a P2V in VMWARE on a Windows 2000 server which went fine. Port forwarding stopped working on R7000 I have two Nighthawk R7000 routers, one at home and the other in my office, both running latest firmware V1. For additional information about this trio of Internet ports, please see the "Background and Additional Information" for the first port of the trio, port 137. It's easy to dismiss the notion that a firewall could contribute to a remote desktop not working, but it's actually quite common. We were not able to enable it, so we uninstalled it and rebooted. netstat -abo. How To Open Port 3389 Windows 10. I have tried everything I can think of. Change the Public Port to 8080 then (leave the private port at 3389) click the checkmark. Hi Guys, I know this most likely won't be on the test but in the spirit of gaining a well-rounded grasp of networking fundamentals Can someone please explain how ports 20 and 21 are used in a typical FTP session/transaction? It's my uderstanding that server transactions are initiated on port 21 and port 20 is kepts closed until a val. C:\>netstat -a | find "3389" C:\> Fortunately, one can use reg commands to configure remote desktop support through the Windows registry from a command prompt. UDP port 464 would not have guaranteed communication as TCP. using tcpdump, I never see port 8089 used. Ask Question Asked 7 years, 3 months ago. However, the server is not listening on that port. Yep, you've specified VBR-01 server to serve as vPower NFS server while creating the repository on it (according to the screenshot in you original post). Neither on bhyve windows guest is listening at port 53. Home › Forums › Client Operating Systems › Windows 7 › Unable to rdp to W7 client – port not listening This topic contains 7 replies, has 6 voices, and was last updated by babulu 7 years. Now, tracing back my steps, I figured that the last change I did on the servers was to uninstall XenApp 6. VRDP now seems to be listening on IPv6 and IPv4 by default; one can connect to either port. CSlistener". I have tried everything I can think of. The first was to display all the active TCP and UDP ports on which the computer was listening and then find the string 3389 which is the default RDP port number, the second command displays information about Remote Desktop sessions on a server. This being a proxy server, it had internal and dmz network adapters. Are you sure the IIS web server is running and listening inside the container itself. This article provides an overview of ports that are used by Citrix components and must be considered as part of Virtual Computing architecture, especially if communication traffic traverses network components such as firewalls or proxy servers where ports must be opened to ensure communication flow. You'll see port 3389 bound to "svchost. 0:3389 in the Local Address column to make sure the port is open. To see all established connections and not just the listening one, we can add an “a” parameter to the command line. To check what port your RDP is currently listening on, use the netstat command in an elevated command prompt. To view which ports are listening (open) on a local host using netstat, from the command prompt type the following:. Users mostly ask for to check if ASA is allowing specfic port or not. Active 7 years, Remote desktop is not working - no port 3389 is bound. Hi When I deploy Windows 2016 server in a domain for the sake of installing the connector on it, I find that the Windows 2016 server is not listening on port 80. Enabling an additional port is recommended over changing the existing port. Then the port 3389 stopped listening for a connection. The use of non-default FTP server ports is more common than for other protocols due to the historic trouble with malicious hackers searching for FTP servers on port 21. Today I found an easy way to check which application is using which port in my system. 3389 | 3389 port | 33896 county | 33897 county | 33896 zip code | 33897 zip code | 33897 time | 3389 rdp | 33898 zip code | 338906 flame sensor | 3389rd | 33893. Look for 0. Any ideas on getting port 3389 running on my server? and yes the Terminal Services srvice is running??? Thanks, Ralph R. 06, and I'd like to run x11vnc on it. If not, then you have not configured the router correctly or the firewall etc. Open regedit on the problem server. This happens only when port 445 is not found to be protected by NAT. If I use a port checker program online to check port 25 it says it's listening. Click the Settings link. How to Close Port 445 in Windows 10/7/XP? Since it is one of the most dangerous ports on the Internet and made way for WannaCry attack, close it becomes urgent. To check what port your RDP is currently listening on, use the netstat command in an elevated command prompt. Hi When I deploy Windows 2016 server in a domain for the sake of installing the connector on it, I find that the Windows 2016 server is not listening on port 80. exe process and then open a command prompt and type. If the port shows to be FILTERED then a firewall or VLAN could be blocking that port, if the port returns NOT LISTENING then we got to the machine but the. What can I do now, apart from a complete re-installation or repair of XP, neither of which I want to do?. vPower NFS datastore that you see already mounted to the host is a different datastore, configured on your default backup repository (which is installed as a part of Veeam B&R installation on the backup server itself, VBRS-01). It’s also the easiest way to add port exceptions for services such as HTTP, file sharing, software applications, and more. Identify the ports used by Worry-Free Business Security Services (WFBS-SVC) to communicate with the server. The Windows firewall is turned off. Attention! TCP guarantees delivery of data packets on port 464 in the same order in which they were sent. This article provides an overview of ports that are used by Citrix components and must be considered as part of Virtual Computing architecture, especially if communication traffic traverses network components such as firewalls or proxy servers where ports must be opened to ensure communication flow. There are three methods to disable port 445 in Windows 10, 7 and XP in total. Correct Answer: 3389 Question 17 0 out of 1 points When using static IP addressing, software automatically configures the network connection on each device. Remote Desktop Protocol is available for several versions of Microsoft Windows as well as some. Resolved: Port 3389 is not being listened on Windows 8 Resolved: Port 3389 is not being listened on Windows 8 « port135. Open a command prompt and run the following command to validate there is an application listening on the probe port: netstat -an; If the port state is not listed as LISTENING, configure the proper port. Question: Change Remote Desktop RDP Port. Click the Settings link. This is a discussion on Port 3389 won't open within the Protocols and Routing forums, part of the Tech Support Forum category. The Google returns many, many results for a search like "port 3389 not listening", although not that many (yet) for Windows 10. I then performed telnet localhost 3389 and noticed that port is not listening. (I have verified in the registery that the default terminal server. 0 means all possible IP address, only ipv4). For example, if my public IP was 123. It may take a minute or so for this change to take effect.