Forums

Subscribe via email Subscribe via email
Subscribe via rss
Guest
or Ask a Question
Add a reply View Replies (5) →
Pudl
Pudl
Offline

No logon server is available

Resolved
0 votes
Hi guys and girls.

My configuration:
- ClearOS 6.8 (as DNS, NTP, user/groups, Windows DC),
- Synology NAS,
- around 40 Windows 10 computers.

For a second week now I am dealing with a huge problems regarding domain. Last week I updated our NAS to latest version. Because of badlock fix it dropped from the domain. I was able to re-join after couple of days with help from Synology technical support. I had to change smb.conf on ClearOS! with adding this line: server signing = auto.
But created havoc on my WIN computers. I cannot log in with users which were not previously already logged on that computer, cannot access any computer shares (eg \\<computer name>;). To me it looks like WIN computers are running in cached domain mode.
Can you please help me what to do in this case?
My current smb.conf file.

Br, Ales.
In Windows Networking
Monday, March 13 2017, 01:17 PM
Subscribe via email
Share this post:
Responses (5)

  • Accepted Answer

    Pudl
    Pudl
    Offline
    Thursday, March 23 2017, 11:20 AM - #Permalink
    Resolved
    0 votes
    Hi.
    I am still experiencing problems with shares on Windows and ClearOS as PDC. They become unreachable few times a week. Restarting smb service on ClearOS solves the problem until next event.

    Is it time to change PDC for COS 7.3 SAMBA Directory?

    Br, Ales.
    The reply is currently minimized Show

  • Accepted Answer

    Pudl
    Pudl
    Offline
    Tuesday, March 14 2017, 06:07 AM - #Permalink
    Resolved
    0 votes
    I think I found it!
    I added this lines to the smb.conf on ClearOS:
    client signing = auto
    client ipc signing = auto

    First tests shows that mapped drive is reachable again when yesterday was not.
    Super happy about that!

    But there are still problems with the domain. I am still not able to open \\share on other computers, still getting "No logon servers" message. So looks like this change had only influence on NAS share (which is running Linux) or CIFS protocol.
    Can someone help me about that?

    Br, Ales.
    The reply is currently minimized Show

  • Accepted Answer

    Pudl
    Pudl
    Offline
    Tuesday, March 14 2017, 04:13 AM - #Permalink
    Resolved
    0 votes
    Yesterday, the problem grew worse. A few computers are not able to reach NAS mapped drive anymore. It is 5 in the morning and I am trying to find alternative solution for mapped drive because we cannot work without it.
    The reply is currently minimized Show

  • Accepted Answer

    Pudl
    Pudl
    Offline
    Monday, March 13 2017, 03:12 PM - #Permalink
    Resolved
    0 votes
    Here you go.
    Thank you.

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters]
    "DisablePasswordChange"=dword:00000000
    "MaximumPasswordAge"=dword:0000001e
    "RequireSignOrSeal"=dword:00000001
    "RequireStrongKey"=dword:00000001
    "SealSecureChannel"=dword:00000001
    "ServiceDll"=%SystemRoot%\system32\netlogon.dll
    "SignSecureChannel"=dword:00000001
    "Update"="no"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]
    "EnablePlainTextPassword"=dword:00000000
    "EnableSecuritySignature"=dword:00000001
    "RequireSecuritySignature"=dword:00000000
    "ServiceDll"=%SystemRoot%\System32\wkssvc.dll
    "ServiceDllUnloadOnStop"=dword:00000001
    "DomainCompatibilityMode"=dword:00000001
    "DNSNameResolutionRequired"=dword:00000000
    The reply is currently minimized Show

  • Accepted Answer

    Dave Loper
    Dave Loper
    Offline
    Monday, March 13 2017, 02:25 PM - #Permalink
    Resolved
    0 votes
    Can you post for me the values you are using in:

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters

    -and-

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters
    The reply is currently minimized Show
Your Reply