[Samba] Samba 3 and Windows Server 2003

[tvsjr]

At 03:12 PM 10/12/2003 -0500, Bryan Haro wrote:
 >Okay, I'm trying to get my samba server to talk to my Windows 2003 domain
 >running in native 2003 mode.  First, while trying to add the samba server
 >with the "net ads join" command, it just wouldn't work.  I wouldn't get an
 >error or a confirmation, I'd just be sent back to the command prompt.  My
 >krb5.conf file is setup properly and when I run a kinit command, it runs
 >fine.   Anyway, I gave up on that as I really don't need full ADS domain
 >membership.

If the directory is running in Windows Server 2003 mode (a superset of 
native mode) then it won't work, from what I understand. I believe this is 
stated in the HOWTOs. You'll need to reconfigure your server and use native 
mode rather than native 2003 mode.

Disclaimer: I have successfully joined a few Red Hat 9 boxes to my Active 
Directory in Native 2000 mode.

 >
 >Now, when I try to join the domain with just "net join" I get a response
 >saying that the samba server successfully joined the domain.  Everything
 >looks good in my smb.conf file and I have corresponding users in the domain
 >and on the linux box so I start up the daemons, go to one of my win 2003
 >servers and try to open a share on the samba server.  Everytime I try, I
 >keep getting a password prompt.  Putting in a domain username and password
 >just brings the password prompt back up.  Here's what my log file says:

I'm having the same problems, but in the other direction - the Samba box 
won't read a share on the 2k3 Server box, while it will from a 2000 box. 
This has been isolated to being a problem with too-old versions of the MIT 
krb5 libraries (for instance, the newest RPM you can get for Red Hat 9 is 
1.2.7-14, while MIT is up to 1.3.1, which is supposed to work with 2k3). 
There are additional problems when trying to rebuild Samba to point at 
newer krb5 builds - check bug 433 in Bugzilla 
(https://bugzilla.samba.org/show_bug.cgi?id=433). This bug has been 
assigned, but has yet to be totally fixed. I'm going to assume you're 
experiencing the same failure mode, just in the opposite direction.

For now, Gavin Davenport (gavdav at gavdav.demon.co.uk) has built a 
workaround, although I have yet to try it (been working on methods to run 
Linux on an SGI O2 - if anyone has any suggestions, please contact me 
direct!).

Hope that helps...

Terry