12-17-04 10:52 PM
Fair enough. The control:
1) attempts to instantiate a Winsock object and connect to a remote host. It
transfers some data with that host and then closes the socket;
2) It attempts local file I/O to write a log of its actions;
I looked at http://support.microsoft.com/?kbid=198432 and gave
IUSR_MachineName the Registry Value Permissions alluded to therein. I think
your emphasis on a 'permissions' problem is along the right lines. However,
what permissions and how do I change them? I'm prepared to give
IUSR_MachineName wide open machine access for debugging purposes if
necessary.
Thanks,
- Andrew
"Aaron [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message
news:e9qOTRF5EHA.2804@TK2MSFTNGP15.phx.gbl...
> ASP-specific
>
> I didn't object to that.
>
> However, to help determine WHY it might be a problem in ASP, it would help
> to know WHAT the object does. For example, ASP by default runs in the
> context of IUSR_MachineName, which has a very different set of security
> credentials than you do when you run an HTML page or VB application.
>
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
[ Post a follow-up to this message ]
|