similar to: Incompatibility Windows 7

That is really weird. I think what is happening is that if you log in immediately you are using cached credentials. If you wait a little bit then your network connections are up and you are truly doing network authentication. If you were do unplug from the network, reboot, login with cached credentials, and then reconnect network cable I would suspect your access to shares would be OK. I

On 05/31/16 11:09, pisymbol . wrote: > 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 >

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

On 06/20/16 15:19, Rowland penny wrote: > 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

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

Thanks for your response, Rowland. Sorry for the late reply. Here is my smb.conf: [global] workgroup = grouptest1 server string = %h server (Samba NAS) dns proxy = no log file = /var/log/samba/log.%m max log size = 10000 syslog = 0 panic action = /usr/share/samba/panic-action %d server role = standalone server obey pam restrictions = yes unix password sync =

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

ORACLE have released this patch for Solaris 10 - Samba v3.6.25: IDR152387-03 addressing CVE-2016-2118 (BADLOCK) and other CVEs for S10 SPARC Which has addressed our issue. Thanks -----Original Message----- From: samba [mailto:samba-bounces at lists.samba.org] On Behalf Of Gaiseric Vandal Sent: 07 June 2016 14:51 To: samba at lists.samba.org Subject: Re: [Samba] Solaris 10 Configure failure

On a samba 4.5.1 domain controllers (PDC and BDC), classic domain , LDAP is used as the backend for both user accounts AND for the idmapping of trusted domains . Partial smb.conf below workgroup = THISDOMAIN security = user passdb backend = ldapsam:ldap://xxxxxxxxxxxxxxxxx idmap config * : backend = tdb idmap config * : range = 5000-6000 idmap config THISDOMAIN :

Rowland penny via samba ha scritto il 24/08/20 alle 17:39: > [...] > As far as I am aware, SMBv1 is still readily available on Win7, but from > Samba 4.11.0, it is now disabled on Samba, so if you must use SMBv1, you > will need to set: > > client min protocol = NT1 > > server min protocol = NT1 > > in smb.conf ok, the samba server I'm using as test has

The wiki page settings control a netlogon security setting. I guess the "server signing" parameter applies to all the other traffic. But my guess - and it is only a guess- is that requiring server signing is causing the netlogon process to break since it does not support signing. The e-mail chain you reference does not make it clear if the samba instance is a domain

On 25/08/2020 08:28, Piviul via samba wrote: > Rowland penny via samba ha scritto il 24/08/20 alle 17:39: >> [...] >> As far as I am aware, SMBv1 is still readily available on Win7, but >> from Samba 4.11.0, it is now disabled on Samba, so if you must use >> SMBv1, you will need to set: >> >> client min protocol = NT1 >> >> server min protocol =

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

Thanks for your reply, Louis However, I am still blocked by this problem now. !-_- I tried to set the samba server as the DNS server and visit the shared folder by input "\\aaa.bb.com" at windows 7 client. In some cases it works and will not fail. However the similar abnormal phenomenon also occasionally happens (especially at changing the authentication, such as local to ldap): 1) I can

I'm not sure if this is supported or not, but I can't get it to work. I'm trying to get the smb password and the unix password to sync for mapped users. I have have 'unix password sync' turned on and I have the username mapping file set up. When I change a users password in windows (where the username is the same in windows and linux) the password changes just fine. When I

>* Am 13.04.2016 um 07:51 schrieb Mogens Kjaer <mk at lemo.dk <https://lists.centos.org/mailman/listinfo/centos>>: *> >* Hello, *> >* I run a CentOS 6 machine with samba, serving approx. 150 Windows users with samba running as an NT-like PDC. *> >* After today's samba update (samba-3.6.23-30.el6_7.x86_64 etc.), nobody can log in. *> >* They all get the

Hi, I have installed samba on one of my Unix server( SUN) and I am trying to access the share directory from a NT workstation. Earlier If I had used a guest account and I was able to connect to the share created on the Unix server. Now I want to access with users / groups through NT domain server which I received the following error : The account is not authorized to login from this

Hi, I'm just installing Samba for the first time and have a problem with name resolution on my test client. Samba 3.0.8 is installed on a RHES system named 'fileserver1 (.our.xxx.edu)'. The clients are Windows 2000 and XP systems. This is a subnet that is part of a larger campus network. There is no Domain, just a workgroup called 'our_adm'. I have a very simple smb.conf file

Hi, File server - samba 2.2.12 serving win95 and winXP systems. Win95 systems see network appropriately. WinXP systems can see the files when I do run > \\servername\filefolder\ but NOT when I go into my network places... What do I need to do to fix this? notes - a) changing the samba config files at times knocks out the win95 clients.. (config file below) b) winXP pro systems -