similar to: Anybody got windows 10 working with our classic DC / need to migrate to samba4?

On Tue, Jun 2, 2015 at 1:24 PM, Marc Muehlfeld <mmuehlfeld at samba.org> wrote: > Hello Andrew, > > Am 02.06.2015 um 09:55 schrieb Andrew Bartlett: >> Just checking if anybody has Samba's classic DC functioning with Windows >> 10 domain member clients? In particular, I'm interested in any tests >> with git master or 4.2. >> >> I'm not

On Thu, Jun 4, 2015 at 5:23 AM, Marc Muehlfeld <mmuehlfeld at samba.org> wrote: > Hello Scott, > > Am 04.06.2015 um 08:47 schrieb Scott Lovenberg: >> Marc, I'm assuming your test was a clean Samba install with stock >> configurations and a clean Windows-10 9926 (with no previous contact >> to either AD or NT4 domains)? > > Yes. It was a new installed

Hello Andrew, Am 02.06.2015 um 09:55 schrieb Andrew Bartlett: > Just checking if anybody has Samba's classic DC functioning with Windows > 10 domain member clients? In particular, I'm interested in any tests > with git master or 4.2. > > I'm not talking about samba4 DCs (our AD DC), but with the NT4-like > mode. > > The reason I ask is that I've got

Hello Scott, Am 04.06.2015 um 08:47 schrieb Scott Lovenberg: > Marc, I'm assuming your test was a clean Samba install with stock > configurations and a clean Windows-10 9926 (with no previous contact > to either AD or NT4 domains)? Yes. It was a new installed Windows 10 TP build 9926, with no contact to any AD or NT4 domain before. Also the Samba 4.2.1 PDC was a fresh installation

Hello John, Am 09.07.2015 um 17:08 schrieb John Drescher: > Hmm. On 2 test boxes I am now getting no login servers available on > 10162 (while it worked for previous builds and I do not experience > that on my windows 7 or 8.x machines). 10130 crashed just after the > login was accepted if the network cables were connected ( I have 2 > networks at work gigabit private to samba

Hello, I have try windows 10 in an Samba 4.4.5 NT4-style domain. With some registry hacks (DomainCompatibilityMode and DNSNameResolutionRequired) it can be an member of the domain. When i try to login with domain member i get the error "There are currently no logon servers available to service the logon request" At

When I enable server signing in Samba (server signing = mandatory), I can still join a Window 7 machine to the domain but I am no longer able to log on into the domain using a domain user. Is this normal? I am using Samba 3.6.3 on Linux 12.04. Is there anything that needs to be configured on the Windows machine? Thanks, Ali

After researching win7 and samba issues we upgraded to 3.5.22. We still can not connect to shares on the RHEL 5.9 box. Odd thing is, when attempting to connect we never see anything in the logs, which makes me think its a networking issue. We've turned off the firewall on the win 7 box, but still nothing. We can ping the RHEL server from the Win 7 box. Any insights or suggestions would

Hello We have a problem with our Windows 10 Clients. Installed on a SLES12 Server is samba v4.4 I can bind the clients to the domain without any problem. Afterwards I want to login in the domain, I get the error, no logonserver available I can change in the smb conf max protocol to NT1 -> now it is possible to login with user xxx in the domain We don't want to use our samba server

On 18/01/15 10:01, Dr. Harry Knitter wrote: > Rowland Penny <rowlandpenny at googlemail.com> schrieb am 18.01.2015: >> Please don't send PM's, it breaks the thread, how was anybody other than >> Jeremy to know you sent it ?? > This happened, becaus I got Jeremies mail by PM, too and did not take care to > send my answer to the list, too. Sorry again > @ all

Hi, I am using a samba server for file sharing in our companies IPv4 based LAN. The samba server is running as VM on a ubuntu 14.04 qemu/kvm host using ubuntu 14.04 as OS. I am using the lastet version available for samba: 4.1.6+dfsg-1ubuntu2.14.04.3 My Windows 7 and Windows 8.1 client are able to find the server and connect to the shares but the Windows 8.1 client of a colleague is not able to

Hi ... After having a tough fight the last days with migrating from samba 3.6 to 4.2.2 in one network segment (see my previous posts) I am facing my next problem: Domain logons with windows 10 pro. I got windows 10 pro build 10159 running in a vm. I added the 2 well known registry changes I always add to windows 7 also to windows 10. So far so good. I joined the machine to my samba 4.2.2

Good Morning Marc, Marc Muehlfeld <mmuehlfeld at samba.org> wrote on 09.07.2015 17:49:36: > Am 09.07.2015 um 14:35 schrieb Roland Schwingel: > > I got windows 10 pro build 10159 running in a vm. I added the 2 well > > known registry changes I always add to windows 7 also to windows 10. So > > far so good. I joined the machine to my samba 4.2.2 PDC. Heureka! It >

The issue does not seem to be connected to SMB1. It can be installed and it still won't authenticate. Something has been changed to force authentication to AD/DNS either solely or as a first step. The translation of the netbios name never happens even if the computer can resolve the name. Given that the authentication thru netbios resolution seems to get grandfathered in provided the domain

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

I've been running Samba 4 in NT4 Domain mode for a few years, and it's been working fine with Windows 7 PCs. I now need to join a new Windows 10 PC to the domain, but I'm not having any success! When I try to join the domain, the Windows 10 PC says "An Active Directory Domain Controller could not be contacted...." I've tried a few things, including:- Setting

Given an existing NT4 Samba 4 DC, a recently upgraded Win10 machine can no longer access NETLOGON to authenticate to the network. This lead to the research revealing that my Samba4 PDC SMB.CONF must be changed to limit MAX PROTOCOL = NT1 to avoid negotiating a version of SMB2 from Win10 that Samba4 can't resolve. Doing this broke authentication via other resources that no longer support NT1,

If this is an NT4-style domain, then DNS is not essential. Things like SRV records aren't relevant since a lot of the NT4 is back from the NetBios days. It looks like your Win 10 machine thinks it is trying to join an AD domain. Windows clients machines typically are using DNS to resolve server names to IP addresses. However DNS does not provide info on locating PDC's

I've used Samba to share files on my home LAN, consisting of Linux and Windows systems. So far, I've never enabled Homegroups on the Windows systems. I'm now asked to set up a larger LAN in a school computer laboratory, consisting of 30+ Windows 7 machines, several printers and scanners, and two Linux workstations. I expect that homegroups would be the easiest way to set up the

Hi, I got the same problem with Build 10162. I dont think it's an Samba issue. It seems that Windows 10 dont like "\\....\netlogon". Our Samba 3.5.6 PDC works like a charm for win 7. From my Win10 PC i can access everything except \\dc1\netlogon Symptoms: Accessing \\dc1\netlogon -> Auth fail Accessing \\dc1\netlogon2 -> Works (same config!!!) Accessing \\dc1\s1\netlogon