amyr Posted May 24, 2010 Posted May 24, 2010 Interesting problem which has been driving me and the guy who installed the Wireless network nuts. We've recently installed a Trapeze wireless network, using an MX-Switch and Trapeze MP-82's. We've installed Network Policy Server and the certification server that is also required (Windows 2008 SP2 domain controllers). Clients are running XP SP3. We've configured the Network Policy Server to use PEAP MS-Chap-v2. The problem we have is that only domain admins can login and get an IP address, normal user's can't - it fails to authenticate and get an IP address. We've tried a radius ping from the Mx-Switch and that responds fine and authenticates. This has really got us puzzled. We've got it logged with Trapeze as well, but just thought I'd see if anyone else has come across this before?!?
DMcCoy Posted May 24, 2010 Posted May 24, 2010 Which groups are set in the network policy rule? Thats what decided which groups will authenticate. Also check the security log on the NPS server as that will log the failure reason. They are probably not matching a rule at the moment.
amyr Posted May 24, 2010 Author Posted May 24, 2010 We currently have it so that all users can authenticate - followed the wizard to configure the policy rules. Checked the log and the only time we get any errors/events is when the local administrator account tries to authenticate/get an IP Address. edited to add: have also tried group specific and machine specific policies but no joy. another edit to say that we can login fine on an xp sp2 laptop. so its something to do with sp3 I think. To me its pointing towards security but I'm unable to identify where/what.
DMcCoy Posted May 24, 2010 Posted May 24, 2010 Try starting the NAP, wired and wireless authentication services automatically on a XP SP3 machine. Make sure there are no health policies on the NPS server as SP3 includes the NAP client.
DMcCoy Posted May 24, 2010 Posted May 24, 2010 Oh, also add the wireless network manually. The automatic adding can get the WPA/WPA2 encryption type wrong. If there continue to be no failed entries in the security log then the machines aren't getting as far as NPS, and are stuck authenticating to the wireless box.
amyr Posted May 25, 2010 Author Posted May 25, 2010 Have tried all of that and still no joy. Only domain admins can authenticate. So still confused.
amyr Posted May 27, 2010 Author Posted May 27, 2010 solved it in the end - laptops required an MS Hotfix (KB969111) and then they worked perfectly! THanks for all your help though
brian1977 Posted July 28, 2010 Posted July 28, 2010 Here is what I get when I try to ping from ringmaster: Ping started... Sending authentication request to server uvserver (217.60.64.3:1812) Encryption failed - unable to send request Ping completed. I cannot get passed "Encryption failed - unable to send request" anybody know what I maybe be doing wrong? Kind regards - Brian.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now