COM and file permissions in a trusted domain

[RoadRacer]

Well, I hope the subject helped and I'm not too far offbase here. =)

I've got a component on my web server which snags a binary file then sends its contents back to the asp page.

My problem is this: When the file is located locally on the webserver, there isn't a problem getting it. The files I really want to get at are sitting in a share on another server in a trusted domain. We have checked to see under what credentials is the COM object trying to get to the file and all we get is a null connection or Anonymous in other words. I've gone into component services and changed the account which Out of Process components use and it seems to have no effect at all. Forget the IUSR account, it's not even attempting to use that account. If anyone out there can help, it would be greatly appreciated. Ed (RoadRacer) Holguin

"I Hate Computers!"

 

[jeepxo]

You aren't authenticated on the server as anything other then IUSER unless you use NTAuthentication when you log onto the website.

That is where your problem is. You access com objects on the web server basically as a service, not as a user. A service on your webserver isn't going to have trusted permission on another domain. This is by design so that you don't open up a security hole on your network.

Think about what you are asking to do here. Log on anonomously to a web server, and then potentially execute code on another computer on the network. Holy security hole Batman!

 

[RoadRacer]

Yep, makes perfect sense and I understand how and why it happens. Fortunately, I figured out how to make it work finally!

Thanks for your reply jeepxo. Ed (RoadRacer) Holguin

"I Hate Computers!"