Bug 11908 - Windows 7 client cannot join a NT4-style domain when nmbd is started
Summary: Windows 7 client cannot join a NT4-style domain when nmbd is started
Status: RESOLVED WORKSFORME
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: DCE-RPCs and pipes (show other bugs)
Version: 4.2.4
Hardware: x64 Linux
: P5 regression (vote)
Target Milestone: ---
Assignee: Andrew Bartlett
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-07 17:53 UTC by Christian Laborde (mail bounces back)
Modified: 2018-12-09 14:39 UTC (History)
1 user (show)

See Also:


Attachments
samba smb.conf (3.61 KB, text/plain)
2016-05-24 17:32 UTC, Christian Laborde (mail bounces back)
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Laborde (mail bounces back) 2016-05-07 17:53:10 UTC
Since the last samba update (4.2.4-3.54.2) windows 7 clients cannot join domain with the error : « La relation d'approbation entre cette station de travail et le domaine principal a échoué » in english : "The trust relationship between this workstation and the primary domain failed".
If the nmbd daemon is stopped, this error does not happen  but the network cannot be browsed. The mapped shared can still be accessed.
Comment 1 Andrew Bartlett 2016-05-07 19:51:02 UTC
Is this Samba as an AD DC?

What options do you have in your smb.conf?

Note that use of nmbd on a Samba AD DC has never been officially supported.
Comment 2 Christian Laborde (mail bounces back) 2016-05-07 20:21:05 UTC
My samba was long time running with the same config. The only change was an update. I apologize, to update. This is an error.
Comment 3 Christian Laborde (mail bounces back) 2016-05-24 12:10:57 UTC
I upgrade openSUSE with samba 4.2.4-15.1 and the problem has disappeared. Great job !!!
Comment 4 Christian Laborde (mail bounces back) 2016-05-24 17:32:33 UTC
Created attachment 12131 [details]
samba smb.conf
Comment 5 Christian Laborde (mail bounces back) 2016-05-24 17:34:09 UTC
Finally the bug is always in the last version.
Comment 6 Christian Laborde (mail bounces back) 2016-06-01 10:09:36 UTC
If you do not want to give support, do not create bugs. I had a long time well running samba and after upgrade (because no more supported Linux version), nothing function. Users cannot join the domain, browse the network and connect to share (permission problem).
Is always Linux a valid option ?
Comment 7 Volker Lendecke 2016-06-01 11:03:45 UTC
(In reply to Christian Laborde from comment #6)
> If you do not want to give support, do not create bugs. I had a long time
> well running samba and after upgrade (because no more supported Linux
> version), nothing function. Users cannot join the domain, browse the network
> and connect to share (permission problem).
> Is always Linux a valid option ?

Unfortunately bugzilla does not have SLAs. Please contact someone from https://www.samba.org/samba/support/ for paid support if you need someone to just focus on your problem individually.
Comment 8 Christian Laborde (mail bounces back) 2016-06-01 11:09:05 UTC
I have changed anything in my config. I have only upgraded samba. These bug are regression. The problem is not mine it's yours. You break the compatibility, so you must repair.
Comment 9 Andreas Schneider 2016-06-01 12:56:34 UTC
Hello Christian,

Windows 7 doesn't support joining NT4-style domain controllers anymore, see

https://technet.microsoft.com/en-us/library/ee681706%28v=ws.10%29.aspx

There are some Windows hacks to still be able to join described here:

https://wiki.samba.org/index.php/Required_settings_for_NT4-style_domains


However we are not responsible for Microsoft products.
Comment 10 Christian Laborde (mail bounces back) 2016-06-01 14:22:20 UTC
I repeat ; I does not change anything except samba upgrade.
Comment 11 Christian Laborde (mail bounces back) 2016-06-10 05:48:12 UTC
OK ! No support ?
I solve myself the problems by upgrading to samba 3.
Comment 12 Björn Jacke 2018-12-09 14:39:15 UTC
comment 9 said it all. closing this bug.