Yes, while this problem appears basic, but it is really Cross-Machine
Delegation, which is a very advanced security implication.

You will find that if you use Basic authentication or coordinate
Anonymous user logins that it works, but it fails if you use
Integrated Authentication.

The protocols which work by default are all insecure with regards to
delegation, which is a non-obvious security concept.

We can certainly go into more details as to why it fails with
Integrated Authentication by default and how to make it work, but
suffice to say, it is well documented. One easy way to explain the
concept is:

Suppose you go to an auto shop to get your car serviced. Instead of
asking you to sign for repair authorization, they asked for your SSN.
What do you do?

The insecure authentication protocols will simply hand over the SSN.
The secure authentication protocols say "no, I won't give you the SSN
unless you go through validation that you safeguard and absolutely
require my SSN".

Now, with a W2K domain, the only way to make Integrated Authentication
work is to use Kerberos. With WS03 domain, you have many more options.

//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

On Mar 21, 10:36 am, guruperplexe
<guruperpl...@discussions.microsoft.com> wrote: