search for: ad2000

...tic googling later it is clear that Windows -really- wants to use kerberos keytype 23, a. k. a. "arcfour-hmac-md5", which that particular version of MIT kerberos won't digest. My doubt right now concerns a statement that this "arcfour-hmac-md5" choice applies already in AD2000 -- so howcome it works? (A) The 2k AD supports other types as well and makes peace with MIT krb5 whereas 2k3 AD has been lambasted out of such fraternizing habits, (B) The 2k3 AD would support other types after the proper Magic Handwaving, i. e., tweaking of some well chosen regis...

...main as a simple file server. Any reason this won't work? Your experiences? Your wisdom? One final question: Can Exchange 2003 be made to authenticate against a Samba domain? I would expect not, since a Samba domain is mostly an NT4 equivalent and Exchange 2003 requires a domain at least at AD2000 functional level. Maybe AD2003 functional level. ~Jonathan Johnson Sutinen Consulting, Inc. jon@sutinen.com

Okay, I'm at wit's end, and am about ready to give up on Samba 3.x as a way to implement single sign-on. I would like to know if there's anyone out there who has the following environment: - Solaris 8 and 9, running NIS (not NIS+) for automount and passwd/group maps - W2K-based Active Directory I'm trying to get Solaris authentication to work using AD user accounts. According to

Hello all. AIX 4.3.3 / Samba 2.0.6 / Production NT4.0 domain Security = DOMAIN encrypt passwords = yes update encrypted = yes Action: Moving from NT4.0 domain called nt40 to AD 2000 Domain called ad-domain Problem: Users that have been migrated to ad-domain cannot authenticate to AIX SAMBA shares . . . the AIX SAMBA server is still part of the nt40 domain. Explanation: I can however, map /