This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(115.19999999999999, 42%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGI%3C/text%3E%3C/svg%3E)
I tried to connect from Windows Server 2016 to Windows Server 2019 via mmc to see remote Taskscheduler and diskmgmt.
Connection failed
And Get-NetTCPConnection -remoteaddress <ip> shown something like this
for taskscheduler
for diskmgmt
Never seen mmc to use such ports before
So what are they used for and why mmc started to use them?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi,
I also get the right ports range in my lab:
Try to restart machine and connect via MMC again, see whether the issue still occur.
Best Regards,
Candy
--------------------------------------------------------------
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
hm, I've restarted it already a couple of times. The issure still occures.
If there is still no progress, I would also suggest you contact Microsoft Customer Support and Services where more in-depth investigation can be done so that you would get a more satisfying explanation and solution to this issue.
Here is the link:
https://support.microsoft.com/en-us/gp/customer-service-phone-numbers
Hi @Grey Ink ,
Edit: Remote management via the Microsoft Management Console (MMC) and other legacy management tools use DCOM ports, by default DCOM assigns ports dynamically from the TCP port range of 1024 through 65535 on older systems, on newer 49152 to 65535.
When it's dynamic it could be anything in between and therefore the port used might be different sometimes.
----------
(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)
Best regards,
Leon
That's not true. They say that since 2008r2 default port range for DCOM is 49152-65535.
So I don't understand why my Windows Server 2016 start using them now
Yes correct I clarified my answer, I did some testing in my lab environments and I do get proper ports within the supposed port ranges on Windows Server 2016 & 2019 servers, so your issue seems rather peculiar.
