Forums

Subscribe via email Subscribe via email
Subscribe via rss
Guest
or Ask a Question
Add a reply View Replies (4) →
Tux Brothers GFORCE1
Tux Brothers GFORCE1
Offline

After upgrading to 7.4 cant join samba domain anymore

Resolved
0 votes
I was stupid to let the auto updates ON ....
But here is the thing , after upgrading to 7.4 (Samba 4.4.6) i cant join windows 10 workstations anymore, win 7 & 8 its working fine.
Its complaining it cant fnd the domain anymore
On windows:
(foutcode 0x0000232B RCODE_NAME_ERROR)

De query was voor de SRV-record van _ldap._tcp.dc._msdcs.GFORCE1

Before upgrading (7.3) it was working perfectly!
In ClearOS Development and Test Releases
Thursday, October 26 2017, 03:22 PM
Subscribe via email
Share this post:
Responses (4)

  • Accepted Answer

    Tux Brothers GFORCE1
    Tux Brothers GFORCE1
    Offline
    Saturday, October 28 2017, 02:05 PM - #Permalink
    Resolved
    0 votes
    Guys thanks helping out!
    But it was a Win problem (solved)

    Thanks in advance for helping!
    The reply is currently minimized Show

  • Accepted Answer

    Nick Howitt
    Nick Howitt
    Offline
    Friday, October 27 2017, 09:09 AM - #Permalink
    Resolved
    0 votes
    There was an update to app-samba (app-samba-3.4.5-1) in the last few days which inserted:
    ntlm auth = yes
    into the top of the global section of /etc/samba/smb,conf. Samba actually disabled all NTLM when it went to v4.5. This update took samba from 4.4 to 4.6.

    Unfortunately I doubt if this is the issue as Win 7/8 work.
    The reply is currently minimized Show

  • Accepted Answer

    Tux Brothers GFORCE1
    Tux Brothers GFORCE1
    Offline
    Friday, October 27 2017, 08:04 AM - #Permalink
    Resolved
    0 votes
    Thanks for answer Mandoor! But it didnt help.

    I also get this messages in samba log:
    [2017/10/27 00:20:35.371610, 1] ../source3/smbd/process.c:554(receive_smb_talloc)
    receive_smb_raw_talloc failed for client ipv4:192.168.22.175:50851 read error = NT_STATUS_HOST_UNREACHABLE.
    [2017/10/27 07:51:36.858487, 1] ../source3/smbd/process.c:554(receive_smb_talloc)
    receive_smb_raw_talloc failed for client ipv4:192.168.22.175:49728 read error = NT_STATUS_CONNECTION_RESET.
    [2017/10/27 09:18:40.363476, 1] ../source3/smbd/process.c:554(receive_smb_talloc)
    receive_smb_raw_talloc failed for client ipv4:192.168.22.175:49733 read error = NT_STATUS_CONNECTION_RESET.
    [2017/10/27 09:36:58.347587, 1] ../source3/smbd/process.c:554(receive_smb_talloc)
    receive_smb_raw_talloc failed for client ipv4:192.168.22.175:49718 read error = NT_STATUS_IO_TIMEOUT.
    The reply is currently minimized Show

  • Accepted Answer

    Mansoor
    Mansoor
    Offline
    Thursday, October 26 2017, 09:41 PM - #Permalink
    Resolved
    0 votes
    Accourding to ClearOS 7.4 change log:
    Samba updates disable NTLMv1

    Maybe that Win10 client is trying to use NTLMv1. See here please to fix this: https://forums.freenas.org/index.php?threads/smb-problem-on-win-10-client-fn11-rc.54316/
    The reply is currently minimized Show
Your Reply