Hi Louis,
Thank you for sharing with us the update.
I wonder if there is any change on samba / configuration which may lead to sudden failure.
What is the samba version in use?
Is it a stock samba?
May I know if there is any chnce you could follow the steps below to collect us log files?
1. Login to the samba server and run where username is the Centrify user who is attempting access to the Samba server.
# adquery user -A <sambausername> > /tmp/adquery.txt
# smbclient -k -L <hostname> (this command will list Samba shares)
2. Using your favorite editor, edit the /etc/samba/smb.conf to include the following lines in the [globals] section as follows:
[globals]
...
log level = 10
log file = /var/log/samba/smb.log
max log size = 0
3. Run below command after saving the changes to verify any syntax errors in smb.conf:
# testparm
4. Restart Samba to get it to pick up the smb.conf changes right away by running:
# /etc/init.d/smb restart
5. Turn on debug:
# /usr/share/centrifydc/bin/addebug on
# /usr/share/centrifydc/bin/addebug clear
6. If Accessing the share from Unix, please go to step 7
For troubleshooting Samba issues from Windows, you need a tool like Wireshark. If you do not have it, please download it from the below location:
http://www.wireshark.org/download.html
Note: Wireshark is NOT a Centrify tool.
Log out of Windows and login again or simply lock and unlock to get a new Kerberos ticket. Start a network capture using Wireshark. Attempt access to the share in question and let it fail and note down the username.
7. On client Unix machine, start capturing network trace using tcpdump:
Start the network trace:
For Linux machines: tcpdump -i <ETHERNET INTERFACE NAME> -s 0 -w <NAME FOR THE FILE>
Example:
tcpdump -i <ETHERNET INTERFACE NAME> -s 0 -w /tmp/login.pcap
For Solaris machines: snoop -d <ETHERNET INTERFACE NAME> -s 0 -o <NAME FOR THE FILE>
Example:
snoop -d ge0 -s 0 -o /tmp/login.pcap
Let the affected user access the samba share to get the issue reproduced.
Once above is done, hit Control + C to stop the trace.
8. After the issue is reproduced, Go back to Samba server& Run the following command:
# adinfo -t
9. Turn off debug on Centrify-enabled Samba server:
# /usr/share/centrifydc/bin/addebug off
10. Send in the following by email or ftp:
a. /var/centrify/tmp/adinfo_support.tar.gz
b. tar of /var/log/samba/
c. /etc/samba/smb.conf
d. /tmp/adquery.txt
e. network trace from Windows. Save it with an extension of pcap.
11. Revert changes made above
Once the log files are collected, please kindly share with us by sending to communitysupport@centrify.com.
We are looking forward to hear from you.
Best Regards,
Alan Ho