Issues Connecting to Remote Desktop Gateway on Windows Server 2025

0
2
Asked By CleverLemon27 On

Hey folks,

I'm having trouble setting up a Remote Desktop Gateway on Windows Server 2025. We're not sure if we're missing something or if there's a configuration issue. Here's a bit about our setup and the problems we're facing:

- **Gateway Server**: Running Windows Server 2025
- **Installed Roles**: We've only got the RD Gateway installed, along with NPS and IIS.
- **Active Directory**: The server's computer account is added to the "RAS and IAS Servers" security group.

**The Problem**:
Whenever a client tries to connect, they always get a "login failed" message, asking for their credentials again. In the server's event logs, specifically in TerminalServices-Gateway, we only see **Event ID 312**, indicating that the user has initiated an outbound connection but hasn't yet been authenticated. The Network Policy Server (NPS) isn't generating any logs, and in the **Security log**, we can see **Event ID 4625**, which indicates a failed logon attempt with the substatus code **0xc000006e**.

We've tried a bunch of solutions we found online, but nothing has worked so far. Has anyone dealt with this issue before? Any assistance would be super helpful!

2 Answers

Answered By JustCurious_23 On

Quick question— is your RD Gateway connected to a domain, or is it standalone with local accounts? Running an RD Gateway isn't exactly the best practice these days since it hasn't really been updated for security. It's often advised to use a VPN before connecting via RDP. This way, you ensure a safer and encrypted connection.

Using it just within your intranet might be fine, but keep that in mind!

Answered By TechGuru1984 On

Hey! This error sounds familiar. A while back, I dealt with something similar while setting up certificate logins. I found that a restrictive firewall was blocking communication with the Domain Controller (DC). Once I fixed the firewall rules to allow for proper line of sight to the DC, the problem was solved.

You might want to check if anything is blocking the communication to your DC for authentication. Just a thought!

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.