i have two F330s, both at 4.3R4, both running CIFS. apart from the number of shares on each one, and the machine names, the CIFS setups are supposed to be identical.
one will authenticate through a PDC, and one won't. we have been through the old "create a domain account for the server" thing *many, many* times. it's not helping. when we try to "cifs setup" to use the PDC, we get the following joyous dialogue:
Tue Jan 27 18:07:18 EST [rc]: Connection with DC BIGDADDY terminated Tue Jan 27 18:07:18 EST [rc]: CIFS - Filer retrying authentication with backup password. Tue Jan 27 18:07:28 EST [rc]: Connection with DC BIGDADDY terminated Tue Jan 27 18:07:28 EST [rc]: CIFS - Filer's security information differs from domain controller.
and, in many cases, cifs will sit there trying to shut down, locking up the console, until i reboot the filer. it's been suggested to me that it needs to authenticate as part of the shutdown process.
so, my questions are: 1) what flaming backup password? 2) what decides whether cifs starts up at boot time, absent a "cifs on" rc entry? 3) is it true that the delayed shutdown is caused by failure to authenticate? 4) has anyone else had trouble going from X to 4.3R4, esp. if X=4.0.1c{,D10}?
and, if were allowed a slightly less serious wish list, any chance of an option such as options no.stupid.microsoft.authentication on to get the CIFS support to authenticate based on the user logged into the NT Workstation in question, a la NFS? or do i misunderstand terribly what's going on here?
Tom Yates - Unix Chap - The Mathworks, Inc. - +1 (508) 647 7561 MAG#65061 DoD#0135 AMA#461546 1024/CFDFDE39 0C E7 46 60 BB 96 87 05 04 BD FB F8 BB 20 C1 8C