Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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 have to find out in which exact format JCIFS stores the user principal in the "getUserPrincipal()" property. Therefor i created a test Environment like this:

  • Windows Server 2008 Domain Controller
  • Domain named "MYDOMAIN"
  • Many Testusers in Active Directory
  • Tomcat Application Server with my Web Application (which simply reads the user Principal and displays its values).

The user should be logged in to the web-application with SSO therefor i need the format that jcifs is using to store the user. (For example user@MYDOMAIN or MYDOMAIN\user...)

I tested the Authentication with other SSO frameworks with Kerberos Method and it works as expected.

I'm now trying to use SSO through the NTLMHttpFilter of JCIFS. When i try to login i get the following error message:

jcifs.smb.SmbException: The parameter is incorrect.

Regarding to the documentation i'm using to configure this, this is a know issue with the Group policy. It is stated there, that i have to change the Group policy "Networkaccess: lan-manager authentication level" to respond to NTLMv1 request.

I have done this, but it's still not working. So what i also have to configure is the same policy on the client computer. I have to change the policy, so that the client computer sends NTLMv1. But it is always sending NTLMv2 tokens.

The problem now is that i'm somehow not able to change this setting. (I already was before) because the dropdown box to choose the authentication method is "greyed out".

Lan-manager authentication level at Client-Side

edit: just to make this clear, this dialog is on the client-side in the "local-security policies"

As you can see from this screenshot, the chosen method is "Only send NTLMv2 responses" which is the wrong setting and i'm pretty sure that this is causing the error above.

My question is now, why can't i change this setting? Why is it greyd out?

share|improve this question

That's because you have a group security policy managing this feature, so you can't modify it locally. Run gpmc.msc instead of gpedit.msc and you should be able to modify it if you are Administrator.

share|improve this answer

Your Answer


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

Not the answer you're looking for? Browse other questions tagged or ask your own question.