English Portuguese
adsutil GET W3SVC/YOURID/Root/NTAuthenticationProviders
adsutil SET W3SVC/SEUID/Root/NTAuthenticationProviders NTLM
adsutil GET W3SVC/SEUID/Root/NTAuthenticationProviders
Pingback from Links (3/11/2008) « Steve Pietrek’s SharePoint Stuff
Hi Felipe,
This is a great article. I have a question,
Whats the difference between
and
adsutil SET W3SVC/SEUID/NTAuthenticationProviders NTLM
In our environment adsutil GET W3SVC/SEUID/NTAuthenticationProviders, returns NTLM. But we still see a lot of 401.1 errors. Will it make a difference by adding the Root/ switch ?
Thanks
Raj
This worked for me! thanks!
Thanx for the hint! You save my time and nerves.
The query posted returned "not set at this node". After setting it the problem still occurred. NTLM was set at
W3SVC/SEUID/NTAuthenticationProviders.
Guess I'll have to search some more...
Good Afternoon!!! weblogs.asp.net is one of the most outstanding informational websites of its kind. I take advantage of reading it every day. Keep it that way.
Understandably, this is a quick and dirty fix. The reality of the matter though, is that in a production environment, Kerberos SHOULD be used. While I have seen SharePoint farms deployed using NTLM, it is NOT in the server / network / security team's best interests.
I've typically deployed a farm using NTLM only in small farms with little security concerns.
Hi Steve,
thanks for your comment. I agree that Kerberos is a lot more secure than NTLM and should be the first option..
but in my case I was in an OpenLDAP + Samba domain, using an old version of both openldap and samba in fact.. so Kerberos was not an option unfortunately..
but this was indeed a small farm :)
regards
Pingback from SharePoint Returning a 401.1 for a Specific User/Computer Drija