Seems Microsoft has documented this behavior: I'm not certain as to why the system is choosing which pool but it are running on high ports (49152-65535) but on others they seem to be running on low ports 1024-5000. On some systems the lsass, wininit, spoolsv, etc. If I block some of them, it slows down the connection process, in particular the 1535 & 1537 ones, where it gets stuck on "Securing Remote Connection." for some time. I am OK with the ports not in bold, but would someone please be able to explain to me what the ports in bold are? (X -> Y : TCP 123 means that the host X sends a packet to host Y on port 123) Here are the ports I have identified as potentially being used when a client tries to login to a remote desktop. I have checked this link: but not all ports I monitored are mentioned here. (Let's call it RDSH) NLA authentication is also enforced. I have a server that acts as the Web Access, Licensing and Broker server (Let's call it RDWLB), another server that acts as the AD DC (Let's call it DC), and another as the RD session host. My servers are all running on Windows Server 2016 Datacenter, and my clients are on Windows 10 Professional. I have a Microsoft Remote Desktop Services deployment in my company that is now configured, however I am still struggling with the firewall ports to open, and there seems to be no documentation on the web talking about it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |