This object monitors the RPC Port Mapper service state and generates an alert if the service is not started, if the alert is enabled for this monitor.
This object monitors the RPC Port Mapper service state and generates an alert if the service is not started, if the alert is enabled for this monitor.
The RPC Port Mapper service (also known as portmap or rpcbind) enables UNIX-based computers to discover the UNIX-compatible services that are available on Windows-based computers. Without the RPC Port Mapper service, Server for NFS cannot start and NFS clients cannot access files on the server.
This monitor can enter a Warning health state if the RPC Port Mapper service has stopped either unexpectedly or by administrative action.
If the health state is unknown, it means that monitoring has not yet begun for this object.
Note Server for NFS and the Server for NFS driver are dependent on the RPC Port Mapper service. Stopping the RPC Port Mapper service will also stop Server for NFS and its driver.
Start the RPC Port Mapper service
To start the RPC Port Mapper service, at an elevated command prompt on the affected server, type net start portmap.
Verification
To verify the startup status of the RPC Port Mapper service, use the following procedure:
1. At an elevated command prompt on the affected server, type devmgmt.msc.
2. On the View menu, click Show hidden devices.
3. Expand the Non-Plug and Play Drivers node.
4. Right-click Server for NFS Open RPC (ONRPC) Portmapper, click Properties, and then check Device status.
To verify the state of the RPC Port Mapper service, use the following procedure:
1. At a command prompt, type sc query portmap.
2. Verify that the STATE is RUNNING.
To verify the state of Server for NFS, use the following procedure:
1. At a command prompt, type sc query >Microsoft-Windows-ServicesForNFS-Server.
2. Verify that the STATE is RUNNING.
This monitor automatically resets to a Healthy state after Server for NFS is restarted.
For more information about configuring Server for NFS, see Services for Network File System (http://go.microsoft.com/fwlink/?LinkId=185983).
| Target | Microsoft.Windows.FileServices.Service.NFS.10.0 | ||
| Parent Monitor | Microsoft.Windows.FileServices.Service.NFS.10.0.Portmap | ||
| Category | AvailabilityHealth | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | MatchMonitorHealth | ||
| Alert Priority | Normal | ||
| Alert Auto Resolve | True | ||
| Monitor Type | Microsoft.Windows.CheckNTServiceStateMonitorType | ||
| Remotable | True | ||
| Accessibility | Public | ||
| Alert Message |
| ||
| RunAs | Default |
Home
<UnitMonitor ID="Microsoft.Windows.FileServices.Service.NFS.10.0.Portmap.ServiceState" Accessibility="Public" Enabled="true" Target="Microsoft.Windows.FileServices.Service.NFS.10.0" ParentMonitorID="Microsoft.Windows.FileServices.Service.NFS.10.0.Portmap" Remotable="true" Priority="Normal" TypeID="Windows!Microsoft.Windows.CheckNTServiceStateMonitorType" ConfirmDelivery="false">
<Category>AvailabilityHealth</Category>
<AlertSettings AlertMessage="Microsoft.Windows.FileServices.Service.NFS.10.0.Portmap.ServiceState_AlertMessageResourceID">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
</AlertSettings>
<OperationalStates>
<OperationalState ID="Running" MonitorTypeStateID="Running" HealthState="Success"/>
<OperationalState ID="NotRunning" MonitorTypeStateID="NotRunning" HealthState="Warning"/>
</OperationalStates>
<Configuration>
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$</ComputerName>
<ServiceName>Portmap</ServiceName>
<CheckStartupType>false</CheckStartupType>
</Configuration>
</UnitMonitor>