board logo
Posted by: DogMan - 16 March 2026 12:08:19
A company trying to remote thorugh to us is hitting this wall - what can we do? [attach]117[/attach] I have tried guiding them through the login to no avail either through the /rdeweb link or the remote icon they have received.

Posted by: sirclesadmin - 16 March 2026 12:13:08

That error code (0x3000008) in Remote Desktop is a bit of a classic-it's essentially the computer saying, "I can see the door, but I can't find the keyhole." It usually points to a breakdown in the handshake between the remote client and your network gateway.

Since you're the one being connected to, here are the most likely culprits and how to address them:

1. The "Waking Up" Issue (Network Level Authentication)

Most modern RDP setups require Network Level Authentication (NLA). If the company's computer is trying to connect without it (or vice versa), the connection will drop immediately with that error.

  • The Fix: Ensure the remote user has "Use a web browser to sign in" or "NLA" enabled in their connection settings. On your end, verify that your RDP settings allow connections from computers running any version of Remote Desktop (if your security policy permits).

2. Workspace/Gateway Mismatch

This error often occurs when the user is trying to access a Remote Desktop Gateway or Azure Virtual Desktop but their local credentials haven't "refreshed" for that specific resource.

  • The Fix: Ask the company to sign out and sign back in to their Remote Desktop app or web feed. If they are using a saved .rdp file, it might be outdated or pointing to an expired session token.

3. Firewall or Port Blocking

If they are connecting from a strict corporate network, their outbound firewall might be blocking the specific port required for the gateway (usually UDP 3392 or TCP 443).

  • The Check: Have them try to connect via a different network (like a mobile hotspot) for a moment. If it works there, their office firewall is the "sidewinder" in this scenario, preventing forward movement.

4. MFA Timeouts

If your company uses Multi-Factor Authentication (MFA), the 0x3000008 error frequently triggers if the MFA prompt times out or is rejected silently.

  • The Check: Check your sign-in logs to see if there is a "Request Timed Out" or "User did not respond" entry at the exact timestamp shown in your image (11:32:06 UTC).

Summary Table for Quick Reference

Potential Cause Who Needs to Act? Recommended Action
Expired Session The Company Refresh the workspace/feed and re-authenticate.
MFA Timeout The Company Ensure they are watching their phone for the push notification.
NLA Conflict Both Ensure Network Level Authentication settings match.
UDP Blocking The Company Force the connection to use TCP only in RDP settings.