similar to: Missing record in share-info.tdb

I need help understanding what is happening and trouble shooting. I have two servers running Samba 2.3.3, one as a Domain Controller one as a Member Server. Both are running Ubuntu 8.10. smbd, nmbd and winbindd using the tdb back end are running on both. I have two shares on the member server and as far as I can tell they are identical. [Projects] works as expected but [Windows] always asks

I have two servers running Samba, one as a Domain Controller one as a Member Server. Both are running Ubuntu 8.10 and running smbd, nmbd and winbindd using the tdb back end. I am having a problem understanding ID mapping. The mapping is not the same on both machines. On the Domain Controller > root at thelma:/etc/init.d# wbinfo -i 'ATLANTA\rob' > rob:*:1000:2003:Robert

I'm running out of things to check. I have two servers running Samba 2.3.3, one as a Domain Controller one as a Member Server. Both are running Ubuntu 8.10. smbd, nmbd and winbindd using the tdb back end are running on both. On the Member Server when I access the [Projects] share everything works as expected. When I access the [Windows] share I get prompted for a user name and password

I had to remove reference to some printer drivers via tdbtool on ntdrivers.tdb. 1. Do I need to restart smbd and nmbd to make these changes take effect? 2. If I restart smbd and nmbd will connected users get disconnected?

I have two servers running Samba 2.3.3, one as a Domain Controller one as a Member Server. Both are running Ubuntu 8.10. smbd, nmbd and winbindd using the tdb back end are running on both. I am don't understand the results. As far as I can tell I have everything configured as it should be. The basic globals for the DC [global] workgroup = ATLANTA time server = Yes

I ungraded my Linux Operating system from Ubuntu 16.04 LTS to 8.04 LTS Samba will not start after an upgrade to 18.04. My samba is running as an NT style member server server with smbd nmbd and winbindd all running. None of them will start. It worked this morning. This morning it was running Version 4.3.11-Ubuntu This afternoon after the upgrade it's Version 4.7.6-Ubuntu The logs in

I have a problem with accessing two share. Sigma works as expected one Windows always asks for a login name even though their smb.conf entries are the same; I even tried adding public to the Windows share with no success. [Sigma] Comment = Sigma Design Data path = /files/Lucretia/Sigma writeable = yes browseable = yes create mask = 0764 directory

I just upgraded my Member Server to 3.2.4 on Ubuntu. I have a permissions problem. Users can create files on the Samba shares but they cannot delete files. Here is a typical share definition. [Testing] comment = Test for Samba path = /files/test browseable = yes writeable = yes create mask = 0764 directory mask = 0775 On the Linux side I can do

We have a Windows Domain NT. We are setting up four samba Servers, two new and 2 legacy servers. The new server are Ubuntu AMD64 Linux with Samba 3.0.22 One of these is the PDC. The legacy Servers are Solaris 8 running Samba 3.0.24. We are using winbindd and local tdb files on the PDC for authentication. We plan to migrate to LDAP latter. I have used SWAT to configure each server. I have

OK I'm back on this after a tour through firewalld and other issues. I see Louis has posted his how to on git-hub. It seems very helpful I also see his method uses the Ubuntu resolver but also uses bind9 so I'm not sure whether his method can be adapted to using the internal DNS in Samba. In setting this up one of my main goals is to limit the amount of customization I do as I have

I have had a long term problem with my set up. winbind authentication is erratic. Whenever I restart one of my servers the member server refuses to authenticate users. Sometimes is will only authenticate some users on some shares. Usually by fiddling with it I can eventually get it to work but I can't identify the solution so I can replicate it. Once I get can finally get it to work it

I have a Win 7 machine which accesses a Samba NT4 Domain. That machine has been used by a single user for a couple of years. I need to change the user. I find I can log in using the old users name and password, but if I try to login using the new users name and password I get an error message that there are no login servers. Sometimes I get an error message that there is not trust

I've posted about this problem several times but so far nothing has worked. Whenever I restart my samba servers the member server refuses to authenticate users. Sometimes is will only authenticate some users on some shares. Usually by fiddling with it I can eventually get it to work but I can't identify the solution so I can replicate it. Once it finally starts to work it works

Hello, There is a small document, which (I hope) useful to others samba user to avoid mistakes, wrong path, that i take, to reach my goal. This document is covered by license: xkcd501[12]. 1. Target 2. Situation 2.1. Software versions 2.2. Software setup 3. Data migration 3.1. alternatives 3.1.1. robocopy 3.1.2. xcopy 3.1.3. net 3.1.4. smbfs/cifs 4. Migration 4.1. Start samba 4.2. ACL vs ACL

Rowland Penny via samba wrote: > If you are only going to have one DC, then the internal DNS server is > okay, it just doesn't work as well as Bind9. Once you have more than > one DC (which is the recommendation), then it is better to use Bind9. I have two other servers. Once the ad-cd server is up the I plan to have the other servers moved to ad and act as alternate dcs > Louis

Hello everyone, I'm preparing a migration from a NT4-mode domain controller 3.5 to version 4.19. The migration process is going well, but from the share management MMC, no matter the share defined in the smb.conf, when I try to access the authorization tab, I get the following message in the Samba logs: Apr 25 11:39:58 svdom01.voillot205 rpcd_classic[1827]: [2024/04/25 11:39:58.511922, 0]

On Thu, 25 Apr 2024 11:44:42 +0000 Philippe Maladjian via samba <samba at lists.samba.org> wrote: > Hello everyone, > > I'm preparing a migration from a NT4-mode domain controller 3.5 to > version 4.19. The migration process is going well, but from the share > management MMC, no matter the share defined in the smb.conf, when I > try to access the authorization tab, I

On Thu, 25 Apr 2024 11:44:42 +0000 Philippe Maladjian via samba <samba at lists.samba.org> wrote: > Hello everyone, > > I'm preparing a migration from a NT4-mode domain controller 3.5 to > version 4.19. The migration process is going well, but from the share > management MMC, no matter the share defined in the smb.conf, when I > try to access the authorization tab, I

On Thu, 25 Apr 2024 12:42:16 +0000 Philippe Maladjian <pmaladjian at hilaire.fr> wrote: > On Thu, 25 Apr 2024 11:44:42 +0000 > Philippe Maladjian via samba <samba at lists.samba.org> wrote: > > > Hello everyone, > > > > I'm preparing a migration from a NT4-mode domain controller 3.5 to > > version 4.19. The migration process is going well, but

I have been running a small domain for years. I finally decided to move the domain to ad. I am also upgrading the server from Ubuntu i6.04 LTS to 18.04 LTS I installed the new server on a new RAID array and loaded the Ubuntu LAMP stack. I installed samba. I have gone through a few tutorials which offer differing recommendation on some things. All were based on either Debian or Ubuntu. I