similar to: 3.4.5->3.5.3 breaks domain logons

I turned off server signing, and domain logons work now. On the server, I had set lanman auth = no ntlm auth = yes and the clients have Digitally sign client communication (when possible) Enabled Digitally sign server communication (when possible) Enabled LAN Manager Authentication Level Send NTLMv2 response only\refuse LM So my guess is that the samba update changes the

I've been trying to upgrade from samba 3.4.5 to 3.5.x (currently 3.5.3) on a Ubuntu 9.10 system where I compile my own Samba. The server is a PDC for several win2000 clients and uses an LDAP backend hosted on the same machine. After the upgrade, clients can connect to shares but can not perform domain logons. 3.5.3 does not build a browse list of other domains on the subnet. Executing

I'm building a replacement samba 3.5.6 domain controller to replace an old 3.0 one. Some other things are changing too. Our user accounts are now in LDAP rather than flat files (although the machine trust accounts will remain in a flat file), but that should be hidden from samba as it's going to be done through NSS. The smbpasswd file is a TDB file and will remain so. Our users

Hey! I Have a problem with samba as is noticed, in fact, i have two, and i will start in order. When accessing the shares on my samba server, it sometimes freezes, i have the lateste version, 3.6.1, mas since version 3.4 wish was the first i used, i've been running into this problems. When i try to browse the shares, many times, like 1 in 10, it freezes and sometimes, when saving files,

Hello, we are currently in the process of migrating Windows machines to Ubuntu 10.04. For now, these machines act as samba clients in a Windows domain (which is controlled also by a samba PDC), and are itself sharing files via SMB/CIFS. The clients are - from time to time and with no apparent reason - losing their domain membership. When this happens, access to shares on the PDC still seems to

think it is a bug of samba but maybe someone can help me figure this out :-) Attached is the log and the relevant parts of smb.conf p.s. the share's name is 'privat' thanks & regards vinz ------=_20110202165921_20608 Content-Type: text/plain; name="smb.conf" Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename="smb.conf" #

think it is a bug of samba but maybe someone can help me figure this out :-) Attached is the log and the relevant parts of smb.conf p.s. the share's name is 'privat' thanks & regards vinz ------=_20110207170208_63601 Content-Type: text/plain; name="smb.conf" Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename="smb.conf" #

hi, i wondered why i can still list my shares with "smbclient -NL localip", security = SHARE ....i just disable the user nobody? the log: [2005/11/27 12:05:48, 2] lib/interface.c:add_interface(81) added interface ip=192.168.10.66 bcast=192.168.10.255 nmask=255.255.255.0 [2005/11/27 12:05:48, 2] lib/interface.c:add_interface(81) added interface ip=127.0.0.1 bcast=127.255.255.255

Hi list, sorry in case I do ask a FAQ, but I did in fact find some more mentions of a problem like this, but always without a solution. I upgraded our Samba server today (from 2.10/SuSE to 3.0x/Debian) and have problems with some of the clients (Windows XP). When trying to access a share from these clients, I get a NT_STATUS_LOGON_FAILURE, and increasing the log level reveals several occurences

We are using samba 3.4.8. We have some pc's using OS Windows XP Pro dan others Windows 7 Pro. All of them can join and logon domain to samba PDC + LDAP. FYI, the windows 7 clients are already hacked at registry settings: [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters] "DNSNameResolutionRequired"=dword:00000000

Hello all, My Samba server has undergone a series of migration. And recently, I found that the newer accounts fails to login to older computers in the network. All PCs in my network runs Window XP. And I'm running Samba 3.4.7 here as PDC. When I login with a new account called "guest2", the computer says the password of my login is incorrect. What is my problem? What should I

Hi, The following ii ?samba ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?2:3.4.7~dfsg-1 SMB/CIFS file, print, and login server for Unix ii ?samba-common ? ? ? ? ? ? ? ? ? ? ? ? 2:3.4.7~dfsg-1 common files used by both the Samba server and client ii ?samba-common-bin ? ? ? ? ? ? ? ? ? ? 2:3.4.7~dfsg-1 common files used by both the Samba server and client are installed on a squeeze ( 2.6.32-3-686 #1 SMP Thu

Hi, I'm using latest Samba version 2.2.8a and are preparing a production server system, which was working fine recently in development stage. My system is basically a SuSE 8.2 Pro with some of the applications being installed manually from source. I'm using CUPS as printer backend and add printers to the system using lpadmin Afterwards I make a reload (or even a restart) of smbd and

Hi I've talked about this in other messages but have a feeling it might have got lost amongst the other symptoms we were discussing. I had a Redhat 9 server on which I'd installed Samba 3.5.6 (built from source). I had it authenticating successfully against a windows 2008 active directory server. I then upgraded the Redhat server to RHEL5.3, on which I installed Samba 3.5.7 (and

Hi, I have two servers, servera (DOMAINA) and serverb (DOMAINB). I have made a trust between this domain. But I try logon computer from domaina as user for domainb, the log in serverb wrotes me that a authentication was succeded: [2004/10/12 17:19:19, 3] rpc_server/srv_netlog_nt.c:_net_sam_logon(620) SAM Logon (Network). Domain:[DOMAINB]. User:[bronasek@\\XP1] Requested Domain:[DOMAINB]

System Summary: centos 6.2 samba 3.5 smbldap-tools 0.9.6 openldap 2.4.23 Hello, I am installing smb 3.5 on a CentOS 6.2 host using smbldap-tools. I've previously installed a similar configuration on RHEL4 using smb 3.0 but CentOS now uses nss-pam-ldapd and nslcd instead of nss_ldap, so the configurations cannot be moved straight across. Currently, when I attempt to connect to an smb share

Thanks TMS, that is not a major problem as of now.. i dont know why but i m facing many problems/errors while using samba :). now the major problem is wbinfo -g is not showing the full list. only few domain groups it is showing . do u have any idea about this ??? .please help On Fri, Jun 25, 2010 at 6:44 PM, <tms3 at tms3.com> wrote: > > > > --- Original message --- >

Good day. I have a problem with connecting Samba 3.5.5 and Windows 7. First of all I have added DomainCompatibilityMode and DNSNameResolutionRequired to windows registry. After that i tried to connect windows to samba domain, but without any results. And some time ago I see, that I can't access Samba shares with right login and password. Windows 7 diagnostik says that It can't find

Hi list, I have the problem, that a samba 2.2.8a server cannot validate the password with a samba 3.0 pdc for a client request. A samba 2.2.1 works fine. Let me explain the situation in more detail: samba 3.0 pdc machine a samba 2.2.8a server machine b (doesn't work) samba 2.2.1 server machine c (works) samba 2.2.8 client machine d Machine b and c should authenticate the passwords

Using LDAP and the smbldap-tools. When attempting to join the domain with an administrative user, the computer gets added to the Computers list in LDAP with the following attributes: cn: workstation75$ description: Computer gecos: Computer gidNumber: 515 homeDirectory: /dev/null loginShell: /bin/false objectClass: top, account, posixAccount uid: workstation75$ uidNumber: