Artem, Win 7 client does not show the dialog box for NS admin credentials. instead, I have message saying it is impossible to contact the domain AD. So I don’t even have the opportunuty to enter NS admin credentials.
Re enable domain service and check firewall on NethServer
@petralemoisson have you changed NethServer admin account password?
To join a Windows 7 client to NethServer Samba domain you must:
- on the client set just one DNS server IP address > NethServer green (LAN) IP
- on the client import registry settings for Samba domain
- on NethServer change admin password to enable this account and allow Windows to join the domain
Did it, i think i found what is happening.
Did you set admins password?
I’ve just joined my machine but i was triying to do it with root and didn’t
work out, set admin password and worked like a charm using admin user.
I have tried with admin user instead of root, disable and renable with no luck.
One thing to add though is my network architecture is as follow
Modem ---->router 1(192.168.2.1) -----> to WAN NS server ( Lan NS 10.10.1.1) —>router2 (192.168.1.1) ---->windows 7 client wireless
Can this be the reason I can’t join NS domain ?
Dns? what happens if you go to windows run and put \home.lan
Is your server on the same lan?
did you tried to open a cmd window and ran nbtstat -a xx.xx.xx.xx where xx
is your domain server ip?
It should answer something like
Host not found.
ireless Network Connection:
ode IpAddress: [192.168.1.106] Scope Id: []
NetBIOS Remote Machine Name Table
Name Type StatusTest i’ve made were run on a virtualized virtual box machine over wifi to a
virtualized netserver over cable
it looks like its resolving it ok, and then when you try to add it to the
domain it tells you that it can’t reach de domain controller?
Yes that’s correct, when I try to add it to the domain it tells me it can’t reach the domain controller?
Are you sure you applied the correct .reg file and it was proccessed ok,
seems to me that that’s the problem.
I applied the .reg file highlighted below. using the process I explained in a previous post:
- copied the Client registry setting
- pasted it in a text file using “Boc Note”
- saved as win7samba.reg
- double click on the file
- when completed, rebooted the win 7 client
It was processed ok and the key was added in the registry.
Your windows client under wifi router! Shame on you! Disable NAT on wifi , or put all wifi like AP mode without NAT! Or make some port redirection rules!
1 Like
I am not sure but it could be that not every Windows version can be integrated in an Active Directory. Is your Windows a Home version?
@Nas Yes Sir ! that’s was the issue. I set the second router in bridge mode and that solve the problem. win 7 successfully join the NS domain.
Thank you all for your great support and thanks for the development team for generously offering this fabulous product. My migration from Zentyal just started 
That’s an amazing topic, 5 people who are trying to help @petralemoisson! That’s the community that I Want! Thanks guys… @mabeleira @Nas @zamboni @sitz @WillZen
@petralemoisson welcome aboard! I read about a migration… Could you please introduce yourself here?
2 Likes
As i asked earlier it might not work if the network subnets are different,
wins protocol normally is not routed, so if you have your dns server over a
regular router, you might try to setup dns entries for you domain on
windows\system32\drivers\etc\hosts and lmshosts, but its a little tricky