Windows 10 join nethserver

Support
16

then all your traffic is directed wrong.
You must configure IP fire so it will handle the ns records. for nethserver.

Your setup is not common and you must make sure that the DNS queryes are directed from the lan to the NS and then to your IPFire box.

Maybe you have other settings on the rest of the clients.

Declare the domain in IPfire, put a host record in DNS for NS server for the LAN so the query will be directed to NS.

Maybe this will work.

It’s really hard to try to guess what you have there (as settings and infrastructure) since you give little information about it.

EDIT: You could try to add a manual entry to the host file in WIN10 for the Nethserver and then reboot and see if you can join the domain

BR
Bogdan

17

i assure the aswer is no. the rest of the clients has the same configuration and work properly

the dns and gateway can be different

i tried but don’t work

i found this. it talk about a registry patch for windows 10 but i haven’t. i think this is the problem.

18

Sme is always the keys of your issues :smile:

I confirm that the registry patch is different between w7/8 and w10

1 Like
19

where is the difference? :smile:

2 Likes
20

don’t ask so, you don’t really want to know :wink:

21

i followed the bug via bugzilla mail and i was sure that at the end the registry key was the same… just rechecked and obviously i remember wrongly … i must definitely stop reading mailing lists when i am almost sleeping or when i’ve just woken up :grin:
i’ll re-read it after a :coffee:

22

I did the patch so i can retrieve informations… But for now i’m at work.

23

Gecco.
Have you tried this registry modifications in the Win10 client ?

HKLM->System->CCS->LanmanWorkstation->Parameters
DNSNameResolutionRequired = 0
DomainCompatibilityMode = 1

And what is the actual error code the win machine shows.

BR
Bogdan

24

ahah this gif is really funny I steal it

25 
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters]
"DNSNameResolutionRequired"=dword:00000000
"DomainCompatibilityMode"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths]
"\\\\*\\netlogon"="RequireMutualAuthentication=0,RequireIntegrity=0,RequirePrivacy=0"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ProfSvc\Parameters]
"UseProfilePathExtensionVersion"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System]
"SlowLinkDetectEnabled"=dword:00000000
"DeleteRoamingCache"=dword:00000001
"WaitForNetwork"=dword:00000000
"CompatibleRUPSecurity"=dword:00000001
26

I used my domain in widows 10 and worked well try my reg

Windows Registry Editor Version 5.00

; Win7_Samba3DomainMember
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters]
“DNSNameResolutionRequired”=dword:00000000
"DomainCompatibilityMode"=dword:00000001

; Speedup settings
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System]
“SlowLinkDetectEnabled”=dword:00000000
"DeleteRoamingCache"=dword:00000001
"WaitForNetwork"=dword:00000000
"CompatibleRUPSecurity"=dword:00000001

; Can drive you nuts
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
“EnableLUA”=dword:00000000

2 Likes
27

sure.

28

don’t work

29

maybe it has to do with the settings of windows(Network or domain settings etc)… Try to see if you re-install windows and try to join the domain.

30

i found the solution but is not a real victory

i installed windows 7, applied win7samba.reg, then update to windows 10.
now window 10 can connect to the domain… i’m happy but i’m not really happy…

1 Like
31

windows… how do you want to get crazy today?

1 Like
32

Which reg you applied ?

33

i tried all .reg

34

I’ve just connected a windows 10 pro to the domain with no issues.

What user are you using to add the machine to the domain? did you set the
dns to the nethserver?

35

again… the dns is right

i connect with admin user