Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am a student and doing an internship. I have to test Microsoft Exchange Server 2013.

I am using Windows Server 2012, I already installed Exchange Server 2013 on it and everything works as intended.

But I couldn't find out how to configure my Windows Server 2012 in order to authenticate my mailbox users from Exchange Server 2013 with a RADIUS server which is not on my Windows Server 2012. I have to use their RADIUS server ( freeRADIUS2 ), the RADIUS server from the company where I am doing my internship.

I already did the checklist that is on link. I configured the NPS as a RADIUS proxy, because that's what I need.

So after doing everything that is on that checklist, my question is:

  • Is it possible that the Exchange Server 2013 will use my NPS which is now configured as a NPS RADIUS proxy to authenticate my mailbox users that I have on my Exchange Server 2013?
share|improve this question
Exchange doesn't use radius to authenticate users.. Exchange authenticates against Active Directory. Radius on windows runs against Active Directory. So this request make no sense. NPS is used for network authentication services (ie RADIUS). This request to authenticate them against another authority seems quite odd. it might be possible to accomplish this if you can convince windows that OpenLDAP or some other service is another trusted domain, but that sounds like much unneeded voodoo. – MikeAWood Mar 26 '14 at 5:51
I see, thank you for enlightening me. It makes sense. – David_Intern Mar 26 '14 at 7:30

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.