Slashdot Mirror
Samba-TNG Team Releases 0.3
emissary47 writes "The Samba-TNG (the next generation) team, releases the
first beta of Samba-TNG (a Samba fork since 2000) including some very interesting features for everyone willing
to replace NT4 domain controllers. With excellent LDAP-backend support,
integration of Microsoft tools such as usermanager for domains and
servermanager and a powerful command-line tool called rpcclient it is
_the_ alternative solution for Windows domain controlling at the moment.
They even include scripts for NT4-server migration in order to make a
change easier."
This was a show-stopper for us only last week - trying to find a reasonably easy way to get Samba supporting NT LANManager v2 authentication? Anyone?
"None are more hopelessly enslaved than those who falsely believe they are free." -- Goethe
late I dont think so
even MS will admit that they cant get people to move from NT to XP or 2k
this is right on time ! because people will start to find NT is no longer supported by MS and move what they move to might just not be Microsoft based because its too expensive hence samba TNG
but what I want to know is this
can samba-TNG be a real PDC and comunicate to a NT BDC all the information such as the userlist AND when it falls over and comes back up (system maintenance) take back the PDC status and any changes from the BDC ?
acting as a PDC and syncing with a NT BDC is what SAMBA really lacks IMHO
regards
John Jones
I guess I should have read the status page. Let me rephrase the question: what are people's experiences with this?
Does'nt suppoort "File locking" or "File ACL Support". I've been able to use ACL support in Linux after compiling. Is File Locking critical? I'm mean what can happen to a file it more than one person opens a file, does it allow them to save over each other's version?
I just wish they'd start adding graphic control tools... that'd make moving way easier.
Does it have graphical configuration tools like NT4?
How many modern software programs allow concurrent editing of a document by multiple people? (where the applications cooperate in modifications to the data structures of the document and don't clibber each other) Excel? Word?
Granted I didn't work at it for that long, but I did attempt to get Word2000 to do this for a few medium sized documents a while ago. My experience was that there was no way to dynamically decide what part you wanted to work on, you had to declare the divisions ahead of time and then could use their master document approach (or whatever they called it). Basically, you declare a bunch of document sections, which are then stitched back into one document. A little clunky and made keeping a version archive pretty nasty, links got fouled up all overthe place.
Given that it was a small group of people working on the documents, and the master document approach seemed to foul a few things up, we found it easier to have someone in control who could manually split out the necessary portions and reintegrate later. Bloody waste of time.
The whole thing about 90% people using only 10% of the capability of Office is right on, the useful features are often missing or very hard to figure out. Not that I have a clue what takes up most of the space in office... clipart maybe?
So what exactly are the advantages of TNG over TOS (The Original Samba)? And I don't mean 2.2.x, but the 3.0 developement series.
This is your sig. There are thousands more, but this one is yours.
http://howto.aphroland.de/HOWTO/LDAP
no way in hell could it withstand the slashdot effect, it runs ontop of Zope which is slow enough as it is! Apache seems to be in the order of 2000x to 2500x faster then zope+Zwiki, but the features of zope make it worth it.
Looks good, too bad if I do a:
wget -m -GMETA http://howto.aphroland.de/HOWTO/LDAP
It doesn't do anything useful.. You don't run standard HTML (which is understandable), and all your links are hard links. I suppose I could 'sweep' the sctructure, and replace 'map' with index.html, and remove the hostname from all the files.. ugh. I'll just bookmark the damn thing.
Bummer.. I'd hold a copy on my dinky Cable for temp use (and my own use)
"I can't give you a brain, so I'll give you a diploma" - The Great Oz (blatently stolen sig)
I noticed on their status page that they don't support printing. This seems like a kinda huge issue.
Did I mis-read it?
The more I learn about science, the more my faith in God increases.
Older but still heavily used DOS based Medical and Accounting packages WILL NOT reliably use a samba machine for a SMB share. a NT server will do it fine, but samba, including the latest and greatest will not. it keeps losing data or losing the connection.
Cince most doctor offices still use Dos based medical software, and Most companies still use their DOS based Accounting software (Quickbooks is a Joke compared to these real accounting packages) any migration of their servers to linux spells doom.
I've waited for over 4 years for this issue to be dealt with and it seems that the samba team is not interested.
I personally wouldn't use these old (but still cost thousands today) apps.... but you cant tell a customer that to save $400.00 on their server they need to spend another $5500.00 to change their software suite and spend 100-200 hours manually keying in the old data into the new system.
companies are funny that way.
Do not look at laser with remaining good eye.
This is extremely attractive - it's just jumped to the top of my list of things to test.
I manage an IT section for an organisation of 110 people. We use NT4 and Linux for our back end servers (there's a couple of HP's but who counts them as serious boxes) and are well aware of the Microsoft EOL issue.
What people need to remember about NT is not just the cost of the server OS, but the per client costs (yes - you pay for each workstation that can connect to the server) and the ongoing problems of license management.
The idea of migrating from a stable working server base (yes - you can get NT4 stable if you work at it) to Windows 2000 and the whole active domain morass is a tough one to consider. Moving to Linux would be a lot easier, as the only NT thing I need is Exchange. This would allow me to replace everything but the mail server with Linux, and then I can start looking at that SUSE exchange replacement product.
Once Samba TNG is as stable as NT4, it means that the only credible place for Microsoft products in my organisation is on the desktop. If Sun can get Star Office on an even (or higher) par with MS Office, I can start pruning that out and simply stick with the Microsoft OS that comes with the hardware.
I repeat - this is extremely good news
Err - both Samba-TNG and Samba support this (byte-range :-). That's why you can use Samba for these multi-user :-).
locks). Out of the box. We have done for years. I wrote the
code
apps
Jeremy.
The status page notes that NT trusting Samba-TNG works. What it doesn't mention is that the converse also works, but requires a certain amount of manual setup and fiddling. This is one thing we'd like to polish up for the next release. (:
(People's experiences? Sorry, not my department, I don't use trusts..)
"How can you claim that you are anti-crack, while still writing a window manager?" — Metacity README