From the ports shown, these are the ones explicitly identified as Windows OS or Windows service related in the provided documentation:
- 1801/TCP — MSMQ / Message Queuing
- 2103/TCP — MSMQ-RPC / Message Queuing
- 2105/TCP — MSMQ-RPC / Message Queuing
- 2107/TCP — MSMQ-Mgmt / Message Queuing
- 3389/TCP — ms-wbt-server / Remote Desktop Services port name is shown in the port list as
ms-wbt-server - 47001/TCP — WinRM
Also listed in the Windows service port documentation:
- 80/TCP — used for HTTP by Windows services in some scenarios, but this port is not OS-exclusive
The remaining ports in the list are not confirmed as Windows OS-related from the provided documentation:
- 1002/TCP
- 2738/TCP
- 4118/TCP
- 4750/TCP
- 5114/TCP
- 5985/TCP
- 7937/TCP
- 7938/TCP
- 8901/TCP
- 9015/TCP
- 9151/TCP
- 9173/TCP
- 9174/TCP
- 9181/TCP
- 9604/TCP
If the goal is to verify which process is actually listening on any of these ports on a Windows server, use:
netstat -ano
Then match the PID in Task Manager to identify the program using the port.