similar to: Windows 10 Domainlogon Samba 4.4.5 NT4-style domain

I had this issue as well; unfortunately, the fix that isn't recommended by the Samba team is to disable SMB 2/3 on Windows 10, which can break them from connecting to other systems (and that's why it's not recommended). Any reason you can't migrate soon to Samba4 AD? On Thu, Aug 18, 2016 at 11:28 AM, basti via samba <samba at lists.samba.org> wrote: > Hello, > > I

There are only a small network with 10 win7 and 1 win10 at the moment. I think the work of a migration is overkilled. At all this is only a test PC so an generic user profile is the simpler solution in my opinion. Thank you luke. On 19.08.2016 03:38, Luke Barone via samba wrote: > Any > reason you can't migrate soon to Samba4 AD?

Hello, at the Moment we use and Samba 4 in NT4-style Domain with approx. 20 Clients. With the Problem of Windows 10 to join to NT4-style (https://wiki.samba.org/index.php/Required_Settings_for_Samba_NT4_Domains#Windows_10:_There_Are_Currently_No_Logon_Servers_Available_to_Service_the_Logon_Request) we plan to migrate to Samba AD. At the Moment there is the following scheme: samba PDC

If I setup a samba 4 PDC (not AD) like I do with samba 3, I still have to change the follow registry key on Win 7/8/?/10 for join it to samba domain ? > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters] > "DomainCompatibilityMode"=dword:00000001 > "DNSNameResolutionRequired"=dword:00000000 > >

Hi, thanks a lot for the tips. I already did the first one, importing the following into the registry: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters] "DomainCompatibilityMode"=dword:00000001 "DNSNameResolutionRequired"=dword:00000000 I didn't do the second tip but it looks like it's not

I was trying to fix a problem on Windows 10 with Outlook 2013. Also running an NT4-style domain. The machine had already been joined to the domain and outlook had been working but recently not (probably after patch tuesday.) I also had had problems with Win 10 mail and RDP. I came across the following link.

You should be able to unbind ipv6 for the win 10 machine's network interface. does "nslookup SRV1" work? Also, you may want to try running tcpdump or ethereal or wireshark on our PDC and see what traffic is captres. On 05/20/16 13:24, Pau Peris wrote: > I'm completely lost as i can ping SRV1 without issues but i'm starting > to think that maybe Windows tries to

I prepared samba PDC and not able to join windows 10 clients. Please suggest any windows 10 registry settings.

Hi, I've got a problem with Windows 10 Education (last build) and my Samba PDC (under Fedora). All machines with Windows 7 can join domain successfully. But with Windows 10, I've got "network path not found" error. I've changed all registry keys that we need to change, but no way (DomainCompatibilityMode, DNSNameResolutionRequired, AllowInsecureGuestAuth) My PDC is in NT4

Hi, i've tried adding server max protocol = NT1 into /etc/samba/smb.conf and restarting smbd and nmbd services but it didn't do the trick. I feel like Windows clients are not able to resolve SRV1 into the PDC and so they can't event try to join the domain. On Fri, May 20, 2016 at 4:22 PM, Pau Peris <pau at webeloping.es> wrote: > Hi, > > thanks a lot for the tips. I

Excuse me for the little flood please, i've just checked it again and now i see SRV1 as master for exedra.cat workgroup, i event can see in the logs Samba name server SRV1 is now a local master browser for workgroup EXEDRA.CAT on subnet 192.168.69.203 So i'll keep digging on how to fix the issue exposed on my first email, tomorrow i'll try to see wether it's an IPV6 issue or

I'm completely lost as i can ping SRV1 without issues but i'm starting to think that maybe Windows tries to join the domain through IPV6. ping -c6 SRV1 from this Windows 10 machine leads to host not found so i'm working on this direction right now. Any help will be really appreciated On Fri, May 20, 2016 at 5:04 PM, Gaiseric Vandal <gaiseric.vandal at gmail.com> wrote: > I

Right now i'm out of the office and i have no way to remotely work with the Windows machines so i've been upgrading the server to Ubuntu 16.04. Everything seems to be working as before but i'm wondering why right now the Master value is blank for Workgroup exedra.cat Any idea? # smbclient -L localhost WARNING: The "syslog" option is deprecated Enter root's password:

On 07.10.15 20:07, Andrew Bartlett wrote: > On Fri, 2015-10-02 at 09:14 +0200, Dario Lesca wrote: >> If I setup a samba 4 PDC (not AD) like I do with samba 3, I still >> have >> to change the follow registry key on Win 7/8/?/10 for join it to >> samba >> domain ? >> >>> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorksta >>>

You have seen : https://wiki.samba.org/index.php/Required_settings_for_NT4-style_domains and you rebooted after the registry changes? And you have (optionaly) set max protocol = NT1 in smb.conf Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Nico > Verzonden: dinsdag 15 december 2015 13:50 > Aan: samba at

my named.conf look like dlz "foo" { # For BIND 9.10 database "dlopen /usr/lib/x86_64-linux-gnu/samba/bind9/dlz_bind9_10.so"; }; Am 07.02.2017 um 15:26 schrieb Rowland Penny via samba: > On Tue, 7 Feb 2017 15:04:30 +0100 > basti via samba <samba at lists.samba.org> wrote: > >> Windows-IP-Konfiguration >> >> >> >>

Hi, thanks a lot for your reply. Yes, i enabled wins through "wins support = yes", i also enabled lmhosts lookup and wins on all clients but will check it as you proposed. Tomorrow will try to disable ipv6 on Windows clients following this link https://support.microsoft.com/en-us/kb/929852 Which process did you follow to disable IPV6? I'm also wondering if it's really necessary

Hi all, some years ago i configured a `Primary Domain Controller` through Samba and LDAP (slapd) on an Ubuntu machine (13.10) at 192.168.69.203 which should be accessible by the string/name `SRV1`. I must note i did not installed winbind. I've never had any issue and it looks like it's working fine as about 10 Windows machines joined the PDC and Windows users can login against PDC on

There's nothing wrong with that path. If your DNS is working, you should be able to connect to \\foo, which is your AD domain. It will just pick one of your DCs instead of a static one. Alex On 06/02/17 14:36, basti via samba wrote: > > samba-tool gpo listall > showes also wrong path in gpo > > > On 06.02.2017 15:21, basti via samba wrote: >> When I do an gpupdate

Are you running a wins server (maybe you already mentioned this.) That tends to help minimize some classic samba issues. On my PDC root at mypdc:~# testparm -v | more Load smb config files from /etc/samba/smb.conf rlimit_max: increasing rlimit_max (256) to minimum Windows limit (16384) Processing section "[netlogon]" WARNING: The