>Ed,
>
>I have learned from the Microsoft support site that your SWAG is probably right on. The currently logged user on the server does not seem to matter.
>
>As for User Context, I think if I knew that I would have the problem solved. Is this set using DCOMCNFG? That so far is all I have played with. I have experimented with a few of the security settings in DCOMCNFG, but must confess that I am going trial-by-error with no understanding of the underlying theory, and am not getting anywhere.
>
>Do you know the simplest settings that just give the COM Server network access? Can you point me to a FAQ or white paper?
>

The identity tab of the DCOMCNFG property sheet lets you establish the userid that the DCOM server will run under. In all probability, the server is presently running in the context of IUSR_server name, so one option would be to grant the necessary access rights to that userid. You might want to pick up Rick Strahl's book Internet Applications with Visual FoxPro 6.0, which discusses some of the issues and options.

Another technique is to make your network connections on the fly using an API call like WNetAddConnection3(), which permits you to make a network connection with a specified userid and password. There's sample code for this in my NETRESOURCE class downloadable from here on UT. You'll want to make/break connections within method calls in all likelihood.

>TIA...
>
>>>Folks,
>>>
>>>I have a DCOM server that is freezing whenever it accesses a network drive. The routine in question does just fine when it accesses the remote server's local drives.
>>>
>>>I assume this is some type of security thing, but I am in over my head, can anyone help?
>>>
>>
>>Just a SWAG, but what user context does the server run under? It does not inherit from the currently logged in user by default.