Topic: E-Smith still acting like a domain controller !

[Michael Dewitte]

Hi,

I asked e-smith not to be a domain controller, since I have a nt server validating accounts. All was fine 'til I upgraded E-smith to 4.0. At the begining, I haven't noticed anything, but when our nt server was re-started, it told me there was already a PDC on the domain, and that PDC was the e-smith machine, and that it won the election. I checked on the e-smith machine the config, it's still set up with the option 'no controller'. I shut down both machines, then restarted the nt server, and after the e-smith machine, all was fine... I tried the contrary, got the same problem again...

Any clue ?

Mike

[Rogier Spoor]

Hi Mike,

You are right, I had the same problem.

You have to login on the machine.
Just edit /etc/smb.conf and change the domain logons setting to no

you also have to change the setting in the template:
/etc/e-smith/templates/etc/smb.conf/20netlogon


after that do a: samba restart

cya

Rogier Spoor

[Dan]

What would probably be better is to change only /etc/e-smith/templates/etc/smb.conf/20netlogon, and then run /sbin/e-smith/expand-template /etc/smb.conf.  And then, as you said, restart samba.

[Charlie Brady]

Michael Dewitte wrote:

> I asked e-smith not to be a domain controller, since I have a
> nt server validating accounts. All was fine 'til I upgraded
> E-smith to 4.0. At the begining, I haven't noticed anything,
> but when our nt server was re-started, it told me there was
> already a PDC on the domain, and that PDC was the e-smith
> machine, and that it won the election. I checked on the e-smith
> machine the config, it's still set up with the option 'no
> controller'. I shut down both machines, then restarted the nt
> server, and after the e-smith machine, all was fine... I tried
> the contrary, got the same problem again...

Please try the update in ftp://ftp.e-smith.net/pub/e-smith/e-smith-4.0/updates/RPMS/noarch/.

Download the file, then do:

rpm -Uhv e-smith-base-4.0.12-28.noarch.rpm
/sbin/e-smith/expand-template /etc/dhcpd.conf
/sbin/e-smith/expand-template /etc/smb.conf
/etc/rc.d/init.d/smb restart
/etc/rc.d/init.d/dhcpd restart

I've changed the samba configuration to be much less aggressive if  configured to not be the domain controller. As well as being less persistent in becoming the browse master, it doesn't advertise itself as a WINS server, if you happen to have DHCP enabled.

The incomplete netlogon support is also removed, and a permissions problem in ibays is fixed.

I'd be very grateful if you can verify that this fixes your domain controller problem.

Regards

Charlie

[James Brook]

The e-smith-base-4.0.12-28.noarch.rpm stopped the e-smith server from grabbing my domain from the NT server.  Hopefully this will stop my boss from yelling at me

Thanks, James

[Charles Steaderman]

I was having the same problem. None of the smb.conf settings would keep the e-smith box from becomming the primary domain controller. The patch fixed the problem and the system is now co-existing much better.

Thanks.

[Gordon Rowell]

Charles Steaderman wrote:
>
> I was having the same problem. None of the smb.conf settings
> would keep the e-smith box from becomming the primary domain
> controller. The patch fixed the problem and the system is now
> co-existing much better.
>
> Thanks.

We advise all 4.0 users to upgrade to 4.0.1, which includes this patch:

http://www.e-smith.org/article.php3&mode=threaded&order=0

Gordon