similar to: Winbind dies

On Thursday July 13 2006 12:39 pm, you wrote: > Dimitri Yioulos wrote: > > Serious apologies if this has been discussed before, > > but my search didn't turn up much: > > > > I have samba (kept up-to-date with latest) running on > > several CentOS 3 and 4 boxes as part of a Win2k3 > > domain. ?On one particular box, ?winbind dies on > > a regular

All, I fear I''ve become a pita with this, but windbind periodically dying on one of my machines is really starting to cause grief, and I have no idea what might be causing it, especially as the same config is used on several similar boxes which do not exhibit the problem. While I've posted the problem previously, I thought that maybe this latest log entry after winbind dies

All, Yesterday morning, I updated samba from samba3-3.6.13-45 to samba3-3.6.14-45 (obtained from sernet) on a couple of CentOS 5.9 boxes. As soon as users started access these boxes, one of my sensors detected a winbind error, as in: Apr 30 08:19:36 norwell winbindd[13283]: ? INTERNAL ERROR: Signal 11 in pid 13283 (3.6.14) Here's what appears in syslog: Apr 30 08:19:36 norwell

On 11/11/15 10:41, Daniel Carrasco Marín wrote: > Hi, first of all i'm sorry for my english. > > I'm trying to create a print server in the same server that has the samba > AD but i cannot make it work. For now i've: > > - A working AD server with Samba 4.2.5 > - A Cups server with the print drivers > - GPO policies to install the printers in the

Since version 3.0.23b, I have been having trouble getting Windows & OSX users to access an NT domain member server running FreeBSD 5.4. It is now at 3.0.23c (installed this morning the 5th). root@aries:/usr/local/lib# net rpc user Password: Could not connect to server 127.0.0.1 Connection failed: NT_STATUS_NO_LOGON_SERVERS root@aries:/usr/local/lib# net rpc user Password: Could not connect

On 11/11/15 11:31, Daniel Carrasco Marín wrote: > Thanks to both but did not worked. Tomorrow i'll try to reinstall the > whole OS because maybe i've installed something wrong. > > Greetings!! > > 2015-11-11 12:08 GMT+01:00 Rowland Penny <rowlandpenny241155 at gmail.com > <mailto:rowlandpenny241155 at gmail.com>>: > > On 11/11/15 10:41, Daniel

Finally is working... I'm not sure, but maybe the problem was stupid (spool folder did not exist for example). Now I've another weird problem and I don't know how to find out the solution. When I use the original server fqdn or the ip address it works prefect, but I've added another dns entry and using that dns name all shares fail. I can resolve the name and even I can see the

Hi folks, Can anyone shed light on this issue? I haven't heard from you guys. Is there anything else I could do to expedite resolution of this issue? I've read the WHATSNEW.txt and reviewed the release notes. I am not sure if I've fully grasped what needs to be done. Can someone point me in the right direction? ~Doug -----Original Message----- From: Doug Sampson

Hi, I'm having a problem getting my Windows machines to access shares in Samba. When they browse to the Samba box it sometimes gives them an error saying that they don't have permission or that the server is unavailable. However this doesn't always happen and other times it lists the shares. When I try to access the shares it just prompts for the username/password over and over.

Thanks to both but did not worked. Tomorrow i'll try to reinstall the whole OS because maybe i've installed something wrong. Greetings!! 2015-11-11 12:08 GMT+01:00 Rowland Penny <rowlandpenny241155 at gmail.com>: > On 11/11/15 10:41, Daniel Carrasco Marín wrote: > >> Hi, first of all i'm sorry for my english. >> >> I'm trying to create a print

It's already done. I did a lot of tests, installed testing packages... and y prefer to start with a clean system. Anyway was an empty domain with only an user. I'll report how it works ;) Greetings!! El 11 nov. 2015 12:43 p. m., "Rowland Penny" <rowlandpenny241155 at gmail.com> escribió: > On 11/11/15 11:31, Daniel Carrasco Marín wrote: > >> Thanks to both

Hi, first of all i'm sorry for my english. I'm trying to create a print server in the same server that has the samba AD but i cannot make it work. For now i've: - A working AD server with Samba 4.2.5 - A Cups server with the print drivers - GPO policies to install the printers in the client computer All works perfect and even i can send test pages from cups, but i cannot

My samba shares aren't working with ACL access since the upgrade. Here is an example of the error from /var/log/messages Dec 14 12:44:17 gfm-atlas smbd[14365]: [2006/12/14 12:44:17, 0] smbd/service.c:make_connection_snum(911) Dec 14 12:44:17 gfm-atlas smbd[14365]: '/usr/GFM_Shares/Users/Receiving' does not exist or permission denied when connecting to [GF_Receiving] Error was

On Tue, 9 May 2017 11:00:09 -0400 Robert Kudyba via samba <samba at lists.samba.org> wrote: > Running Feora 25 workstation we're able to register the computer in > AD but I can't get SSH to authenticate properly. wbinfo -u brings > back all the users. Just getting "Permission denied, please try > again." Below are key settings in related conf files. > >

Hello everyone, I use winbind against a Samba DC for nsswich, and on one client it works perfectly (Samba 3.5.15 on all systems). On another client, everything works except SID_TO_UID (i.e. wbinfo -i, -S ... which breaks directory listings, too). I've now tried to narrow down the problem in a level 10 log, but I need some help interpreting. In log.winbindd, I see the following when

Good Morning, Ive been trying to test Samba AD on Ubuntu 18.04 using samba version 4.8.0  The DC seems to be working fine all tests have passed.  I was able to connect Win7 RSAT, a Ubuntu workstation and a File server.  My problem is the file server will not give response to 'sudo getent passwd' with or with out username or DOMAIN\username. Everything else works as far as I can tell.

Hello We are trying to implement SSO with mod_auth_ntlm_winbind. We followed the instructions on [1], but have the issue that users can not authenticate with web browsers. In addition to that document we did the following extra steps: - chown root:winbind /var/lib/samba/winbindd_privileged/ - apache user (vagrant) is in group winbind - net setauthuser -U vagrant - smb.conf has: winbind use

Running Feora 25 workstation we're able to register the computer in AD but I can't get SSH to authenticate properly. wbinfo -u brings back all the users. Just getting "Permission denied, please try again." Below are key settings in related conf files. rpm -q samba samba-4.5.8-1.fc25.x86_64 winbindd -V Version 4.5.8 /etc/nsswitch.conf: passwd: files winbind shadow:

> On May 9, 2017, at 11:15 AM, Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Tue, 9 May 2017 11:00:09 -0400 > Robert Kudyba via samba <samba at lists.samba.org> wrote: > >> Running Feora 25 workstation we're able to register the computer in >> AD but I can't get SSH to authenticate properly. wbinfo -u brings >> back all the

Hello all. After last update (from winbind-3.5.3 and krb5-1.8.1 to winbind-3.5.10 and krb5-1.9.1) users from a trusted domain can't authenticate any more. Machines are joined to domain PERSONALE, and users from domain STUDENTI aren't recognized. Domains are handled by W2k8 or W2k8r2 (I have no control on these). Last lines from /var/log/samba/log.wb-STUDENTI report: [2012/02/23