Re: SetCurrentDirectory question

• Previous message: NMD: "SetCurrentDirectory question"
• In reply to: NMD: "SetCurrentDirectory question"
• Messages sorted by: [ date ] [ thread ]

Date: Tue, 7 Sep 2004 12:53:16 -0700

Don't you get ERROR_ACCESS_DENIED after FindFirstFile
fails?

I suppose the network redirector does not check the permissions
on the underlying directory when you set the current directory,
it only checks the permissions on the network share, that's why
your SetCurrentDirectory call succeeds.

-- 
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================
"NMD" <NMD@discussions.microsoft.com> wrote in message 
news:92A0B614-07D4-40B3-8701-836D856DB2F8@microsoft.com...
> This may be a stupid question, but I will ask it anyway, as I can't find
> anyone on the web who has ran into the same problem.
>
> If for instance, I am on a machine that has a particular directory(\foo 
> for
> instance) secured, i.e. I do not have permissions to look inside, if I
> execute the SetCurrentDirectory call to set the current directory to this
> directory, I get a failure(5), as expected.
>
> However, if I am on a remote machine that can access this system, if I 
> issue
> the SetCurrentDirectory call using the share path, i.e. 
> \\remote_server\foo,
> I do not get an error.  It does appear that I am being blocked, as this
> particular piece of code is unable to list any files in this directory,
> however, the SetCurrentDirectory call does not fail, as it did when ran on
> the actual machine.
>
> This makes it difficult for us to determine if the failure to find files 
> was
> due to the fact that the directory is empty, or we do not have the right
> permissions set up.
>
> Any ideas?
>
> Thanks,
> NMD 

• Previous message: NMD: "SetCurrentDirectory question"
• In reply to: NMD: "SetCurrentDirectory question"
• Messages sorted by: [ date ] [ thread ]