PROBLEMThe error: 'The RPC server is unavailable' is encountered when the server needs to access a remote computer.
This error can occur in different situations, for example:
- GFI LanGuard scans a remote computer
- GFI LanGuard deploys the agent to a remote computer
- GFI EventsManager collects events from a remote computer
- GFI EventsManager
- GFI LanGuard
- GFI EndPointSecurity
- all supported environments
SOLUTIONCheck the following:
- Does the remote computer exist?
- Is the remote computer shut down?
- Is there a network or hardware problem?
- Are there no common transports?
- Does a DNS entry exist for the remote computer?
Are the following Microsoft Windows services disabled?
- Remote Procedure Call (RPC)
- Remote Procedure Call (RPC) Locator
- Remote Registry
- Are firewalls (or even antivirus software) blocking RPC traffic?
Check all the policies for NTLM in the local policy editor (Gpedit.msc) AND in the local security policy editor (secpol.msc) under the following section and set them to Not defined or Allow All (Important Note: the same policies can be set separately in each editor and the most restrictive will take effect)
- Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options
- If the target computer is a WinXP machine, check to see if the following applies:
- RPC can be used over SMB protocol which uses ports 139 and / or 445 (ex. connecting to the remote registry)
- RPC can also use dynamic ports from a large port range by default (1024 - 65535 for Microsoft Windows 2003 and XP / 49152 - 65535 for Microsoft Windows 2008, Vista and 7). The port range used can be limited: