I'm testing Windows 10, and I personnaly think it has more chance to be installed in my LAN than Windows 8/8.1 ;)
Unfortunaltely, I can not join W10 to my domain. I use Samba 3.6.6 as a PDC.
When I click on "Join an organization", I set my domain name. Then login and password are required. After typing them, I can see Windows 10 "searching". After about 10 seconds, I have the following message :
"That domain couldn't be found. Check domain name and try again"
Which is weird, as it seems to have found the domain, because login and passwords are required (I have tried with a fake domain name ; login/password are not required and I got that message immediately).
Any other OS can join my domain (XP, Vista, 7, 8).
I do not have internal LDAP nor DNS server ; I use WINS.
Has anybody tested W10 with Samba 3.6 yet ?
Thanks for your help and feedback
maybe that sounds like MS has given up supporting plain old Domaincontroller..
Since Server 2003 DNS is the mehtod to query anything AD needs in a Directory. Server 2000 was the last
Version, i played around with, which came without DNS. For the whole join, you need a the zone _msdcs.<domain>.<com>
_ldap._tcp._dc._msdcs.domain.com should point with a SRV entry to the dc (fqdn) and a A for the hostname/IP
and the forwarder inside your domain.. but i dont think itll work :)
good luck.. PDC was before my time.. :)
"plain old Domaincontroller" --> do you mean NT domain controler (without AD or LDAP) ?
If yes, that would need a confirmation : is Windows 10 compliant with NT domain controler ?
Actually, I tested W10 with a Samba4 AD DC, and it works ...
I recently identified an issue with SMB1 over NetBIOS on Windows 10 that is slated to be fixed with the next milestone of Windows 10. Due to the fact you are using Samba3, I am think you might be encountering a similar type of issue where the Windows 10 client may be having troubles communicating over TCP port 139.
Can you use network monitor to capture a trace when reproducing the issue on Windows 10 and then send the trace to me at arudell at microsoft dot com? I can then review the trace and at least confirm if this is indeed the scenario you are encountering or if there is something else.
Have you found a solution for your issue yet? Please keep us posted!
Sorry for not replying to you since your post. I didn't have time to check my messages on technet...
Regarding your advises - use network monitor to capture a trace when reproducing the issue on Windows 10 and then send the trace - can you exactly tell me which part to capture ? Because the network monitor is quite huge. When reproducing the problem, I took a look to the "Listening Port" panel and didn't see anything about TCP port 139.
By the way, is there a new build of Windows 10 ? I'm still using 9841.
Unfortunately, no. Because of that, I'm studying the possibility to migrate to Samba 4, with AD DC.
But still, I'd like to know why Win10 can not join Samba 3 :)
Just ran into this issue myself. I hate to have to give up the flexibility of OpenLDAP just so we can join win10 systems to the domain. Hopefully this is a feature or setting that will be dealt with later.
I did set up a Samba4 box in AD mode, but the ldap tools were, well, sub-par compared to openldap, though better than what's in windows.
If you're using samba3+LDAP I have a migration script you may want to use as a starting point.
Can you share the migration script am in the same situation.