Internet-Security.com TCP port 1030 details

TCP 1030 is commonly observed as a dynamically assigned Microsoft RPC (MS-RPCE) port on Windows systems.
On Windows 2000/XP/Server 2003 (default dynamic RPC range 1025–5000), services like Active Directory components (LSA/NetLogon), the Print Spooler, DFS/FRS, and the Server service often bind to 1030 after negotiating via the RPC Endpoint Mapper on 135.
Enterprise software that relies on Windows RPC—such as Microsoft Exchange Server 2000/2003 (MAPI/RPC)—can therefore appear to listen on TCP 1030 in real deployments.
As a result, real-world operations like Outlook-to-Exchange (pre-Exchange 2010) or domain join/management against AD DCs may traverse TCP 1030 when the OS assigns it.
Security note: worms exploiting the DCOM/RPC flaw (MS03-026, e.g., Blaster) targeted Windows RPC services and, after negotiation on 135, could use dynamically allocated ports like 1030 to deliver payloads.

TCP 1030