rpc port 49158

Posted on 2010-09-07
Last Modified: 2013-12-04
I am trying to do a small test for restricting rpc to use static port. Using the Registry I did static port assignment for NTDS to be 49155 in the domain controller. I have two virtual machines, the dc is running windows 2008 r2 with ip, and a member server running windows 2003 ip using the dc windows firewall i created new rpc rule to use port 49155. from the firewall log bellow I have two questions:
1- why win2003 is trying to connect to with port 49158? And what is the affect of that?
2- for NTDS static port assignment , do I have to do it for all the company dc’s?
firewall log
ALLOW UDP 1026 53 0 -- RECEIVE
ALLOW TCP 1058 135 0 - 0 0 0 - - - RECEIVE
DROP TCP 1059 49158 48 S 1388427278 0 64240 - - - RECEIVE
DROP TCP 1059 49158 48 S 1388427278 0 64240 - - - RECEIVE
ALLOW UDP 138 138 0 -- RECEIVE
ALLOW UDP 1060 88 0 -- RECEIVE
ALLOW TCP 1061 88 0 - 0 0 0 - - - RECEIVE
ALLOW UDP 1062 88 0 -- RECEIVE
DROP TCP 1059 49158 48 S 1388427278  - - RECEIVE
DROP UDP 137 137 78 -- RECEIVE
DROP UDP 137 137 78 -- RECEIVE
DROP UDP 137 137 78 -- RECEIVE
ALLOW ICMP - - 0 - - - - 8 0 - RECEIVE
DROP UDP 137 137 78 -- RECEIVE
DROP UDP 137 137 78 -- RECEIVE
DROP UDP 137 137 78 -- RECEIVE
DROP UDP 137 137 78 -- RECEIVE
DROP UDP 137 137 78 -- RECEIVE
DROP UDP 137 137 78 -- RECEIVE
ALLOW TCP 1064 49155 0 - 0 0 0 - - - RECEIVE
Question by:alex-2010
1 Comment
LVL 38

Accepted Solution

Adam Brown earned 500 total points
ID: 33666695
The RPC ports that you're messing with are actually client ports. When a DC makes an RPC request to another DC for replication, it will initiate the request on one of the ports in the range so the RPC server is able to more easily route traffic back to the requesting client. That port is chosen randomly from a range of several thousand. Pinching down the RPC ports on the server will limit the ports that it uses to make requests. So in your situation, the Win2k3 server is opening an RPC request on port 49158 which is being blocked by your firewall. In order to limit ports used by RPC, you'll need to actually limit the ports available on all DCs.

Also, I wouldn't recommend using a single port for RPC client requests, as you may rapidly run out of available ports and in turn decrease throughput and increase latency for replication.

Featured Post

Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

This article offers some helpful and general tips for safe browsing and online shopping. It offers simple and manageable procedures that help to ensure the safety of one's personal information and the security of any devices.
Container Orchestration platforms empower organizations to scale their apps at an exceptional rate. This is the reason numerous innovation-driven companies are moving apps to an appropriated datacenter wide platform that empowers them to scale at a …
A company’s greatest vulnerability is their email. CEO fraud, ransomware and spear phishing attacks are the no1 threat to a company’s security. Cybercrime is responsible for the largest loss of money to companies today with losses projected to r…
The Email Laundry PDF encryption service allows companies to send confidential encrypted  emails to anybody. The PDF document can also contain attachments that are embedded in the encrypted PDF. The password is randomly generated by The Email Laundr…

919 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now