BUMP!

I cannot get freshly built windows 10 to join either.

I always get some DNS error yet clearos is the DNS server.

Do I need to add a DNS entry with my registrar?

Has anyone successfully joined fresh windows 10 to COS?

Nick Howitt wrote:

Get rid of the line or set it to "139 445" which is the default if it is not set. Then reload samba or stop and start it from the webconfig. I saw it in this post about the Badlock bug and I think I've seen it elsewhere.

Excellent, I will be trying this a.s.a.p. and will post some feedback on the results.

I guess that it may be the same process for Windows 7 or 8 or 8.1. Will be upgrading to Windows 10 this weekend and need to test it myself sometime.

I recommend testing it on a test machine before doing it on production machines.

Hi,

any news on that topic?

Best regards
Christoph

i want to know the same thing my windows 10 will not join the domain at all what do i do

Hi

I have upgraded a number of PCs from Windows 7 to Windows 10 and the domain joining worked without any changes.

The windows 7 PCs were domain members before the upgrade

I have upgraded several clients (that were already domain members) without problem.
I'm now however in the process of re-joining a Win10 client and it gives me problems. It claims it can't find the DC. The registery fix doesn't seem to help.
It seems pretty safe to say it doesn't work as predictably as I'd like, maybe due to the Samba version and/or dropped support on Windows 10's end.

Chris Musty wrote:

BUMP!

I cannot get freshly built windows 10 to join either.

I always get some DNS error yet clearos is the DNS server.

Do I need to add a DNS entry with my registrar?

Has anyone successfully joined fresh windows 10 to COS?

So far I have not been able to join an Windows 10 computer to our domain.
Computers that were in the domain before the migration to Windows 10 (from Windows 7) do not seem to have a problem so long as they remain domain members. Once taken out they cannot rejoin. I'm also still eagerly in the search for a workable solution, perferably sometime before the end of July.
(after that date the free upgrade program stops and upgrades have to be paid for so the upgrade loses priority untill Windows 7 reaches the end of it's support cycle...)

BTW the version is Community 7.

I am amazed more people are not complaining about this, unless they all have it working, in which case can anyone who has successfully set up COS for windows 10 please explain what they did?

I don't use domains so can't help directly, but can you check your /etc/samba/smb.conf that it either does not contain the "smb ports" line or that it is set to "139 445" and not "139" only?

There is a troubleshooting guide somewhere on this site written by one of the devs but I can't find it.

We have a domain on a 6.7 box and the smb ports variable is set to 139. Would I try setting it to 139 and 445 or...?
This troubleshooting guide you speak of would be excellent. I feel i've checked all the relevant variables but it'd be nice to have either some confirmation that I did check all the variables or if not have something new to try.
I've spent more time on this issue then I care to mention, it'd be nice to get somewhere with this.

Get rid of the line or set it to "139 445" which is the default if it is not set. Then reload samba or stop and start it from the webconfig. I saw it in this post about the Badlock bug and I think I've seen it elsewhere.

OK so I managed to get it... still ironing out some bugs but I got it.

Firstly there is the well know registry hack - got to:

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters]



and add these dwords



"DomainCompatibilityMode"=dword:00000001

"DNSNameResolutionRequired"=dword:00000000

next go to you samba configuration file and add this line

server max protocol = NT1

for some unknown reason when I logged into my domain account my personal network folder was not available. I had to change ownership.

setfacl -Rm u:usersname:rwx /home/usersname



chown usersname /home/usersname

on your pc go to system > change > add your domain name (I am not elaborating here because I feel its a well known step)

I had to change the workgroup to something other than work group (I think COS was originally workgroup)

Reboot

Now go back to system and change from workgroup to domain and hit ok.

If you get the DNS error here then you are probably using the wrong domain

In the COS dashboard go to server > File > Samba > under Windows Domain add the name you want - and use this for the domain in windows

Initial login must be done with a user not winadmin (I dont know why) winadmin works after a user logs in

Happy to elaborate, I wrote this quickly so no doubt its full of errors but hope it helps someone!

I am disappointed if you need to use "server max protocol = NT1" unless that is different from "max protocol". I thought one benefit of samba > 3.6 was that you could use "max protocol = SMB2". It is what I use in simple file sharing mode, so no domains.