similar to: authenticating using winbindd against NT4 domain fails

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

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

I am running a very mixed network, Linux, win nt4 servers OS X, Linux, Win 98SE, 2k, & XP clients just added a new ubuntu server running samba 3.0.22. (new server a replacement for an old NT4 server) NT 4 is PDC Everything was mostly fine for about a month, then started getting errors logging into shares. At first I could fix this by restarting winbind, but then came times when I was

Been working with Samba back to 1.9 or so, but this is the first time I've tried to set it up as a domain member server. I followed (I think) the instructions on how to do this in TOSHARG (which are about as disjointed as the book, which I took back), but I continue to be unable to get the box, running winbind, to reliably authenticate users off the PDC, which is running NT4 (and I'm not

I have Samba server joined to NT domain. My previous version was 3.0.12. It worked fine. But after upgrade to 3.0.22 (FreeBSD 5.3) smbd fails during startup. I see following messages at /var/log/messages: May 22 08:46:07 ws170101 smbd[537]: [2006/05/22 08:46:07, 0] smbd/server.c:main(829) May 22 08:46:07 ws170101 smbd[537]: ERROR: failed to setup guest info. May 22 08:46:08 ws170101

Hello. I can not enter the domain machine: net rpc join -S 192.168.128.10 -U user cli_rpc_pipe_open_noauth: rpc_pipe_bind for pipe \lsarpc failed with error NT_STATUS_UNSUCCESSFUL Could not initialise lsa pipe Enter root's password: cli_rpc_pipe_open_noauth: rpc_pipe_bind for pipe \lsarpc failed with error NT_STATUS_UNSUCCESSFUL Error connecting to LSA pipe. Error was NT_STATUS_UNSUCCESSFUL

Hello, For some time now have been trying to connect a Samba-3.0.14a-0.4 server running on SuSE Ent 9 linux server to our Exchange 2003 (running on Server 2003 Std w/ SP1) server which is also the AD server for our domain. I can connect to the shares using the AD as the authentication source, so the basic functionality is there but some command output does not show in the way i expect

Have been running samba successfully authenticating to a windows 2003 domain since 3.0.1. Starting in 3.0.23 and 3.0.23b I can't do a "net ads join" on a HPUX itanium server running 11.23 ia64. I can kinit just fine w/ this userid. Samba was built with gcc 4.1.1. See below: root@serv00 # kinit jjurich_wa Password for jjurich_wa@DIVMS.UIOWA.EDU: root@serv00 #

Hello List I'm running Samba 3.0.24,1 on a freebsd 6 server I've joined the unix server to an active directory domain and set up PAM I've shared directories and users can access them (provided they belong to the correct group) the problem is : if I list the shared directory mail# /usr/local/lib > ls -al /usr/local/www/www.dmsware.it/ total 6 drwxr-xr-x 3 root wheel 512 Apr

Am 26.02.19 um 12:26 schrieb Ralph Böhme: > On Tue, Feb 26, 2019 at 11:19:45AM +0100, Alexander Spannagel via samba > wrote: >> The huge delays are seen, when user isn't known to sssd and winbind >> tries to look that user without explicitly a domain given and the >> option "winbind use default domain" is on it's default of "No" in >>

Hi We have a few Linux samba servers that authenticate against our Active Directory domain (Small Business Server 2000). I've added a couple of disks to a FreeBSD 6.1 server in our office and I'm trying to achieve the same but not having much luck. I'm new to all this... I'm not our network admin, but he is BSD-phobic so I thought it was safer to do it myself.

Hello list. The issue I have is that with the changes made to the idmap functionality of winbind, as regards the enumeration of rfc2307 users and groups using getent passwd and getent group, only those AD users that are not in the domains included in the "idmap config (domain)" statements (the ones in trusted domains that get their ID mappings auto-assigned by the TDB backend with

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.

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

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

Hello, There is FreeBSD-6.1 box with gcc 3.4.4 compiler (the default). The box is a member of an ADS domain. Everything was working perfectly with samba-3.0.22. After upgrading it to samba-3.0.23_1 from FreeBSD ports collection, the following problem appeared. The system does not seem to recognize that a user is a member of some domain group, and does not grant him appropriate permissions. For

I posted my original post to FreeBSD-questions@freebsd.org and since then have had a running dialog with another poster. It now seems I am having trouble with the NSSWITCH function. I am now reporting back to the Samba list in hopes someone can help me out at this point. Can anyone help me out here? ~Doug -----Original Message----- Sent: Friday, September 16, 2005 12:48 PM To: 'Dan

I portupgraded my samba domain server and domain member to 3.0.23b from 3.0.23 and found that the domain member was not accessible from workstations. The error message: \\HOSTNAME is not accessible. There are currently no logon servers available to service the logon request. In the log.winbindd of the domain member, I found: [2006/08/23 22:52:00, 0] nsswitch/winbindd.c:request_len_recv(517)

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