Files hidden from view on a mac

  • Thread starter Thread starter shelby craft
  • Start date Start date
S

shelby craft

Hello,

When up loading files from any of our Macintosh to our windows 2003 server
using the (User Authentication Module (UAM)) people on the macintosh
platform can't see the files but the p.c. people can. We are perplexed by
this issue and are wondering if anyone has any insight to this problem. This
problem is repeatable.

Thanks,
Shelby
 
shelby craft said:
Hello,

When up loading files from any of our Macintosh to our windows 2003 server
using the (User Authentication Module (UAM)) people on the macintosh
platform can't see the files but the p.c. people can. We are perplexed by
this issue and are wondering if anyone has any insight to this problem. This
problem is repeatable.
Click to expand...

Hi Shelby!

Not an answer, but a couple of questions.

If you create a new Mac volume, do you still have this issue with it?
Are you assigning any Windows extended permissions to the shared folder
on the Windows side?

bill
 
Yes, there is a MAC volume, and no extended permission on the windows ahred
drive. this was never a problem until recently.
Any suggestions?

Thanks so much.
 
Liz Cardona <[email protected]> said:
Yes, there is a MAC volume, and no extended permission on the windows ahred
drive. this was never a problem until recently.
Any suggestions?
Click to expand...

And what happens with a new and entirely different Mac volume?

bill
 
Its actually not a new Mac voume, its the same existing volume, we just
started to notice that some files are not showing when using UAM but can be
seen when using SMB.
 
Liz Cardona <[email protected]> said:
Its actually not a new Mac voume, its the same existing volume, we just
started to notice that some files are not showing when using UAM but can be
seen when using SMB.
Click to expand...

I don't think you're understanding me. In my original response, I
suggested you create a new Mac volume and test with that to see if you
have the same results. This is just a means for troubleshooting to see
if the problem is specific to the volume or the entire server.

If you don't have the same problem with a different volume then you
should be able to migrate your data to a new volume and delete the old
volume.

bill
 
Back
Top