It looks like Terminal Services may have a built-in 30-second timeout. I found something that may solve the problem. We have used it here at Microsoft without any timeout issues as well. We have a number of customers that are using MFA Server with RD Gateway without any issues. Do I start from scratch, delete all traces of Radius/NPS/MFA and rebuild, or is there some other trick?Ĭonfiguring the 'Number of seconds without request is considered dropped' and 'Number of seconds between requests when server is identified as unavailable' on the Load Balancing tab of the RADIUS server settings are the only timeouts The server has been marked as unavailable.'Īgain - no changes have been made.

Service) server did not respond.' Also getting the beloved 'The remote RADIUS server x.x.x.x has not responded to 5 consecutive requests. When Radius is enabled, it logs 6274 in NPS - 'Network Policy Server discarded the request for a user. The remote RADIUS (Remote Authentication Dial-In User If I set the RD Gateway to bypass the Radius/NPS/MFA piece, it works as expected. The gateway or MFA systems, but as previously mentioned, it stopped working after our subscription lapsed.

No configuration changes have been made on either RD Gateway logins, however, just time out. Testing its functionality within the MFA console works - I get a phone call and can authenticate successfully. Since that time, 2 factor authentication with RD gateway no longer functions, though our subscription has been reinstated. Our bill was not paid for several months (thanks, accounting), and our subscription was understandably cancelled.

Rd gateway mfa