Page actions Read View source History. Category : NT4 Domains. Wiki tools Wiki tools Special pages. Page tools Page tools. Userpage tools. Categories Categories NT4 Domains. This page was last edited on 24 January , at This page has been accessed , times.
Content is available under CC-BY unless otherwise noted. Privacy policy About SambaWiki Disclaimers. If you are running Samba Active Directory AD , do not set any of the modifications mentioned on this page. It has been reported that rolling back to an earlier version of Windows 10 does allow the join to occur. You should plan to upgrade to AD as soon as possible.
Same error trying to connect though. I've been looking through as many log files as I can, but can't find any entry that is even remotely similar to the error message. Am I correct in assuming it's being generated by the Active Directory Connector app?
I have been concerned about DNS recursion because sometimes my load averages go have been going haywire. This will stop the Samba resolver resolving anything except domain FQDN's 2 - remove the first "--dns This will stop the container resolving back into itself. It may be OK but I don't see it is needed. The other line is needed to set the external resolver for the container, I think, otherwise it falls back to the default external resolver OpenDNS?
Unfortunately I need to cut back the time I've been putting back into this, especially as my next step is possibly a full re-installation.
Nick Howitt wrote: Cameron, I think I have found the issue. Tuesday, August 14 , AM - Permalink. Cameron, I think I have found the issue. Please can you post back with your findings and I'll update the HowTo. Depending on when you did your set up, you may or may not have picked up the corrected version. Monday, August 13 , PM - Permalink. I am in discussion with the dev's now as I hit the same or a similar issue.
In an LDAP system it should show something like from my production box : Please do not edit this file. Please let me know if you're in the same boat. You can fix it by changing the nameserver to Docker is up and running, however I'm having trouble connecting the Active Directory Connector to it. Any suggestions? Saturday, August 11 , PM - Permalink. Dave Loper is working on a migration path for existing installations.
Wherever you see Note the name of the name if the interface it creates. Change the ClearOS Samba port bindings to bind so it does not bind to the virtual interface. If you do an "ifconfig" you'll see a full list from which to make your choice. Do not add the virtual interface. If they are already disabled, enable them and disable them again. Both lines are needed, including the one in red the forum has split the lines into two sections and made the second line red - there is nothing I can do about it Add a guest user or Samba won't start useradd -r guest Then start smb, nmb and winbind.
Restart dnsmasq with a: systemctl restart dnsmasq. The package has better firewall treatment. It may be worth at this point doing an "ifconfig" and checking it has chosen a subnet which does not clash with any of yours. It does not seem to spot VLAN subnets in use and can have other issues mine, obscurely, is a VM running with natted interfaces on my desktop which has a local IP in the Note that the IP address you use should be the IP address you want to give the docker0 interface, so If you use Best practice says to use a subdomain of your proper external domain which does not resolve externally.
As an example, my proper domain is howitts. Change all occurrences of howitts. I have set password complexity off but the start script only changes the settings after the administrator password is set so you must use a complex administrator password. You can also change the administrator password to something else non-complex later on. I am not sure what the restrictions are for complexity but I had to have at least one upper case character, one lower case character and a number. The container itself can still resolve externally because of the "--dns" lines.
You should see some output where you can match a lot of it to the start up command. You now need to add some rules to the firewall. There is a troubleshooter here.
To use samba-tool you have to get to a command line within docker. You can change it here with: samba-tool user setpassword administrator and so on. RSAT may be the better tool to add users and add them to groups but that is down to you. Wednesday, August 08 , AM - Permalink. The client is visible, but can't be accessed most of the time Update: it works if you are logged in on other clients with the same username e.
It just doesn't seem to work - and it used to be just few clicks? Tuesday, August 07 , PM - Permalink. Hi Anyone tried to share a printer on domain members running W10 domain joined then upgraded to ? I have one Zebra label printer connected to a client via USB and then shared to others. I tried many things but couldn't get it to work reliably I have "Function Discovery Provider Host" and "Function Discovery Resource Publication" services enabled and set to Automatic Delayed Start , but that for some reason doesn't solve the issue completely Saturday, August 04 , PM - Permalink.
The current ClearOS implementations of Samba and dnsmasq need to be changed to bind on specific interfaces or interface IP's. Details are in the doc and in issue trackers and I've used the instructions in the container link to get the image starting up, but I've used different file locations. Dnsmasq can handle the rest of the queries. Dave is looking at how to implement this as a migration out of the current LDAP directory controller. Friday, August 03 , PM - Permalink. They can only be used if you have a licence.
I'd suggest you get yourself a copy of and , but remember in you will have to enable SMB1. There will be a bit less updating to do compared to the 15xx build. Friday, August 03 , AM - Permalink. Hi Just started tracking this We tried to join W10 to our domain and got an error Still have 15xx build. One day this possibly won't work anymore meaning after upgrading domain logons won't be possible How would any possible solutions work for paid 7.
Thursday, August 02 , PM - Permalink. While I was working on other things inside the samba migration path, Nick was working on how to get the addressing compatible between ClearOS and the docker image. He hit a brick wall after exhausting some methods and even exhausting and proving that some of the items I thought might work were untenable.
In the end, this left a limited set of options and I tried the stupid and simple one, which failed initially but then found that it would work with a restart of the docker daemon itself.
So with that daemon defeated, we are ready to put it together. The big thing that is left is the Samba Directory to Samba Directory artifacts migration. I've got a busy day today but will hit try and put some end to end testing together tonight and see if we can't come up with a comprehensive howto by the end of the weekend. Monday, July 30 , PM - Permalink.
That would require a highly customized docker. I'll look into whether or not this is possible to do the inline restore with existing docker images but I kind of doubt it.
But the fact that OpenLDAP is required for the migration is a big 'showstopper' for an elegant transition since you wouldn't want it at ALL running in your ideal endpoint. That being said, there is no need to torture everyone by making them jump through this hoop solo. The ideal thing to do here is to: a provide the VM via FTP to everyone to use with simple instructions. But the correct answer here is likely Let them decide. I failed to import any group memberships even though it imported all the group names.
The failure was with the 'flexshare' group name and I believe it fails because it is the same name as the flexshare users which is strictly prohibited. When I refine the steps, I'll contend with this and see if I get different results. Secondly, my workstation previously joined to the old domain can log in using cached credentials but cannot complete the login with another user 'no logon servers'. It can also use the RSAT tools to see the domain but since group membership import was broken, is not able to manipulate things.
The samba-tool, for example, doesn't exist properly which prompted me to go the Fedora route. Monday, July 30 , AM - Permalink. Hi Dave, As an alternative to the VM route, would it be possible to do an in-place migration of Samba to Samba Directory, back up the migrated Samba set up and restore it into docker then do a config restore of the original Samba?
Higher risk in case your last restore fails. One of the difficult barriers is the total lack of upstream mechanisms. There are various reasons for this but the short answer is that there isn't good support upstream for Samba Directory which solves the issue totally. Redhat has their reasons for this but it may be until RHEL 8 that there is domain controller support upstream. So that represents several development tracks that we have worked on and attempted.
In the end, it isn't elegant. My next attempts will focus on getting an existing directory to a docker container. The idea is this, since Samba Directory cannot be made to work well because of upstream, we will containerize the Samba Directory and then use the very stable AD Connector method.
This means that that there are two development tracks This install looks like this. Install the AD Connector module and connect it to the docker image. We want to end up in the same state as the 'NEW install' paradigm.
To get there we have a full list of problems - Exploring the migration of the domain off of ClearOS and then onto a Fedora VM with working Samba Directory - From there either 1 create a way to backup the Samba Directory domain for use by the docker, or 2 join the docker image domain to the migrated domain then decommission the Fedora VM.
If anyone wants to assist here. I will be focusing on the Samba elements so if you know docker and can point me to making the dperson image work on an alias LAN IP address in ClearOS, that would be very useful to me. Thursday, June 28 , AM - Permalink. Mansoor wrote: I'm trying to access clearOS shares from Windows 10 but without success!
The SMBv1 is enabled in Windows The clearOS server is 7. The server appears in the Windows file manager and in "nbtstat -A When I double click on the server's icon, Windows asks for username and password. All usernames and passwords I enter are rejected! I tried to login with "winadmin" and with normal users, but always the same result. I use the same account name on the PC as in the server, but the PC has no password whereas the server has a strong one.
Map Network Drive, connecting with different credentials was not reliable. I also found that the drives would map on boot but stay in a disconnected state until you clicked on them. This was fine in a GUI environment but I used a batch file to do backups and if it tried to access the network drive it would not force a reconnect and the batch file failed. Trawling the internet I found a program which will automatically connect the drives using stored credentials which I run on boot.
At the end of the day the recommendation is to use the same credentials in the PC as in ClearOS, but I've never got round to testing it as the family works without logins to the PC's.
Wednesday, June 27 , PM - Permalink. I'm trying to access clearOS shares from Windows 10 but without success! Wednesday, June 20 , PM - Permalink. Thursday, June 07 , AM - Permalink. One of my team got the following response from Support at Clearcenter today There are a couple of reasons for that; one of them being security isolation and the other is being able to partition the directory in a way that is more scalable.
We will have further guidance by Monday, June
