similar to: wbinfo, net, getent and groups

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

We have two servers, one PDC and one Domain Member Server. I have been having problems with the Domain Member Server since a recent upgrade to Samba 3.0.28a on Ubuntu. Every time samba is restarted users lose access to the shares on the Member Server. It appears to be related to group mapping. Users on the Domain Member (Louise) seem to be GID "users", not GID "samba" as

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 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'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 have having problems with what should be a fairly simple configuration. I have a PDC and a Member server accessed by several windows workstation. The PDC seem to be working fine, but every time I restart the network (usually for an update) all users have problems accessing the shares on the Member Server. Sometimes only a few share are accessible. sometime none. I have been able to get it

I have a problem with a Member Server on Samba 3.0.28a running on Ubuntu Heady. Both systems were recently upgraded using Ubuntu's automated upgrade. It's also possible I broke a working configuration by accident. The shares on the Member server are visible on the XP clients and some users can authenticate properly. At least one user on one XP desktop cannot. The shares are visible

I may have a clue. I have two servers running Samba 3.2.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 but no combination

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 had a long running problem with two servers. One is the PDC of a NT style domain one is a Member Server. Sometimes when I restart the servers after maintenance some users lose connections to the Member Server. Sometimes it takes several hours for the problem to show up (today it took about 16 hours). I have been unable to determine the cause but I can usually solve it by restarting

I am moving our Samba Server from Solaris to Linux on a new server. I have the users moved the users home directories moved and showing up correctly on the workstations. The Profiles are in the Users home directory. Users profiles seem to be saving correctly and being read, however no changes can be made to them. The new server are Ubuntu AMD64 Linux with Samba 3.0.22 One of these is the

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

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

All, Hey hey, am new so if this is way basic, flame on. ;-) I have a Dell Poweredge 2300 running RedHat 6.0 and whatever versions of samba and such that are part of that distribution. Samb 'works' from the standpoint of file sharing and printing in a sense. The issue is that the printer is an HP Laserjet 4 connected via an external HP Jetdirect box running IP. The only connection to

On Sun, 24 Feb 2019 13:08:07 -0500 Robert Steinmetz <rob at steinmetznet.com> wrote: > Rowland Penny via samba wrote: > On Sat, 23 Feb 2019 19:55:03 -0500 > Robert Steinmetz via samba <samba at lists.samba.org> wrote: > > 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