What is RPC and why is it so important? - Super User
Nov 10, 2017 · Remote Procedure Call (RPC) is a protocol that one program can use to request a service from a program located in another computer in a network without having to understand network details. (A procedure call is also sometimes known as a function call or a subroutine call.) RPC uses the client/server model.
rpc - Usefulness of having port 135 open in Active Directory ...
Apr 25, 2019 · Port 135 is the RPC Endpoint Mapper service. It is a service that allows other systems to discover what services are advertised on a machine and what port to find them on. It is mostly associated with remote access and remote management. It is a sensitive port that is associated with a slew of security vulnerabilities and should never be ...
windows registry - Whitelisting RPC dynamic ports - Super User
May 14, 2018 · Now I might be quite tired but as long as a session is initiated (lets say on TCP 135) then all the following communication within that session regardless of ephemeral ports should be good to go without any specific firewall rules but I guess that RPC behaves quite differently. Outgoing firewall rules should be good, Windows Firewall is disabled.
Why are there many similar firewall rules with "RPC-EPMAP" suffix?
May 9, 2016 · 2. RPC-EPMAP is the RPC "endpoint mapper", which multiplexes several different MSRPC-based services over a single port. (Similar to HTTP vhosts, I guess.) Windows Firewall knows more than just TCP ports – AFAIK, it can block and allow individual MSRPC services. So my first guess would be that these rules have hidden parameters which select a ...
Which ports to open to ensure NFS mount succeeds?
mount.nfs: prog 100005, trying vers=3, prot=17. mount.nfs: trying X.X.X.XX prog 100005 vers 3 prot UDP port 60219. mount.nfs: portmap query retrying: RPC: Timed out. In addition to the standard NFS port (2049), there's a random UDP and TCP port being tried, which I hadn't allowed through my security groups.
linux - iptables rules for nfs - Super User
Oct 31, 2013 · Flush and check Iptables rules. iptables -F. iptables -L. Obtain the firewalled NFS Server ports from the client machine and notedown the port numbers and the OSI layer 4 protcols. rpcinfo -p 'ip-addr-nfs-server' | sort -k 3. Restore the pre-nfs-firewall-rules now. iptables-restore < pre-nfs-firewall-rules-client.
Does Psexec execute Remote Procedure Calls? - Super User
9. Yes. Psexec issues a remote procedure call to start up the specified process on the foreign machine with the credentials provided. Although traditionally 445 is used for SMB and 135 is used for DCOM, both can be used by RPC depending on the specifics of the protocol and the objects that are being remotely used.
How are source ports determined and how can I force it to use a ...
Aug 29, 2016 · net.ipv4.ip_local_reserved_ports. knob that does somewhat opposite but nevertheless it might be very useful because that way you can "punch a hole" for services that open specific port(s) in otherwise ephemeral range of ports. Brief excerpt from the docs: Specify the ports which are reserved for known third-party applications.
windows 7 - How to stop listening at Port 135? - Super User
Dec 12, 2015 · At the right column, locate the value EnableDCOM and modify the value to N. Navigate to this registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RPC. Right click on & Modify the value named DCOM Protocols Under the key Value Data, you will see values like below (or something similar). These values keep Port 135 open.
Is it OK to have ports 135 & 49154-49155 open in Windows Firewall?
However, besides ports 80 and 443 (which are needed for IIS), two ports are still accessible from the outside world: 135 and 49154 (or 49155 sometimes). It seems these ports are used for RPC/DCOM. Since they are left open, I presume these are needed for Windows 2008 to function? Are there hacks possible on these ports? windows. windows-firewall.