I have a few spreadsheets that are on my NT 4 server that nobody - even the administrator can access. If I browse to the properties of the file through an XP machine, I can only see a "general" tab - no security or summary tabs. If I attempt to set or view persmissions on the file while I'm on the NT server, it gives me an access denied error. If I attempt to open the file, excel tells me that the file can not be found. I have no clue how these files are getting locked. It almost seems as if no users have permissions to access the files. Is there any type of software that will allow me to wipe the permissions on this file?

Sounds like the file system is formatted FAT and not NTFS, which would answer why you would not see a permssions tab at the file level. Check the file system in disk administrator.
Sometimes an old re-boot may resolve your problem.

If FAT can you access the folder permissions?
If NTFS can you take ownership of the files?

Try taking ownership of a folder above in the structure from the NT Server.

Could be that some bright spark has used XP to set the permissions which NT doesn't understand so it may have got confused?

Regards,
Iain

I've tried taking ownership from the NT server. When it gets to some of the files within the directory, it tells me that access has been denied while applying security information to certain files. This user also tends to fuss with these files from a MAC occasionally.

So its NTFS?  

Files Saved from a Apple Mac?

Can you set silly permissions from the Mac computer?  If so that's  probably the problem.  But how to fix it?

Change the permissions from the MAC creator?

Iain

So the share, is set up as a Mac volume on the NT Server or is the Mac Client (OSX) connecting to the share using "SMB:\\servername\Share"
If it is a Mac Volume, how many files are in the share? From my old NT Memory bank, there is a limitation of 40,000 items per Mac Volume. Strange things start to occur when you hit or get close to that mark.
If you are over that mark, create another mac volume and move some of the files to the new resource.

Sometimes you have to take ownership of individual files. Try that. If you are successful, set the user's permission to CHANGE, and not full control. Users are such a pain in the ...

When all else fails, READ THE DAMN BOOK!