similar to: Problem joining Samba 4 to Samba 3 PDC

On Fri, May 27, 2016 at 3:55 PM, Gaiseric Vandal <gaiseric.vandal at gmail.com> wrote: > Is the netapp a member of the domain? Yes. > My assumption is that you can have domain members that are patched with domain controllers that are not. I don't know what you mean by that. This worked before the samba CVE changes took effect in the latest samba3 RPMs distributed by the CentOS

On 14/05/16 05:10, Ram Prasad Bikkina wrote: > ---------- Forwarded message ---------- > From: Ram Prasad Bikkina <parvathiprasadb at gmail.com> > Date: Sat, May 14, 2016 at 9:39 AM > Subject: Re: [Samba] Not able to join windows 10 clients to samba 3.6.23 > NT4 Style PDC > To: gaiseric.vandal at gmail.com > > > Hi Gaiseric Vandal, > > I applied these

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

Running a mix of samba versions (3.6.25 and 4.5.1) in two domains- one "classic" (with samba domain controllers) and one AD (with windows domain controllers.) The eventual goal is to drop the classic domain in favor of the AD domain. Also trying to move from samba 3.x to 4.x since Samba 3 is EOL'd. the "wbinfo -u" command will list users in the servers domain

On Mon, Apr 30, 2018 at 11:55:24AM -0400, Gaiseric Vandal via samba wrote: Hello Gaiseric. > I suspect at this point making Windows 7 and Windows 3.11 interact is a > loosing proposition.     It is pretty scary to think that there is still > equipment that requires  Windows 3.11.  Hopefully it is air-gapped and not > part of the electrical grid. I can evaluate different options: I

Hi, I resolved NMBD errors, but still same error in windows 10 pro, Could please suggest any changes in windows 10 PC. Applied registry changes suggested by samba wiki but no improvement. I am able to join windows 7 clients without error. Regards, Ram On Mon, May 16, 2016 at 8:11 PM, Ram Prasad Bikkina <parvathiprasadb at gmail.com> wrote: > Hi Gaiseric, > > Thank you for

On both the synology (samba 4.1.20) and PDC (samba 3.6.25) testparm showed client schannel = Auto server schannel = Auto I don't know if the server even supports schannel. Maybe it doesn't any all the clients successfully negotiated not to use it. On the synology, I set client schannel = no This fixed my domain membership issue. Although

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 have a Synology NAS array appliance. It is linux based and uses samba for file sharing. Normally the config is done via a gui interface but you can ssh to the array. The domain controllers are running Samba 3.6.x in classic domain mode. I have member servers running 3.6.x and 4.3.8. no problem. I recently updated the Synology "OS." The current version of samba is

On both Samba 4.5.1 member server and Samba 3.6.25 member server I tried the following command wbinfo –set-uid-mapping=35049,S-1-5-21-xx-xx-xxx-xxx this should have created a mapping entry consistent with the one on the domain controller for a trusted user But I got the following error failed to call wbcSetUidMapping: WBC_ERR_NOT_IMPLEMENTED As far as I can tell from network

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

On 20/06/16 19:53, Dale Schroeder wrote: > On 06/17/2016 4:31 PM, peter lawrie wrote: >> Hi all >> About 18 months ago I connected 14 new Windows 7 PCs to a Centos5.1 >> server >> with samba3x as domain members. There are no other servers on site. >> Today, I had to visit to connect up a PC in a new location. As I would >> normally do I checked for Centos

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

Suggested changes applied to smb.conf (and yes, server role is classic PDC): server max protocol = NT1 client signing = auto client ipc signing = auto server signing = auto With no apparent change to the behaviour or resolution to the problem(s). I'm particularly mystified by the logging-in behaviour (that is, if I manage to do it quickly I can log in, but if I

Thanks for your attention, Gaiseric. Sorry , but I had a little confused. Did you mean that the problem was something relevant with the DNS? However in my impression, I might not do anything about the DNS. I have some clues that might be helped: 1) First of all, my samba server version set is "max protocol = SMB2", and the final protocol according to the negotiation result is smb2.10.

The client is a Windows 2008 R2 server. I don't know what you mean by classic vs. AD. I assume it's AD, but how would I check? I see the same problem, i.e. "Access is denied" and a window to enter the username/password, if I use the fully qualified name. Thanks, Rob On Fri, Jan 12, 2018 at 10:58 AM, Gaiseric Vandal via samba < samba at lists.samba.org> wrote: > Can

This morning due a a power outage our samba servers crashed. All looked OK at reboot (at first) - users who had stayed logged in could still access shares. However users who tried to log back into the network got the "The trust relationship between this workstation and the primary domain failed" message. Removing a machine from domain and rejoining did not help. Servers are a

Hello everybody, we have a problem joining a domain from a remote location. The remote location is connected via VPN. Everything is working as exspected but joining the samba domain from the remote location does not work. - Server Samba Version is 3.5.10 - Windows Client is XP SP3 - Joining the domain locally works without problems - ping does work in both directions - WINS is running on the

Just a follow-up. Still, no resolution. I've tried different combinations with "client ipc signing" without luck. A traffic dump shows the problem as: i) windows XP client sends a DCE/RPC SAMR command GetDomPwInfo ii) samba DC responds with DCE/RPC Fault nca_proto_error I've also tried fiddling with Local Security Policy registry values at the Win XP machine, but got nothing

I currently have several fresh installs of XP that will connect to shares, but will not reconnect after a workstation reboot. These are workstations that are not joined to the domain. Only accessing shares from a local profile, but using the same user/pass to login as to connect to Samba. I get various errors at that point. Upon reboot, attempting to access the share generates: "An error