search for: soonerdave

Dear all, Le 07.09.2015 à 15:52, soonerdave a écrit : > Windows 10 will try to negotiate SMB3_11, which Samba4 doesn't yet support > except in the current 4.3 release candidate. I suspect for now disabling > SMB2/3 on the Windows 10 client is your best, if not ideal, option. > > Instructions for doing.this can be found &gt...

Hi! I have a Samba server version 4.1.11 running on Ubuntu Server 14.04. I cannot connect from Windows 10 (but I can from Windows 7). The server and the clients are not on the same LAN. The error message given by Windows is that the server is online but not responding. However the Samba logs say otherwise. I have attached the logs for a failed connection attempt from Windows 10, and those for

Dear Rowland, Thanks a lot for your anwswer ! Le 2017-10-17 20:16, Rowland Penny via samba a écrit : > On Tue, 17 Oct 2017 19:31:17 +0200 > "Denis BUCHER via samba" <samba at lists.samba.org> wrote: >> Le 07.09.2015 à 15:52, soonerdave a écrit : >> > Windows 10 will try to negotiate SMB3_11, which Samba4 doesn't yet >> > support except in the current 4.3 release candidate. I suspect for >> > now disabling SMB2/3 on the Windows 10 client is your best, if not >> > ideal, option. >> >...

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,

On 31/08/15 18:12, soonerdave wrote: > 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...

On Tue, 17 Oct 2017 19:31:17 +0200 "\(lists\) Denis BUCHER via samba" <samba at lists.samba.org> wrote: > Dear all, > > Le 07.09.2015 à 15:52, soonerdave a écrit : > > Windows 10 will try to negotiate SMB3_11, which Samba4 doesn't yet > > support except in the current 4.3 release candidate. I suspect for > > now disabling SMB2/3 on the Windows 10 client is your best, if not > > ideal, option. > > > > Instructi...

On 11/02/15 17:42, soonerdave wrote: > I am migrating an old but functional Samba 3.3.4 smbpasswd-based PDC to a new > Samba 4.0-based VM. I planned to build the 4.0 as a BDC and then simply > dcpromo it to my PDC, and then retire the old server. But I've come across > two problems for which I'm needing some...

I am migrating an old but functional Samba 3.3.4 smbpasswd-based PDC to a new Samba 4.0-based VM. I planned to build the 4.0 as a BDC and then simply dcpromo it to my PDC, and then retire the old server. But I've come across two problems for which I'm needing some guidance. I've built the 4.0 box, extracted the original domain SID, and joined the machine to the domain. I can log into

On 12/02/15 18:42, soonerdave wrote: > I'll certainly give that a try this evening, Rowland. Thank you for the > suggestion and review. > > What concerns me about the wbinfo issue on the existing PDC is that there's > really no rationale for it *not* to work. Almost makes me wonder if there's > som...

* sigh * this is becoming an exercise in frustration. * Performing a direct migration of my Samba 3.3.4 box by copying .tdb and related files to the new machine looks like a non-starter, as the group_mappings file went from an ldb to a .tdb format, and it appears the only conversion occurs during an in-place version upgrade. * The next step, it appears, looks to be some sort of upgrade to the

On 15/02/15 04:41, soonerdave wrote: > Update > > I did update my Samba 3.3.4 PDC to 3.6.24 after MUCH grief, overcoming (at > least) two library incompatibilities PLUS recalling the dusty old memories > that if you start with Slackware, you use Slack's samba installer, not the > source from Samba itself....

On Thu, 2015-02-19 at 22:06 -0800, soonerdave wrote: > ***** SUCCESS ***** > > After nearly a week of wrangling with this annoying and frustrating issue, > I'm delighted to report that I finally have EVERYTHING working. I was on the > cusp of giving up, but some diligent reading, lots and lots of testing, and > some long...

On 12/02/15 02:43, soonerdave wrote: > As promised, I'm posting the smb.conf files for the two servers in question. > > One minor correction I should offer is that the new SAMBA server will be > version 4.1, not 4.0. > > Following is SMB.CONF for the current PDC, which is Samba 3.3.4 on Slackware > 13....

Hi, Rowland, and thanks for the reply. The PDC OS is Slackware 13. The BDC OS is Slackware 14. The choice to use Samba 4.0 was merely due to its inclusion on the Slackware 14 distro. I'll worry about upgrading that once I have the migration complete. I will post the two machine's respective smb.conf's later today. -- View this message in context:

No broken domains!! That's for sure. Actually, I am leaning toward abandoning the "migration" effort as much as just replacing the server (as noted in the upgrade section of the Samba Guides) by manually copying the relevant files to the new SAMBA server. I'm beginning to realize that if whatever is broken is actually broken on the server I plan to retire, then time spent

Update I did update my Samba 3.3.4 PDC to 3.6.24 after MUCH grief, overcoming (at least) two library incompatibilities PLUS recalling the dusty old memories that if you start with Slackware, you use Slack's samba installer, not the source from Samba itself. I've fixed two library problems with libtalloc and libwbclient that prevented smbd from starting (with a Signal 6 - hard crash). It

***** SUCCESS ***** After nearly a week of wrangling with this annoying and frustrating issue, I'm delighted to report that I finally have EVERYTHING working. I was on the cusp of giving up, but some diligent reading, lots and lots of testing, and some long evenings finally paid off. I know this thread is kinda buried now by virtue of its age, but I wanted to highlight the problems I had and

As promised, I'm posting the smb.conf files for the two servers in question. One minor correction I should offer is that the new SAMBA server will be version 4.1, not 4.0. Following is SMB.CONF for the current PDC, which is Samba 3.3.4 on Slackware 13. I've omitted all share definitions to allow focus more on the configuration side. Actual server/domain names have been omitted.