Fix RPC Server Unavailable Error 1722 in Windows: 5 Working Solutions

By /

RPC stands for Remote Procedure Call. It’s how Windows components talk to each other. When you see error 1722, it means this communication broke down.

Error 1722 says: “The RPC server is unavailable.” This stops you from doing things like accessing shared folders, syncing files, or managing network resources.

The error usually appears when:

  • Your network connection drops
  • Firewall blocks RPC ports
  • Windows services stopped running
  • Network drivers have issues
  • DNS resolution fails

You’ll often see this error in Event Viewer, network troubleshooting tools, or when trying to access shared resources on your computer or network.

The good news? Most people fix this with one of the five solutions below.

Solution 1: Check Your Network Connection First

Before trying complex fixes, confirm your internet and network work properly.

Step-by-step:

  1. Open Settings
  2. Go to Network & Internet
  3. Check your connection status
  4. Click on your network name
  5. Look for “Connected” status

If you’re not connected, reconnect to your network.

Test your connection:

  • Open Command Prompt (right-click, Run as Administrator)
  • Type: ping 8.8.8.8
  • Press Enter

You should see responses from Google’s server. If you get “Request timed out,” your network has a problem.

What to do if connection is down:

  • Restart your router and modem
  • Wait 2-3 minutes
  • Reconnect to your network
  • Try pinging again

Most network-related RPC errors fix themselves once connection returns.

Solution 2: Restart the RPC Service

Windows has a specific service called “Remote Procedure Call” that needs to run for RPC communication to work.

How to restart it:

  1. Press Windows Key + R
  2. Type: services.msc
  3. Press Enter
  4. Find “Remote Procedure Call (RPC)” in the list
  5. Right-click on it
  6. Select “Restart”

Windows will stop and start the service automatically.

Verify the service is running:

  • The Status column should show “Running”
  • Startup Type should be “Automatic”

If the service won’t start:

  1. Right-click “Remote Procedure Call (RPC)”
  2. Select Properties
  3. Set Startup Type to “Automatic”
  4. Click Apply, then OK
  5. Click the Start button
  6. Click OK

Also restart these related services:

  • RPC Endpoint Mapper
  • DCOM Server Process Launcher

Restarting these three services fixes error 1722 in most cases.

After restarting, try accessing your network resource again.

See also  Best Sound Equalizer for Windows 11: A Complete Guide to Better Audio

Solution 3: Configure Your Firewall to Allow RPC

Firewalls often block RPC ports, causing error 1722. You need to allow RPC through Windows Firewall.

Open Windows Firewall:

  1. Press Windows Key + R
  2. Type: wf.msc
  3. Press Enter

Allow RPC through the firewall:

  1. Click “Inbound Rules” on the left
  2. Look for rules with “Remote Procedure Call” in the name
  3. Make sure these rules exist and are Enabled:
  • Remote Procedure Call (RPC)
  • Remote Procedure Call (RPC-EPMAP)
  • Remote Procedure Call (RPC) over HTTP
  1. If any are disabled, right-click and select “Enable Rule”

If these rules don’t exist:

  1. Click “New Rule” in the right panel
  2. Select “Predefined”
  3. Choose “Remote Procedure Call (RPC)”
  4. Click Next
  5. Check all RPC options
  6. Click Next, then Finish

For outbound rules:

  1. Click “Outbound Rules” on the left
  2. Repeat the same process
  3. Look for and enable RPC rules

Which ports does RPC use?

RPC dynamically uses ports in the high range (49152 and above). Your firewall should allow traffic on these ports.

After configuring firewall rules, restart your computer and test if error 1722 is gone.

Solution 4: Fix DNS Resolution Issues

RPC errors often happen when Windows can’t resolve network names to IP addresses. This is a DNS problem.

Test your DNS:

  1. Open Command Prompt (Run as Administrator)
  2. Type: nslookup google.com
  3. Press Enter

You should see IP addresses returned. If you get “server failed,” DNS isn’t working.

Reset DNS settings:

  1. Open Command Prompt (Run as Administrator)
  2. Type these commands one by one, pressing Enter after each:
ipconfig /flushdns
ipconfig /registerdns
ipconfig /release
ipconfig /renew

Change DNS if needed:

  1. Go to Settings
  2. Select Network & Internet
  3. Click WiFi (or Ethernet)
  4. Scroll down to DNS server assignment
  5. Click Edit
  6. Change from “Automatic” to “Manual”
  7. Toggle IPv4 on
  8. Enter these DNS servers:
  • 8.8.8.8
  • 8.8.4.4

These are Google’s public DNS servers, which are reliable.

  1. Click Save

Flush DNS cache on next restart:

