search for: schaefert

Hi folks, I've been testing out Windows Vista Enterprise today. It defaults to only using NTLMV2 authentication. I'm testing with Samba 3.0.23d running on Sparc/Solaris 8. Samba is configured with security = domain The password server is a Windows Server 2003 domain controller. I've joined Samba to the domain. I simply can't get Vista to connect unless I change its security

...as, with Samba 3 you can't. I'd REALLY like to see that come back to smbstatus. Here's a real world example of my complaint... Samba 2 smbstatus output... Samba version 2.2.8a Service uid gid pid machine ---------------------------------------------- htdocs schaefert cfusion 8004 medusa (192.168.0.5) Fri Jul 30 09:21:18 2004 optometry schaefert cfusion2 8004 medusa (192.168.0.5) Fri Jul 30 09:21:22 2004 Samba 3 smbstatus output... Samba version 3.0.2a PID Username Group Machine ------------------------------...

More precisely what I've discovered is, at least in the cases of 2.2.8a and 3.0alpha22, when a 64-bit Samba is built with Sun's Forte compiler you'll end up with something incompatible with Mac OS 10.2.3. I always compile Samba myself with Sun's compiler to produce a 64-bit Samba. Well yesterday it came to my attention that Mac OS 10.2.x doesn't work with whats on my main

Sparc Solaris / UFS file system. I have some ACL's set up for a handful of users and its all worked flawlessly with every incarnation of Samba I've used over the past couple years, which would be most. Last Friday evening I upgraded from 3.0.11 to 3.0.13 and some of the users I have some ACL's set up for promptly found Monday that they couldn't save new Excel files, they'd be

Hi, I've spent a lot of time digging the last couple days and seen some talk about how now with 3.7.1p1 the PAM challenge response requiring keyboard interactive on the client is "right" and no longer a kludge. I understand that. Unfortunately I've got a bunch of users who's client (www.ssh.com's client version 3.2.3) doesn't function without a kludged server.