Here's the situation :

I have the same asp.net 2.0 web application running on both Machine A and Machine B.  On both machines, I have Integrated Windows Authentication turned on, and Anonymous Access turned off.  When I hit a certain page on Machine A, it will call the web service on Machine A, and then it will call the same web service on Machine B.  Likewise, when I hit the same page on Machine B, it will call the web service on Machine B, and then it will call the same web service on Machine A.

On both machines, I have an account set up for this web service to use.  The username/password for Machine A is different from the username/password for Machine B.  The machines are on different Active Directory domains.

The websites on Machine A and Machine B use the same second-level domain, but have different subdomains.

On the page that calls the webservice, I have a block of code that looks like this :

try
{//call the webservice on Machine A
    CacheMaintenance maintain = new CacheMaintenance("local.mysite.com");
    maintain.Credentials = new NetworkCredential("LocalLoginName", "LocalPassword", "LocalDomain");
    maintain.FlashTheCache();
    maintain.Dispose();
}
catch (Exception exp)
{
    errors = "Could not flash local cache.  " + General.UnrollException(exp) + "  ";
}

try
{//call the webservice on Machine B
    CacheMaintenance maintain = new CacheMaintenance("testlive.mysite.com");            
    maintain.Credentials = new NetworkCredential("TestLiveLoginName", "TestLivePassword", "TestLiveDomain");            
    maintain.FlashTheCache();
    maintain.Dispose();
}
catch (Exception exp)
{
    errors += "Could not flash live cache.  " + General.UnrollException(exp);
}   

Machine A has no problem calling the webservice on Machine B.  Likewise Machine B has no problem calling the webservice on Machine A.  However, when Machine A tries to call the webservice on Machine A, or when Machine B tries to call the webservice on Machine B, I get a "401 Not Authorized" error.

Does anybody know why I'm getting this error?

Thanks for your help.

Here's a minor correction to my original post :

Originally, I said that Machine A could call the webservice on Machine B but not on Machine A, and that Machine B could call the webservice on Machine A but not on
Machine B.  After some more testing, I realized this was not the case.

Machine A is a Windows 2000 Server machine.  It is capable of calling the webservice on Machine A and on Machine B.

Machine B is a Windows 2003 Server machine.  It is capable of calling the webservice on Machine A, but not Machine B.

Here are some things I tried :

I tried having Machine B call the webservice on Machine B using CredentialCache.DefaultCredentials.
I tried having Machine B call the webservice on Machine B using CredentialCache.DefaultNetworkCredentials.
I tried having Machine B call the webservice on Machine B using the administrator account credentials.
I tried having Machine B call the webservice on Machine B without setting the credentials at all.

All to no avail.  This seems strange to me.  Why would Machine A be able to call the webservice on Machine B, but Machine B couldn't call the webservice on Machine B with the very same credentials?

I have exactly the same problem. The only difference is that for me machine A is running Windows XP Pro, B is Windows 2003 Server.

A little research suggested that having the WebService impersonate the client might be the key but I've not tried yet.

Any luck finding a solution? Has anyone else come across this?

 

Heh, no luck finding a solution yet.  However, I did upgrade Machine A from Windows Server 2000 to Windows Server 2003.  The result is that, like Machine B, it can no longer call the webservice on itself.  So now we know that :

1) This is a problem with Win2K3 in general, and not just Machine B's specific setup.

2) This is a problem that wasn't present in Win2K.

My guess is that some part of the Windows security model changed between 2K and 2K3.

I kinda gave up on this for a while, but would really like to find a solution.  I was figuring I'd re-post the question to a few forums some time next week.
 

That's a strange problem. This may or may not help, but try this. Instead of Integrated Windows Authentication, swich to Digest authentication and enter your AD domain i nthe configuration. Then switch your credential code to the following:

Net.NetworkCredential userCredential = New Net.NetworkCredential("Username", "Password", "Domain");
Net.CredentialCache credentials = new Net.CredentialCache();
credentials.Add("http://local.mysite.com/wsDirName", "Digest", userCredential);
maintain.Credentials = credentials;
maintain.PreAuthenticate = true;

Hope this helps.

Oops, left something out of the code... first credential argument should have been a URI:

Net.NetworkCredential userCredential = New Net.NetworkCredential("Username", "Password", "Domain");
Net.CredentialCache credentials = new Net.CredentialCache();
credentials.Add(new Uri("http://local.mysite.com/wsDirName"), "Digest", userCredential);
maintain.Credentials = credentials;
maintain.PreAuthenticate = true;

Sorry!

Afro Blanca:

Heh, no luck finding a solution yet.  However, I did upgrade Machine A from Windows Server 2000 to Windows Server 2003.  The result is that, like Machine B, it can no longer call the webservice on itself.  So now we know that :

1) This is a problem with Win2K3 in general, and not just Machine B's specific setup.

2) This is a problem that wasn't present in Win2K.

My guess is that some part of the Windows security model changed between 2K and 2K3.

I kinda gave up on this for a while, but would really like to find a solution.  I was figuring I'd re-post the question to a few forums some time next week.
 

I used to have such a problem.

WebService works fine on XP but result in 401 Not Authorized error on 2k3(setup by others).

I solved the problem by adding user accont

LOCAL SERVICE

NETWORK SERVICE

read and write permissions on application fold.

Hope this helps.

Hello!

 I also have the same problem.

I can't seem to get my ASP.Net Web App to access my Web Service when they are both hosted on the same Windows Server 2003.

I've already tried to switch the account where my app pool works to Local System, but it still doesn't work.

 I've tried giving the permissions you mentioned to my Web Service folder, but it still doesn't work.

Any ideas?

Thanks,

Pedro Feio

Sorry it took me so long to get back to you.  As it turns out, digest authentication works!  Any idea why this would work, but integrated Windows authentication would fail?

Hi,

I tried as you suggested and still get the 401 error. My code is below. Any ideas?

Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
        Dim serviceproxy As New WSBus.ServicesBusWebService()

        Dim userCredential As NetworkCredential = New NetworkCredential("username", "password", "domain")
        Dim credentials As CredentialCache = New CredentialCache()
        credentials.Add(New Uri(serviceproxy.Url), "Digest", userCredential)
        serviceproxy.Credentials = credentials
        serviceproxy.PreAuthenticate = True

        Dim response = serviceproxy.HelloWorld() 'BREAKS HERE
        lblMessage.Text = response

End Sub