DCOM port requirements for Windows Discovery

[Suggy]

I need more details on DCOM ports opening for Windows Discovery.

Which all ports needs to be opened. How DCOM is related to Windows discovery. What all needs to be done.

Need to share the exact details to my windows team for fulfilling successful discovery of Windows hosts.

I see its a huge list:

The default ranges of DCOM ports are:

• from 1025   to 5000:   Windows 2000, Windows XP and Windows Server 2003
• from 49152 to 65535: Windows Server 2008 and later versions, and in Windows Vista and later versions

Should I tell my windows team to open all the above ports? Will my windows team be okay to enable so many ports? 

Please share your experience on this topic.

Thanks

[Rahul Priyadars]

@Suggy refer this as per service now.  

Shazzam probe, port probes, and protocols | ServiceNow Docs

I have not seen any Service Now Docs stating 300 High ports for communication after Classification is done on port 135. May be i am missing something.

Regards

RP

[VivekSattanatha · Accepted solution]

hi Suggy,

These are high ports there is no need that we need to open all these 16k+ ports. we need a minimum of at least 300 ports within that range so that wmi can use any of them. You can talk to your windows teams it's not like the windows team has to open these ports one by one, when they create a firewall inbound rule they can specify these ranges which they need. If your company using agentless monitoring solutions like SolarWinds, Icinga, or Nagios they would be having these ports already so it won't be a problem for them.

Regards,

Vivek

[Minesh Bandre]

Hello Vivek,

Does ServiceNow still supports discovery based on DCOM ports in latest(SD) release? Or have they stopped.

Thanks in Advance

[Suggy]

Thank you so much @Rahul Priyadarshy @Vivek.Sattanatha  🙂