Forums

Resolved
0 votes
Dear experts,
I'm configuring a small network of 4 Win 10 clients and a COS 7.3 server. I've installed the Directory server which is initialized. After that Windows networking. Also configured.
Now I am wondering if this even should work out of the box. I've placed the logon.cmd in the /var/samba/netlogon folder using winscp since winadmin didn't seem to have access to that folder. Which might point to the initial issue. But it is a clean install and just changing settings till it works doesn't seem like the right approach.

If I try to add a client I get the add username and password question just fine. So the server is found and the name is correct (if I try to add to a fake domainname I get an direct error the domain can't be found).
After entering the winadmin credentials I get the error.
"There are currently no logon servers available to service the logon request"

I've searched google and this forum and these kinds of issues seems abundant but all under win 7 as far as I could find.
I've attached screenshots if the samba and ldap settings. Did I make some rookie mistake? or is something else playing up? Please advise,
Cheers, Foeke
Saturday, August 26 2017, 10:49 AM
Share this post:
Responses (3)
  • Accepted Answer

    Monday, August 28 2017, 10:11 AM - #Permalink
    Resolved
    0 votes
    Hi Dave thanks for your reply!,
    I did set the file to the domainusers. But shouldn't I at least be able to open the folder? By going straight to \\192.168.10.1\netlogon ? I do get the request for the winadmin credentials but after that it loops back to the credentials question again (i've also set it to an very simple password to be sure).
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, August 26 2017, 04:18 PM - #Permalink
    Resolved
    0 votes
    If you copy a file to netlogon using WinSCP to /var/samba/netlogon using root then it will set the permissions to root:root. Using WinSCP, you can change the permission so that others can read/execute it. 755 should do it. You can also change the owner and group to something like winadmin:domain_users. The netlogon folder is hidden but winadmin should still be able to get to it by simply specifying it:

    net use z: \\192.168.10.1\netlogon

    As for the flexshare, make sure that it is executable to the group that owns the folder. All objects in the folder and the subfolders should be owned by the group that you've specified in the flexshare. If this isn't the case you can repair it with:

    chgrp -R groupname /var/flexshare/shares/sharename

    As always, user folders are exclusive and not meant to be shared under the Group-based permission model in ClearOS which is done for various compliance directives.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, August 26 2017, 01:54 PM - #Permalink
    Resolved
    0 votes
    I've found an other thing that might be related. In a flexshare going to \\fileserver\kantoor I couldn't run an executable (no permission) that was placed there from another account. But it does run from \\192.168.10.1\kantoor .
    The reply is currently minimized Show
Your Reply