• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

What's the best linux solution for replacing Windows NT BDC?

FreshPrince

Diamond Member
I need the new server to host the following functions:

File Server (both Windows and MAC)
Print Server
WINS
Ability to pass domain information to Exchange 2000 server running Native mode(optional)

which linux distro? samba version?

thx!

- FP
 
Last I checked Samba can't be a BDC.

Ability to pass domain information to Exchange 2000 server running Native mode(optional)

Samba can join an NT 4 domain or just authenticate through it, but I'm not sure what you mean here.
 
I know this isn't what you were asking, but I'd really say stick with NT or go 2000. If the client computers are Windows NT, NT servers will be a lot easier to share everything with. As far as being a BDC, I'm not sure you can do that with Linux (at least I haven't heard of it). Samba is ok as a fileserver, but I've found it to be flaky at best, and it is certainly a lot harder to set up than Windows file sharing. JMHO.
 
Samba is far from flaky, I have a box at work thats been running for over a year now and it's needed no attention from me. It's a little more setup work than right->click->sharing but it's not rocket science.
 
I know samba can be a PDC, but not sure about BDC. Although, if it can be a PDC, then being a BDC shouldn't be that different.

As for windows 2000, I need samba to be the middle man between windows 2000 AD domain and NT DS domain so that my NT users in domain A can get to the Exchange 2K box sitting on my DMZ in domain B. Right now I have a trust between AD and DS so that exchange knows which AD user ID associates with which NT user ID. Does this make sense Nothinman?

Rainsford,

my boss wants me to experiment with different thing cause he doesn't want to pay the upgrade service fee come July. I'm loving M$ less and less everyday.

anyways, does anyone have real world experience with samba + NT networking? I need some suggestions.

thx
 
As for windows 2000, I need samba to be the middle man between windows 2000 AD domain and NT DS domain so that my NT users in domain A can get to the Exchange 2K box sitting on my DMZ in domain B. Right now I have a trust between AD and DS so that exchange knows which AD user ID associates with which NT user ID. Does this make sense Nothinman?

You basically want the users in the NT domain to be able to authenticate against the AD without being a part of it, so they can get their mail? May I ask why Exchange 5.5 wouldn't have worked?
 
Originally posted by: Nothinman
As for windows 2000, I need samba to be the middle man between windows 2000 AD domain and NT DS domain so that my NT users in domain A can get to the Exchange 2K box sitting on my DMZ in domain B. Right now I have a trust between AD and DS so that exchange knows which AD user ID associates with which NT user ID. Does this make sense Nothinman?

You basically want the users in the NT domain to be able to authenticate against the AD without being a part of it, so they can get their mail? May I ask why Exchange 5.5 wouldn't have worked?


that's already happening, I just want to make sure samba can do the same thing. Also, e2k was already implemented, not really my choice.
 
If your running AD in Domain Emulation mode... then Samba will be fine..

Also note that the new version of SAMBA is now in testing... it has full AD Support including the ability to be your whole AD infrastructure totally replacing Windows, as well as just normal authentication of users against AD...
 
Back
Top