User cannot copy .ini file. Huh?

[humbletech99]

I've got a user who connecting to a Windows 2003 Terminal Server. He has permission to write to all the directories in a tree on the d: drive. He is trying to copy a .ini file to another directory in the same tree but is unable to.

This is most puzzling because he can write to the directories, he can copy another file or copy the blah.ini file to another name in the target directory.

From cmd, he is doing

copy blah.ini ..\
access is denied
0 files copied

It seems ridiculously simple, but I can't see any reason why the thing shouldn't work, the user has write permissions to the directory above and can do the following successfully

copy blah.ini ..\blah.txt

So it seems that this is isolated to the .ini extension and not a permissions issue.

So is there some security measure that stops an ordinary user from working with .ini files? Or is it something specific to Terminal Server 2003?

[ɹəuəllıʍ ʇɐb]

I do not have too much experience with Terminal Servers, so I may just be fishing here.

1) does this happen with any .ini file?

2) if only with that one specific .ini file, the source file may be protected (e.g. in use).

[humbletech99]

no, turns out it was mcafee blocking it.