Ok, so you touch on a few different things in your question…
Your issue doesn’t appear to be a problem with authentication, but maybe routing or DNS. We have the exact opposite happen in our environment. When our 2003 server is rebooted, Mac clients can’t browse for the shares being shared out over Services for Macintosh.
Does this affect your Mac clients? Remember, you’ll want to browse with the Macs over SMB, since your Windows clients will be using SMB, not AFP.
You mention a Windows 2003 DC…do you have a split environment? Like one 2003 DC and one 2000? It seems by how you posted that you might. If that’s the case, best practice is to create keytabs on the 2003 server. We found that out in my environment a couple months back.
Samba doesn’t require keytab files to be created to work with AD’s Kerberos. You simply need to edit your smb.conf file located in the /etc directory. If you want AD’s Kerberos to work with Mac OS X Server’s AFP service, then you have to create the keytab files and install it on your server.
Comments are closed