Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

User cannot copy .ini file. Huh? 1

Status
Not open for further replies.

humbletech99

Programmer
Nov 22, 2005
155
GB
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
Code:
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

Code:
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?
 
does blah.ini already exist in the target directory he is trying to copy blah.ini to? maybe he doesnt have enough permission to overwrite an existing file.
 
What error messages(s), if any, is the user getting????? Maybe the file is in use (altho I know this shouldn't matter if you are just copying the file.)

Also, I would try renaming the file first. Something like blah.ini.xxx, then copy it, and remove the .xxx after the copy is done.
 
humbletech99... A star for you, I have seen this also but never was able to put 2 and 2 together (didn't have the time to research it). Did you find a way to keep McAfee running and tell it to ignor INI files??



Thanks

John Fuhrman
Titan Global Services
 
no didn't look into that yet, perhaps mcafee is right, lowly users shouldn't be playing with ini files! <evil laugh>

no seriously, I will do something about it if asked but I think the user was gonna work around it.

I actually just went and investigated this for you, you can disable it by doing to access protection, unlocking the user interface and then on the anti-virus standard protection section, on the right untick block box next to "Prevent mass mailing worms from sending email"

That does the trick.
 
not really, it's another layer of protection but one that you can do without, the virus should never get a chance to do anything anyway, mcafee is pretty sharp, it would first have to beat mcafee in order to run and send emails of itself around.

all you are doing is removing a restriction on outbound port 25, that's all.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top