The Peer Name Resolution Protocol (PNRPsvc) service enables peer name resolution over the Internet without using a server. If this service is disabled, some peer-to-peer and collaborative applications may not function. This protocol enables the naming of computers and services without relying on a DNS server. This allows for flexible, informal, temporary networks of nearby computers for collaboration, data sharing, and data storage.
Security in peer-to-peer networks is difficult to establish. If computers in your organization are allowed to connect to peer-to-peer networks, a security policy about the types of information that is shared and the types of peer-to-peer networks that are compliant with your policy should be explicitly designed and communicated to your users. This helps users make decisions about which peer-to-peer networks they can trust.
A trusted peer-to-peer network should meet the following industry standards for establishing trust:
- Uses a trusted authentication method to identify the network and its users. Your security policy should identify which form of authentication is the minimally acceptable method.
- Supports different authorization levels to allow for control over who shares information by using the network.
- Supports encrypted data transmission so that when users collaborate over this network, their information is not as susceptible to capture by unauthorized users.
- Provides some form of data-integrity checking, such as digital signatures, to ensure that the data was not modified in transit.
This service is installed by default and its startup type is Manual.
When the Peer Name Resolution Protocol service is started in its default configuration, it logs on by using the Local Service account.
The Peer Name Resolution Protocol service is dependent upon the following system component:
- Peer Networking Identity Manager
The following system components are dependent upon the Peer Name Resolution Protocol service:
- Peer Networking Grouping
- PNRP Machine Name Publication Service