IIS6 ASP3 web application for configuring an ISA Server is
configured to use Windows account X when accessed anonymously. ASP
VBScript gets error 80070002 when calling the Connect function in the
ISA Server Management API.

Same script put into a VBS file succeeds when the user logged in is
account X.

Why does running under IIS with account X cause the ASP VBScript to

Because the "way" a user is logged on is different between interactive logon
and how IIS does it, for various good reasons (though they can appear
confusing to the unaware... but that is just human nature). Also, actions
against remote servers performed within an ASP page is implicitly "double
hopping" while if you run it yourself it is not.

These are the major differences that account for many of the differences
that one commonly sees, and it is completely intentional and by-design
(since to do otherwise would be insecure... even if you do not realize why).

Though I am expecting differences like 80070005 instead of 80070002, but eh,
things are fundamentally different so anything goes.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
[quoted text, click to view]
IIS6 ASP3 web application for configuring an ISA Server is
configured to use Windows account X when accessed anonymously. ASP
VBScript gets error 80070002 when calling the Connect function in the
ISA Server Management API.

Same script put into a VBS file succeeds when the user logged in is
account X.

Why does running under IIS with account X cause the ASP VBScript to
fail?