Hi Steve,

It looks like the machine SID registered in the DC is different to the local SID on the filer. i.e. someone has deleted the filer from the domain and then put it back in with server manager without re-running CIFS setup on the filer.

Is it an NT4.0 or Win2K environment?

What may have happened is that the DC may have crashed and then was restored using a tape backup that was from an earlier integration period.

i.e.

1. Filer integrated as "Filer" and is allocated machine SID S-.....-2314 (shortened for readability) 2. For some reason later on "Filer" is removed and re-added. CIFS setup is rerun. This time it gets machine SID S-.....-5236 3. DC crashes, is restored from a backup that was taken when the filer had machine SID S-.....-2314.

Whatever the reason, you will probably find there was some human intervention on the weekend :-\

-----Original Message----- From: Steve Evans [mailto:sevans@foundation.sdsu.edu] Sent: Tuesday, 3 June 2003 1:48 AM To: toasters@mathworks.com Subject: Log Entry [CIFSAuthen:CRITICAL]

[CIFSAuthen:CRITICAL]: CIFS - Filer's security information differs from domain controller.

Any idea what causes that? I don't believe any changes where made this weekend.

Steve Evans SDSU Foundation (619) 594-0653

**** ASI Solutions Disclaimer **** The material transmitted may contain confidential and/or privileged material and is intended only for the addressee. If you receive this in error, please notify the sender and destroy any copies of the material immediately. ASI will protect your Privacy according to the 10 Privacy Principles outlined under the new Privacy Act, Dec 2001.

This email is also subject to copyright. Any use of or reliance upon this material by persons or entities other than the addressee is prohibited.

E-mails may be interfered with, may contain computer viruses or other defects. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments. **** END OF MESSAGE ****