similar to: Users lose connections after restarting servers.

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 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 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'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 two samba servers running Ubuntu 10.04 Samba Version 3.4.7 One server acts as domain controller and stores user ids in a .tdb Somehow I've ended up with a duplicate user name. On the Domain Controller # pdbedit -w -L|grep debbie debbie:1005:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:84DEC6FE3B018B0FB977EDDF5009742C:[U ]:LCT-4D4B086F: On the other Server running winbind I get #

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

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 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'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, when i send the SIGHUP signal to Samba, then Samba won't load the printers from CUPS. I need to shutdown Samba and start it again. Now when i'am running cupsaddsmb i got the following errors(this error occours in 3.5.x but not in 3.2.x): server-p:/# cupsaddsmb -H server-p -v edv01 edv02 edv03 Kennwort f?r root erforderlich, um ?ber SAMBA auf server-p zugreifen zu k?nnen:

Hi. We add a new virtual machine with vmware server 1.0.4, centos 5.x client, we update the server with yum and receive samba 3.0.25b-1.el5_1.4, we have a PDC running Gentoo with Samba 3.0.24+ldap, all the windows clients and other Linux boxes(.3.0.10 + 3.0.23 + 3.0.24) are working very good and stable. The only problem is this new server, i read about some changes with samba 3.0.25b and

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

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

Hello! i have some trouble with my samba setup (v3.4.5 or 3.3.10). the server is not responding (or very slow) for some minutes in log.winbindd-idmap i get: ---------------------------- [2010/02/03 04:14:27, 1] lib/util_tdb.c:521(tdb_wrap_log) tdb(/home/samba-server/samba/3.4.5/var/locks/mutex.tdb): tdb_lock failed on list 43 ltype=1 (Interrupted system call) [2010/02/03 04:14:27,

Hello, I saw on my member servers in winbindd.log sometimes the following message appearing: [2009/05/29 21:51:53, 1] rpc_client/cli_pipe.c:cli_pipe_validate_current_pdu(755) cli_pipe_validate_current_pdu: RPC fault code DCERPC_FAULT_OP_RNG_ERROR received from host GENOME, pipe \lsarpc, fnum 0x7101! What does this error mean and how can I fix it? PDC and meber server are running 3.3.4.

I recently brought up our fifth Samba domain member server with 3.0.26a-0.9-1787-SUSE-SLES9 against an NT4 domain on a new subnet. The subnet also has an NT4 BDC that is working correctly. Wbinfo and getent both work properly but users can not get to the [homes] service but can get to another share that is on the same system. If I setup a share definition in smb.conf for myself as a home

I'm testing out a new Samba setup to hopefully replace my aging Win2k domain. I've got some of it working: - My PDC (shadow) seems to be working on the CASA domain with an LDAP backend. - nss_ldap and pam_ldap are working on shadow - I can run wbinfo -u and get the user info from LDAP on shadow. - I can run wbinfo -a username%password and authenticate a user on shadow. I can run

Thanks for the response. I think  found and fixed the problem, but I need to do some more testing tomorrow. It seems that the "handle_name_resolve_order: WARNING: Ignoring invalid list value 'hosts'  for parameter 'name resolve order'" is not really a warning and it causes testparm to stop processing the smb.conf. I think that is also what caused the daemons to fail.

I thought I had setup winbind correctly as I can login to my ubuntu 9.04 machine with domain users, but I am trying to get ntlm working with squid, and while testing winbind I get the following error. sudo wbinfo -a MBAG\\user%passwd plaintext password authentication failed Could not authenticate user MBAG\user%passwd with plaintext password challenge/response password authentication failed error