Skip to main content

I recently setup a dev environment in a standalone config with a seperate SQL server. I keep getting a 401.2 error when trying to access workspace. If I go into IIS and change the security to use Basic Authentication I get prompted and it lets me in. This only happens when security is set to Windows Authentication in IIS. I also have IE to use Integrated Authentication and it is a trusted site. The only thing that is different than any other setup of BP that I have done is that this is on a network with ISA 2004 and all client machines go through the ISA proxy. From what I read on M$ is that NTLM does not work through proxies (http://support.microsoft.com/kb/907273). I do have the settings in IE to bypass the proxy with local traffic. I don't have any type of ports blocking on the inside, just outside, which I am not coming from the outside.

 

I ran in console mode and it shows no activity during the 401 error, and Windows Logs and IIS logs don't say anything fancy excepth 401.

 

I am also getting a .Net violation when trying to install the 803 patch so until that is working I am running BP SP1. Any pointers.

 

Server A: MOSS/BP SP1/Windows Server Enterprise 2k3 SP2

Server B: SQL 2005/Windows Server Enterprise 2k3 SP2

Hi,


The possible problem is that your Workspace web site has nothing set for the NTAuthenticationProviders node in the IIS Metabase and that it is trying to use Kerberos authentication by default. You need to set the node to NTLM to force it to use NTLM.


C:InetpubAdminscripts>cscript adsutil.vbs set w3svc/xx/NTAuthenticationProviders "NTLM" (Replace xx with the web site number)


IISRESET


Reference KB: http://kb.k2workflow.com/Articles/KB000171.aspx - Step 11 for more information.


Also make sure that your server has the DisableLoopbackCheck registry key applied (http://kb.k2workflow.com/Articles/KB000098.aspx)


Hope this helps.


Regards,


Thanks Johan.


That works too for 401.1 errors :-)


Reply