You are experiencing the classic multi-hop problem caused by NTLM. I
assume you are using integrated authentication between your client and
the IIS box correct? If this is true...you cannot hop from you client
on one box to IIS on another box and then have IIS act as yourself as
you talk to yet another 3rd box. To verify that this is the problem
for sure, trying launching IE from directly on the IIS box and connect
to your application. If you can conect that way, but the exact same
user credentials cannot connect from a client machine that is remote
from the IIS box, then you have with 100% certainty the NTLM multi-hop
issue.
The simplest way around the issue is to configure your IIS box for
Basic Authentication. The box will now prompt you for credentials
whenever you hit it (yes...annoying I know).
The more complex method...and the method that must have been employed
in your previously working configuration is to configure your setup for
Kerberos with Delegation instead of NTLM. Details on this process can
be found here:
http://support.microsoft.com/default.aspx?kbid=828280
psychatricmeuh (AT) caramail (DOT) com wrote:
Quote:
hi!
I have one big problem. I have an app using OWC11. this app is on a
server named "A". the cubes that owc would use are on another server
"B", which is on the same domain than A. After configuring, It works
fine.
But i tried to changed the servers. "C" and "D" are two other servers
which are on another domain than A and B. I have change the
configuration to adapt to them, but if I try to charge the page from
a
station in the same domain, it told to me "the cubename XXXX is
invalid", If i try from a computer in another domain, it timed out.
I don't understand. do you?
thanks |