Fix: LSA is Unable to Obtain an RPC Connection

Adding a forwarder to the domain should fix this

by Ola-Hassan Bolaji
Ola-Hassan Bolaji
Ola-Hassan Bolaji
Editor
A Computer Engineering graduate, he has spent most of his life reading and writing about computers. He finds joy in simplifying complex topics into simple solutions for PC... read more
Updated on
Affiliate Disclosure
  • If the Local Security Authority is unable to obtain an RPC connection error, it might be because of interference from your firewall.
  • You can fix this issue by running a few commands on an elevated Command Prompt.
  • Another effective solution is to uninstall the shared folder if you use VMware.
local security authority is unable to obtain an rpc connection
XINSTALL BY CLICKING THE DOWNLOAD FILE
A message from our partner

To fix Windows PC system issues, you will need a dedicated tool

  • Download Fortect and install it on your PC
  • Start the tool's scanning process to look for corrupt files that are the source of your problem
  • Right-click on Start Repair so the tool could start the fixing algorythm
Download from Fortect.com Fortect has been downloaded by 0 readers this month, rated 4.4 on TrustPilot

Connecting and establishing trust between two Domain Controllers is a popular practice. However, some users are reporting a Local Service Authority is unable to obtain an RPC connection error after entering the Domain FQDN or NetBIOS name.

While this issue can be pretty annoying, it is not the most difficult to fix, as it only requires minor tweaks most times. In this guide, we will show you the steps to follow to fix this issue and establish trust relationships between your servers.

Why is Local Security Authority unable to obtain an RPC connection?

Below are some of the potential causes that can cause LSA to be unable to obtain an RPC connection:

  • Firewall interference – One of the first things to check if you are getting this error is Windows Defender Firewall is not blocking the connection. You might need to disable the firewall on the two servers temporarily to fix the issue.
  • Issues with Shared folder on VMware – If you are using VMware, this problem might be due to the shared folder. Uninstalling it has proved effective for most users.
  • Incorrect time – If the time on the two servers you are trying to connect does not match, you are likely to get the Local Security Authority unable to obtain an RPC connection error.

Now that we know what can cause this issue, let’s fix it by using the solutions below.

What do I do if LSA is unable to obtain an RPC connection error?

Before delving into the fixes in this section, try the following troubleshooting steps:

  • Check if the time on the two servers is in sync
  • Ensure the passwords of both administrators in different domains are in sync
  • Disconnect and reconnect to the domain network

If this does not work, proceed to the solutions below:

1. Disable the firewall temporarily

  1. Press the Windows key, type firewall, and select Windows Defender Firewall.
    firewall local security authority is unable to obtain an rpc connection
  2. Select Turn Windows Defender Firewall on or off.
    turn windows
  3. Now, tick the radio buttons for the Turn off Window Defender Firewall button for both the Public and Private network settings.
  4. Finally, click the OK button.
    turn off

If the firewall on either of the servers or DCs is active, it might be stopping you from creating trust relationships. This leads to the Local Security Authority is unable to obtain an RPC connection error.

The solution to this is to disable the firewall temporarily and retry the connection.

2. Add a forwarder

  1. If you have added the DNS of the server (say D2) you want to create trust with to your source server (say D1), you need to remove it.
  2. Now, open the DNS console under Administrative Tools.
    tools
  3. Right-click on the DNS server node and choose the Properties option.
    properties local security authority is unable to obtain an rpc connection
  4. Next, click the Forwarders or Forwarding tab at the top, depending on your server.
  5. Click the New or Edit button under the DNS domain section and enter the name of the domain you want your name server to forward to (e.g., domain2.com).
    forwarders
  6. Type the forwarder IP address (the remote site’s DNS, which is also the DC for that site), and click the Apply button followed by OK.
  7. From here, press the Windows key, type cmd, and select Run as administrator under Command Prompt.
  8. Finally, type the command below and hit Enter to run it: ipconfig/flushdnsipconfig local security authority is unable to obtain an rpc connection

According to some users, you can eliminate the Local Security Authority is unable to obtain an RPC connection error by adding a forwarder IP address to your connection.

3. Try net use

  1. Press the Windows key + R, type \\domain.com\c$, and click the OK button.
    domain
  2. Now, type your username and password and check what the \\domain.com\c$ opens.
  3. Finally, try creating trust again with FQDN and not NetBIOS.

4. Uninstall the Shared folder on VMware

  1. Press the Windows key, type control, and select Control Panel.
    control panel
  2. Select Uninstall a program under the Programs option.
    uninstall a local security authority is unable to obtain an rpc connection
  3. Now, right-click VMware Tools and select Change.
  4. Click the Next button.
  5. Finally, untick the box for Shared Folders and reboot your machine.

If you are getting the Local Security Authority is unable to obtain an RPC connection error while trying to establish trust between your Domain Controllers, it might be due to the Shared Folders feature of VMware.

Note that the steps above are for uninstalling the feature on Windows 2003, which is the common version users face this error.

There you have everything you need to get rid of the Local Security Authority is unable to obtain an RPC connection while trying to establish trust between your Domain Controllers. You should now be able to fix this issue provided you follow the steps above.

If you are dealing with a similar error in Local Security Authority cannot be contacted, check our detailed guide to fix it.

Feel free to let us know the solution that helped you fix this issue in the comments below.

This article covers:Topics: