Slashdot Mirror
Samba 3.0.0 Released
Matt writes "As posted on Samba.org the fine folks at Samba.org released their newest version of the popular free Windows File- and Print Server. Most famous additions are Active Directory integration and possibilities to form NT4 trust relationships. Release notes are online." See also their press release.
..at O'Reilly's Safari Bookshelf!
Congrats to the Samba Team!
I'm not entirely sure what you're talking about. I'm running Samba at home, and my XP boxes can pick up the shares on it just fine.
You may need to add smbpasswd entries for the machines users, but other than that, it should be ok.
They're really very professional, and a pleasure to work with.
--dave (the Using Samba 3rd author) c-b
davecb@spamcop.net
I quite happy with this new release, what I like the most about it is the new Active Directory support, I have been waiting for it since I started to use it in my homenetwork. Another impressive feature is UNICODE support (isn't mentioned in the post), one of my family members needed it badly to deal with non-latin charsets.
And the new "get" command which is similar to windows "net" is useful too.
Keep up the great work SAMBA team!
The IT section color scheme sucks.
Samba 2.2.x + XP + SP1 requires some tweaking to do domain logons for XP clients.
:)
Basic file sharing is fine, but if you're using Samba as a domain controller, you need to set a SignOrSeal reg value off to allow domain logons and also unset a "check profile ownership acls" setting which was introduced by SP1.
-- Someone who uses Samba 2.2.x as domain controller for several hundred XP boxes
I've experienced numerous random lockups using samba v3. The mount point would just hang requiring a samba restart.
After searching for a while, I found that there's a bug in Redhat 9's new thread library which samba somehow triggers. There's a workaround on the net, look for it and avoid hassling the samba team - they're not at fault here!
It's accessable from the MMC on each client machine, or alternatively if you have a recent enough samba, there's a "profile acls = yes" option you can set in the smb.conf
It's a fair enough question.. one that someone asked Tridge at LCA2003.
;)
Basically no.
Buffer overflows in RPC are due to server programming, and since both are entirely different server codebases, they don't share vulnerabilities. But the Samba team have found many of these RPC bugs with windows
You could do this with 2.2.8a if your AD server allowed anonymous authentication. If not, you need 3.0.0.
See how we do it on Mandrake (since 9.0).
I run a Mandrake 8.2 box in production as a mail server in an AD domain, all authentication is via winbind.
Yes, use pam and the winbind. I can ssh to my samba box and authenticate against Active Directory. There are how tos out there, here are a few links I used. http://www.netadmintools.com/part172.html http://www.flatmtn.com/computer/Linux-Samba3.html http://us1.samba.org/samba/docs/man/winbind.html
One thing that does change with Samba 3 is the way that you need to configure Squid to use NTLM authentication...
If you upgrade and try using the old authenticators built with squid, you'll be stuck. Samba 3 comes with it's own helper utility (ntlm_auth) to work with other applications such as Squid.
I have written a Samba 3 / Squid Walkthrough that takes users step by step through getting this going.
Find out about it here:
http://itmanagers.net/article-4--0-0.html
Why dont you configure samba as PDC and use LDAP for all the authentication purpose?. I found it a robust solution. The beuty is that you can use it as a back end for any services/servers which requires authentication and can act as a truly single source of authentication. All the requirements you mentioned is possible with this.
http://www.nasirudheen.blogspot/
There is an easy fix to this for XP:
Settings -> Control Panel -> Admin Tools -> Local Security Policy
Look under Local Policies, then Security Options.
Look for "Domain Member: Digitally encrypt or sign secured channel (always)" and set it to DISABLED.
That should solve some of your problems.
XP only wants to trust other Windows machines when working in a domain environment.
XP Home does not allow logon to domains, so there's no problem to fix.
Actually, I think the most important feature is this:
10) Support for migrating from a Windows NT 4.0 domain to a Samba domain and maintaining user, group and domain SIDs.
Why? NT Server is coming to the end of support period (Dec 2003). There are still LOTS of NT4 server out there. Last time I checked, you had to recreate ALL of the groups and users whenever you migrated them from NT4 to any other PDC (there is a little support for automating this activity, but it just saves you from retyping the users and groups names).
My other OS is the MCP!
Not any more. We implemented sign&seal for Samba 3.0.
If it doesn't work when you remove this please log
a bug at bugzilla.samba.org.
Thanks,
Jeremy Allison,
Samba Team.
It's probably the Web sharing service. Turn off the client :-).
side on the XP box. It tries to contact a port on the Samba
server that isn't open and times out. Sorry, I can't remember
the exact instructions to turn this off (I only use Windows
under VMware to test Samba
Jeremy Allison,
Samba Team.
I wouldn't do it. And I write lots of the Samba code :-).
The protocol is just too complex to be sure any implementation
is safe.
Hopefully that should tell you something. It should also
tell you why we don't want it in the Linux kernel. Microsoft
put it in their kernel - I think that's a mistake.
Jeremy Allison,
Samba Team.