Estimated reading time: 4 minutes
Setting up Remote Desktop Protocol (RDP) between two Windows 11 Enterprise PCs on a home network can be incredibly useful for managing multiple machines. However, if you’re using local accounts without a domain, you might run into errors when trying to connect. This guide walks you through the steps to configure RDP on a home network (e.g., IP range 192.168.0.0–254) and troubleshoot common issues. Whether you’re getting authentication errors or connection denials, we’ve got you covered!
Prerequisites
Before diving in, ensure the following:
- Both PCs run Windows 11 Enterprise.
- Both use local accounts (no domain).
- Both are on the same home network (e.g., 192.168.0.x).
- No third-party firewalls are blocking RDP (default port: 3389).
- You know the IP address or computer name of the target PC.
Configuring the Target PC (The One You’re Connecting To)
Step 1: Enable Remote Desktop
Start by enabling RDP on the target PC:
- Go to Settings > System > Remote Desktop.
- Toggle Enable Remote Desktop to On.
- Click Confirm if prompted.
- Note the PC name (you’ll use this or the IP address to connect).
Step 2: Allow RDP Through Windows Firewall
Ensure the firewall isn’t blocking RDP:
- Open Windows Defender Firewall from the Start menu.
- Click Allow an app or feature through Windows Defender Firewall.
- Find Remote Desktop and check both Private and Public boxes.
- If it’s not listed, click Allow another app, browse to
C:\Windows\System32\mstsc.exe
, and add it.
Step 3: Adjust Local Security Policies
Modify policies for compatibility with local accounts:
- Press Win + R, type
secpol.msc
, and press Enter. - Go to Local Policies > Security Options.
- Find Network security: LAN Manager authentication level.
- Set it to Send NTLMv2 response only.
- Find System cryptography: Use FIPS-compliant algorithms.
- Ensure it’s Disabled.
Step 4: Authorize the Local Account
Specify which accounts can use RDP:
- In Settings > System > Remote Desktop, click Select users that can remotely access this PC.
- Add the local account username (e.g., “User1”).
Step 5: Verify Registry Settings
Check RDP isn’t disabled in the registry:
- Press Win + R, type
regedit
, and press Enter. - Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server
. - Ensure fDenyTSConnections is set to 0.
Configuring the Source PC (The One You’re Connecting From)
Step 1: Test the Connection
Try connecting to the target PC:
- Press Win + R, type
mstsc
, and press Enter. - Enter the target PC’s IP (e.g.,
192.168.0.100
) or name. - Click Connect.
Step 2: Enter Credentials
When prompted, use the target PC’s local account credentials:
- Format:
TARGETPC\User1
or justUser1
.
Step 3: Verify Network Connectivity
Ensure the PCs can see each other:
- Open Command Prompt and type
ping 192.168.0.x
(use the target’s IP). - Confirm you get a response.
Troubleshooting Common RDP Errors
Here are fixes for frequent issues:
- “User account not authorized”: Revisit Step 4 under Target PC.
- “Authentication error”: In Remote Desktop > Advanced settings, uncheck Require Network Level Authentication (NLA).
- “No response”: Double-check IP, restart PCs, and ensure same subnet.
Tip: After changes, restart the target PC and try again.
Frequently Asked Questions
Can I use RDP without a password?
No, Windows blocks RDP for accounts with blank passwords unless you modify the Limit local account use of blank passwords policy (not recommended).
Why does it ask for Network Level Authentication?
NLA adds security but may fail with local accounts. Disable it on the target PC if needed.
What if I don’t know the IP address?
Use the computer name (found in Remote Desktop settings) or check the IP with ipconfig
in Command Prompt.
Glossary of Terms
- RDP: Remote Desktop Protocol, a Microsoft tool for remote PC access.
- Local Account: A user account not tied to a domain or Microsoft account.
- NLA: Network Level Authentication, an extra security layer for RDP.
- secpol.msc: Local Security Policy editor for managing system policies.
- mstsc: Command to launch the Remote Desktop Connection app.
Conclusion
With these steps, you should have RDP working smoothly between your Windows 11 Enterprise PCs. If you hit a snag, note the error message and double-check the settings. Happy remote managing!
Share this content: