Creating Custom RPC Protocol Definitions
By default, only two types of RPC options are available for RPC-based server publishing
rules. The first option is to open all RPC interfaces, which is what was used for the
scenario in the previous section. The other defined RPC protocol definition is used for
Exchange MAPI access to mailboxes that use RPC. This protocol definition includes all the
custom UUIDs that Outlook and Exchange need to communicate over MAPI.
In addition to using the default RPC protocol definitions, custom RPC protocols can be
created and used for server publishing rules. If custom definitions are created for RPC, the
service can be secured even further to allow only RPC traffic to the UUID services that the
rule absolutely needs, rather than open up blanket RPC access.
For example, an RPC protocol definition could be made for Active Directory domain
controller replication that uses the UUIDs that are required for replication to take place.
Or, a RPC protocol definition could be created to allow access to a system using the
Microsoft Management Console (MMC), which uses a different unique ID.
NOTE
To determine which UUID is used by a particular service, the Network Monitor tool can
be used to ???sniff??? the packets that hit a server and determine which UUIDs are necessary.
Pages:
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672