Some computers have stuck DNS cache. Flushing helps clear it.

  1. Restart your computer
  2. Open Command Prompt (Run as Administrator)
  3. Type: ipconfig /flushdns
  4. Press Enter

Wait a few minutes, then try accessing your network resource again.

See also  How to Reset a COM Port in Windows for Free: Your Guide to Fix Port Issues

Solution 5: Update Network Drivers and Windows

Outdated drivers often cause RPC errors. Updating them usually fixes the problem.

Update network drivers:

  1. Press Windows Key + X
  2. Select “Device Manager”
  3. Expand “Network adapters”
  4. Right-click your network adapter
  5. Select “Update driver”
  6. Choose “Search automatically for updated driver software”

Windows will search and install the latest driver.

If a newer driver is found:

  • Windows installs it automatically
  • You may need to restart your computer

Update Windows:

  1. Go to Settings
  2. Select Update & Security
  3. Click “Check for updates”
  4. Download and install any available updates
  5. Restart when prompted

Update other critical drivers:

Open Device Manager and update:

  • Graphics driver
  • Chipset driver
  • Any devices with yellow warning marks

Download drivers manually if Windows can’t find them:

  1. Go to your computer manufacturer’s website (Dell, HP, Lenovo, etc.)
  2. Enter your model number
  3. Download the latest network driver
  4. Right-click the downloaded file
  5. Select “Run as Administrator”
  6. Follow installation steps
  7. Restart your computer

After updating all drivers and Windows, error 1722 should be resolved.

When to Use Each Solution

SolutionBest ForTime RequiredDifficulty
Check NetworkError just appeared5 minutesVery Easy
Restart RPC ServiceService stopped running5 minutesVery Easy
Firewall SettingsRecently installed firewall10 minutesEasy
DNS ResetCan’t access some resources10 minutesEasy
Update DriversComputer is several months old20 minutesEasy

Prevention Tips to Avoid RPC Error 1722

Now that you’ve fixed error 1722, keep it from coming back.

Maintain good network health:

  • Keep your router updated
  • Don’t use too many devices on one network
  • Use a wired connection when possible (more stable than WiFi)

Keep Windows updated:

  • Turn on automatic updates
  • Install updates when prompted
  • Restart your computer when Windows asks

Update drivers regularly:

  • Check for driver updates monthly
  • Use your computer manufacturer’s update tool
  • Enable automatic driver updates if available

Protect your firewall:

  • Don’t disable Windows Firewall entirely
  • Add exceptions instead of turning it off
  • Review firewall rules periodically

Monitor network services:

  • Check that RPC service is running weekly
  • Restart it if it stops
  • Use Task Scheduler to automatically restart it daily (optional)
See also  Fix "User Must Change Password at Next Logon" Not Working in Windows

Troubleshooting Steps If Error Persists

If error 1722 still appears after trying all five solutions, try these additional steps.

Run Network Troubleshooter:

  1. Go to Settings
  2. Select Update & Security
  3. Click Troubleshoot
  4. Select “Network troubleshooter”
  5. Follow the prompts

Check Event Viewer for clues:

  1. Press Windows Key + R
  2. Type: eventvwr.msc
  3. Look in System and Application logs
  4. Find errors with RPC in the name
  5. Note the error codes and descriptions

Try connecting to a different network:

If you can access resources on a different network, your home network setup is the problem. This points to router or DNS issues.

Test with a wired connection:

WiFi sometimes causes RPC errors. Try connecting with an ethernet cable to rule out WiFi problems.

Check for malware:

Malware can block RPC communication.

  1. Run Windows Defender (built-in antivirus)
  2. Go to Settings
  3. Select Update & Security
  4. Click Windows Security
  5. Run a full scan

Disable VPN temporarily:

VPN software sometimes interferes with RPC. If you use a VPN, disable it temporarily to test.

Summary: Your Action Plan to Fix RPC Error 1722

RPC error 1722 happens when Windows communication breaks down. You’ve learned five solutions that work:

  1. Check your network connection first (fastest)
  2. Restart RPC service (usually fixes it)
  3. Configure firewall rules (if blocked)
  4. Fix DNS resolution (when names don’t resolve)
  5. Update drivers and Windows (if outdated)

Your immediate next steps:

  • Restart your computer
  • Try Solution 1 (check network)
  • Move to Solution 2 (restart RPC service)
  • Test if error is gone

Most people succeed with just these two steps.

If error 1722 persists, work through Solutions 3, 4, and 5 in order. Give each solution 15 minutes before moving to the next one.

Error 1722 is fixable. Don’t panic. Follow these steps methodically, and you’ll restore RPC communication. If you’re still stuck after all five solutions, your error may need professional network support.

Osmanim
Latest posts by Osmanim (see all)
Scroll to Top