net rpc join fails in Ubuntu 16.04

Bug #1585111 reported by Andre Bacao
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Expired
High
Unassigned

Bug Description

Trying to join a machine to a domain.

This worked well in 12.04

smb.conf
[global]
security = domain
netbios name = LD7vb2
realm = DOMAIN.COM
# originally we had "password server" but this is the recommended setting
wins server = ipbrick.DOMAIN.COM
workgroup = DOMAIN
# programatic UID calculation to make UIDs uniform accross machines
idmap config * : range = 2000-302000
idmap config * : base_rid = 0
idmap config * : backend = rid
winbind separator = +
winbind enum users = yes
winbind enum groups = yes
winbind use default domain = yes
#template homedir = /home/%D/%U
# WA folderview vs long paths
template homedir = /home/%U
template shell = /bin/bash
client use spnego = yes
domain master = no

Cant use it on Ubuntu 16.04

doing: net rpc join -U administrator
Result:
No realm has been specified! Do you really want to join an Active Directory server?
Enter administrator's password:
smb_signing_good: BAD SIG: seq 1
Failed to join domain: failed to lookup DC info for domin 'DOMAIN' over rpc: Access denied.

Can use: smbclinet -L ipbrick -U administrator and see infos about the server.

What can I do to join my machine to a domain with "net rpc join"?

Revision history for this message
Andre Bacao (andre-bacao) wrote :

Also tested with:

client ipc signing = auto
client ipc signing = disabled
client ipc signing = mandatory

in smb.conf and nothing worked.

No realm has been specified! Do you really want to join an Active Directory server?
smb_signing_good: BAD SIG: seq 1
Failed to join domain: failed to lookup DC info for domain 'DOMAIN' over rpc: Access denied

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1585111/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → samba (Ubuntu)
tags: added: xenial
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in samba (Ubuntu):
status: New → Confirmed
Changed in samba (Ubuntu):
importance: Undecided → High
Revision history for this message
Barış İNANÇ (baris-x) wrote :

This bug is affecting me after upgrading 14.04 to 16.04. Cannot login to AD after upgrade

Revision history for this message
XaTTa6bl4 (xatta6bl4) wrote :

Does anyone have temprory solution to fix that?

Revision history for this message
ghomem (gustavo) wrote :

Adding the line

client ipc signing = auto

on the Ubuntu 16.04 client fixes the problem for recent server versions of samba. Tested successfully with

samba 2:3.6.6-6+deb7u6

on the server.

For earlier samba versions (ex: 3.5.x) the extra client does not help. Don't know from which version on the samba server starts to work with this extra line.

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

What is the server controlling the domain you are trying to join? Another samba? Or some version of windows?

Revision history for this message
Hubert Higelin (hh68300) wrote :

I don’t now if this can help

1) On a Xubuntu 12,04 the samba shares became inaccessible after update to Xubuntu 14.04 (Access denied for Windows an Samba clients). About one year latter they became accessible again. Probably due to a samba upgrade.

2) The shares became inaccessible again after upgrade to Xubuntu 16,04. I tried all combinations of client use spnego = no, client NTLMv2 auth = no, allow nt4 crypto = yes, require strong key = no without success. I removed the machine from the domain (Using Windows NT4 server manager).
The machine can’t join the NT4 domain :
No realm has been specified! Do you really want to join an Active Directory server?
Failed to join domain: failed to lookup DC info for domain xxxxxx over rpc: Access denied

(The smb.conf is for a NT4 domain, not for Active Directory. I tried all the cripto settings again.)

3) New machines with Xubuntu 16.04 and Ubuntu server 16.04.2 have never been able to join the domain : same message.

Primary an backup domain controller are Winndows NT4,0 Service pack 6.

As temporary solution, I moved the shares to Windows running in VirtualBox with bridged network access.

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

@andre-bacao, what is running on this domain controller that you can't join?

@hh68300 sorry, but I don't have access to NT4 to test your scenario. Maybe you can get some help in the samba mailing list at https://lists.samba.org/mailman/listinfo/samba ?

Changed in samba (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for samba (Ubuntu) because there has been no activity for 60 days.]

Changed in samba (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Kristian Du (kristian.hitech) wrote :

The fix proposed in comment #6 works. Shouldn't this bug be closed now?

Revision history for this message
Hubert Higelin (hh68300) wrote :

For the moment, it is still impossible to join an NT4 domain. (PDC and BDC are Windows NT4.0 Service Pack 6.) This since Ubuntu 16.04 (before there was no problem).
My last attempt: 31/10/2017 with a Ubuntu server 16.04.3

Revision history for this message
Stefan Metzmacher (metze) wrote :

I tested against NT4SP6a with this options:

       workgroup = NT4DOM193
       security = domain
       require strong key = no
       client use spnego = no
       client ipc signing = auto

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Thanks for your config, @metze.

@hh68300, could you please try with the config options from @metze's comment #13?

Revision history for this message
Hubert Higelin (hh68300) wrote :

I tried with the parameters indicated by @metze in # 13. I made a second attempt by adding allow nt4 crypto = Yes. Both attempts failed. Attached is the copy of the testparm and net rpc join outputs of the first attempt. The outputs for the second attempt are similar.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.