[Samba] (SOLVED) Runnung samba4 as classic domain controller, win7 thinks it is AD

Michael Tokarev mjt at tls.msk.ru
Sun Dec 7 03:34:15 MST 2014

Ok.  The prob was, as usual, as stupid as ever possible.

My nmbd process hasn't been restarted for a very long time,
even if I stopped and restarted samba multiple times.  It
looks like a prob in the startup script or in samba handling
of pidfiles or something -- because `stop' action is unable
to find a running "old" nmbd (and there's no pidfile of it),
and new nmbd can't be started because it can't bind to the
sokets.  nmbd logfile is empty for a long time too.

So basically I have a stray nmbd which did not do anything
useful but prevented real nmbd from starting.

Killing it manually and starting real nmbd helped, and now
I successfully joined a win7 machine to a classic NT4-style
domain running by samba4.

So Andrew's suspicion was exactly right.  But the cause was,
well, fun.

Thank you very much for the help!


More information about the samba mailing list