similar to: cannot login from some machines after upgrading from 2 to 3

Hi all, I'm having a problem with an upgrade of Samba running on a Redhat4 Update 4 system. The default installation provides only 3.0.10 which doesn't include the privilege model or a number of fixes including some in 3.0.21a and 3.0.23 which it looks like we'll need. The system runs in PDC mode with user accounts in an ldap database. On a test system which I'm using to

The below Globals section is reporting some testparm failures that don't make sense to me. Perhaps someone could shine a light for me? This is a new installation - from 3.6.23 to 4.10.6-1. Necessitated by a Windows Server 2016 DC being installed. The testparm command, when run, reports the following error(s): # testparm Load smb config files from /etc/samba/smb.conf Loaded

Hello, i have a fresh installed/compiled from source samba 4.11.2 on ubuntu 18.04. But samba wont start. Syslog output: Nov? 6 12:15:19 dms systemd[1]: Starting Samba4 smbd... Nov? 6 12:15:19 dms systemd[1]: Started Samba4 smbd. Nov? 6 12:15:19 dms smbd[1557]: [2019/11/06 12:15:19.594448,? 0] ../../source3/auth/auth_util.c:1385(make_new_session_info_guest) Nov? 6 12:15:19 dms smbd[1557]:??

Hello, I've been using samba for a few years but I use it only occasionally. Today, I've found out that since the upgrade to 4.9.2, smbd wouldn't start. I use Arch Linux. The command that starts samba on the systemd service is this: /usr/bin/smbd --foreground --no-process-group These are my configuration file's [global] parameters: bind interfaces only = Yes domain master =

*I am running Samba on CentOS 7 and for some reason I cannot get the smb daemon to start (Samba version 4.9.1). This is the status after a failed start:* smb.service - Samba SMB Daemon ???? Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: disabled) ???? Active: failed (Result: exit-code) since Mon 2019-10-14 10:29:59 EDT; 31s ago ???????? Docs: man:smbd(8)

Hello all; I am installing samba4 (version 4.9.5) on Debian 10.5 to use it as a member of a samba4 AD DC domain (version 4.11.4). I am following the guide https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member but I am having problems starting samba. So far I have installed the necessary packages listed here

Hello all, I guess that everyone knows the message "the trust relation between this workstation and the primary domain failed" when joining Win7 into samba domain. Unfortunately, the same problem appeared few hours/days after the machine was successfully joined in the domain(with reg keys from https://wiki.samba.org/index.php/Windows7) and user able to use it for awhile. Then at

On 05/10/2019 14:10, Rowland penny via samba wrote: > On 05/10/2019 13:41, lejeczek via samba wrote: >> hi everyone, >> >> I believe a resolution is there - >> https://access.redhat.com/solutions/4367771 > Which is behind a paywall ;-) >> >> But what I'm hoping for is an expert would comment how >> would this apply >> to Samba with LDAP

Hello, My PDC is working but I have some errors on my log, I'm searching since some days but I cannot find why. In log.smbd I have [2006/08/22 16:30:22, 0] lib/util_sock.c:get_peer_addr(1229) getpeername failed. Error was Noeud final de transport n'est pas connect?? And In log.MachineName I have [2006/08/22 19:17:33, 0] auth/auth_util.c:create_local_nt_token(899)

Hi, I'm trying to migrate our PDC from samba 2.2.3 on redhat 7.3 to samba 3.0.10 on fedora core 3. We use smbpasswd which I have copied to the new server - all the unix users and groups are yp'd so they're the same on both servers. Everything seems to work fine initially. Most people can log on and get their roaming profile from most machines (they can all log in from their own

I have upgrade the pdc server from debian sarge to etch. After this operation we can't login to the domain (client windows 2000 & XP) smbclient works fine and from a windows local account I can browser the samba directories too (puttin username and password before..) I use tdbsam of course and pdbedit -L let me see all the accounts, it seems to work fine I tried to remove a pc from

Hello! I want to permit the root account to be called administrator from the win clients in my network. Therefore I have added 'root = administrator' in my /etc/samba/smbusers. I have also added 'username map = /etc/samba/smbusers' in smb.conf. When I try to log on as administrator from a windows client I get a message that the user does not exist. I am running samba 3 on

Hello, I'm running Mandrake 9.2 and Samba-3.0.2a I'm connecting a Samba Server as a Domain member to an 2003 ADS, called TEST2. I've been able to create the computer account. I've also tested successfully, from Chapter 7 of ' Samba HOWTO Collection' with a W2K client logon/mount a share from the samba server using Kerberos. The testing of the smbclient was also

I have a samba 3.023c server with winbind joined to a windows 2003 AD domain. The issue I'm having is from the windows computers, I can't connect to shares on the samba server using the administrator account. It works just fine with normal domain users. When I try to connect with the admin account, I the smbd process that forked to handle the request core dumps. The same thing

I have a number of Samba servers on RHEL (Samba 3.0.33) in an AD environment using a mix of Windows 2008 and windows 2008 R2 servers. Configuration file is pretty minimal: [global] workgroup = AVWORLD security = DOMAIN log file = /var/log/samba/samba.log max log size = 500 wins server = 10.50.4.31 dns proxy = no #log level = 10 log level = 3 passdb:5 auth:10

I'm relatively new to samba I have been experimenting for a week or so, though I have setup several 2000/NT domains and have been using Linux for a couple of years. I'm using Red Hat 9, updated completely via apt. Samba 3.0.9 installed from apt and i am using the stock ldap server that installed with red hat as my back end. I followed the samba.idealx.org guide to get to where I am

Hello, I have a problem where non-AD systems can no longer connect to Samba shares. Samba 3.5.x servers are a members in AD, Windows 2008R2. This has worked flawlessly since we initiated it a couple years back. This happened to all 3 Samba servers after AD servers were rebooted. My thoughts are it was a Windows update that wrecked the system. Here is a typical setup: Winbind not used Samba

Running Samba mostly on Redhat 5 with version 3.5.4-0.83 Also failed on Debian 3.5.6 and Solaris with a 3.5 version. Logging details here are from Redhat case. We have a similar problem on all Unix/Linux systems using ADS as the backend authentication for samba shares on Unix/Linux. It was working before today and we didn't change anything. Today, any time we try smbclient or a Windows drive

Hi, I'm trying to use the sambaUserWorkstations option to allow users to log on certain computers only. This option looks great... In fact it looks now a lot better than the 'ldap filter' one than was deprecated with samba 3.0.20... The fact is, if the sambaUserWorkstations option works well with machine names, it doesn't seem to work when specifying groups of machines.

My Question: ------------ Is it possible to get 2-way Interdomain Trust relationships working between a Samba domain and an NT4 SP6a domain, while restricting all password hashes to NTLMv2 only? Everything works except the inter-domain trust I'm able to get the NT4 domain to trust the Samba domain, but not the other way around. My System: ---------- I have a perfectly running Samba domain