search for: soonerdew

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

...y I know the reason why it is working without "." in workgroup name, Is there any specific reason? I tried several settings in smb.conf as well as registry settings in windows 10 PC but it was not worked. Regards, Ram Prasad Bikkina On Wed, May 18, 2016 at 8:28 PM, David Whitney <soonerdew at gmail.com> wrote: > A couple of other issues to keep in mind... > > Aside from the fact that the errors suggest your W10 box is trying to join > an AD domain, W10 also defaults to a protocol of SMB 3.3 which Samba 3.x > does not support. If you resolve the issue wherein W10 thi...

A couple of other issues to keep in mind... Aside from the fact that the errors suggest your W10 box is trying to join an AD domain, W10 also defaults to a protocol of SMB 3.3 which Samba 3.x does not support. If you resolve the issue wherein W10 thinks it is joining an AD domain, there's a strong possibility (if not certainty) you will then see errors in the log of the W10 box indicating

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

If the problem machines are Windows 8 or later machines, it *could *be an SMB protocol negotiation issue. Windows 8 will attempt to negotiate SMB 3.11, but samba < 4.3 will cap at SMB 3.0. SMB 3.11 support came out with Samba 4.3.x. If this is the problem, you could either disable SMB2/3 on the Windows 8 box as noted in https://support.microsoft.com/en-us/kb/2696547, or possibly consider

Hi, all. I have discovered that I botched a migration from a 2.2.8a Samba PDC to Samba 3.3.4; in particular the domain sid was not preserved. Users of the domain have been authenticating presumably against cached local machine credentials, mapping them to their old domain SIDS. That's ultimately how I discovered the domain SID had been trashed - every machine started showing unmapped users

Greetings, all. I have a Samba 3.3.4 PDC up and running on my small home network, having migrated from an older 2.2.8 configuration. My XP Pro and Vista clients have remained as members of this migrated domain, logging with no problem. Client logins have worked precisely as expected. All seems to be happy - with one exception. My only problem, which I've spent the last two or three days

All: On various occasions, some users have posted questions regarding the situation in which their Vista clients are unable to log on to their Samba PDC from their workstations, receiving the "The trust relationship between this workstation and the primary domain has failed" message. Ordinarily, the solution I have seen for this issue is to remove the machine from the domain and rejoin

***** 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

* 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

Paul, Thank you very much for your information. I, too, had noticed that the ProfilePath and CentralPath values could be altered to point to the proper local path, and that technique at least fixed the immediate problem. Unfortunately, further review of my setup has revealed a very frustrating migration issue that I had not yet realized. The issue is very subtle and very frustrating, but I believe

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,

Greetings! I have a brand new Windows 10 Pro box, Version 1703, Build 15063.1155, and made the two registry mods (DNSNameResolutionRequired and DomainCompatibilityMode) to enable it to join an old-style NT4 Samba domain (Version 4.3). However, I note that the dialog for joining a domain within Windows 10 now specifically says to "Join an Active Directory Domain," and no attempt to join

Grettings, all I have a bizarre problem on a laptop in my Samba 3.3.4 domain. This domain includes a mixture of XP Pro and Vista Ultimate clients. I had just completed a migration to this new domain (from a Samba 2.2.8a domain), and all seemed happy and well - machines had rebooted and were still active in the domain, users were logging in with no problem, shares were working perfectly - all

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

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.

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: