You will need to set up the remote Samba as a BDC, and use LMHOSTS or WINS so the clients (Windows?) can find the domain controllers

 

I am not sure if Samba can do WINS replication, but even if you only enable WINS support on the First Samba box, when a windoze box queries it for a domain controller it “should” pick the one that is on the same subnet. My experience is that this works about 95% of the time. But on occasion a 2k or NT box will get a hard-on for a domain controller that’s a bazillion miles away. (You guessed it > reboot! <)

 

If the link is down, they will authenticate against the local Samba box, since the last resort is to broadcast. They just won’t be able to change anything. (The only read-write box is a PDC)  

 

The Clients will all need to see the Samba PDC though for things like password changes, joining the domain etc..

 

Robert Toole

[EMAIL PROTECTED]

 

-----Original Message-----
From: Kevin Anderson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 05, 2002 11:18 AM
To: [EMAIL PROTECTED]
Subject: (clug-talk) Samba Question.

 

If I set up 1 Samba PDC here in Calgary for a group of users here, and I set up another Samba server hundreds of miles away (Ontario and Tulsa) across a VPN (or a leased line), for another group of users, will the remote users be authenticated by their remote server, or the one in Calgary?  Is there a way (other than having multiple domains) to protect this against outages in the connection?

 

Kev.

Reply via email to