Scott,

I'm plodding through the same set of discoveries myself right now.

It turns out that the COM server, when launched on a remote machine, has no connections, and its "user" has nothing to do with the logged machine on either the server or the workstation. You have to run DCOMCnfg and specify who the program is when it is logged in.

Next, you (apparently as AFAIK at this point) then have to create network connections as you need them in the COM server code. Ed Rauh pointed me to use of an API Call like WNEtAddCOnnection3(), but I haven't pursued it yet.

Hope this helps.

>I am crawling through the development of a small COM Object that has to check a number of directories for a file on a remote resource. We have 90 offices that complete daily file transfers via dialup to a ras sever. When they have completed the transfer a file is ftp'd to the RAS server (i.e dnld.ok). Our help line staff would like to view a list off offices that have that file in thier directory via the browser along with some other things. Each office has a directory associated with thier office code containg several subdirectories. When I started I was thinking of taking the adir() getting the list offices, checking each for the file, building a HTML table and passing the list back to ASP. I am using NTLM, NTFS, IIS 4.0., and a trust has been established across the two domains. I can map a drive from the web server to the RAS server if that helps. I am looking for a solution to this particular problem but also if someone could point me to some "good" info regarding this whole
>security/access to resources scenario with NT and IIS. I have read numerous acticles talking around how to access NT resources but nothing said how to actually do it.
>
>Thanks again
>
>
>Scott