similar to: NT_STATUS_INVALID_HANDLE

I may have a solution to this problem but would like any advice on the downside of doing this. Essentially, I remove role check in nmbd.c as follows: --- samba-4.1.13.orig/source3/nmbd/nmbd.c +++ samba-4.1.13/source3/nmbd/nmbd.c @@ -914,16 +914,6 @@ static bool open_sockets(bool isdaemon, reopen_logs(); - if (lp_server_role() == ROLE_ACTIVE_DIRECTORY_DC - && !lp_parm_bool(-1,

Dear All, i've finally succes to add my samba server to join my active directory. when i execute command #wbinfo -u and #wbinfo -g its show user and group in active directory but when i try use #getent passwd or #pw show user -a (well i'm using FreeBSD machine) it's only show user on FreeBSD machine, the users in active directory not show up. anyone can explain why its happen? when i

Hello, upgraded to Samba 3.2.6, and immediately printing went into coma. Observed that printers lose their configurations (driver models, locations, etc). And if I reset the printer drivers on each share, eventually they will be lost again. Looking at the logs we are getting panics like this: --- [2008/12/16 05:12:51, 0] lib/util_tdb.c:tdb_log(682) tdb(/var/lib/samba/printing/CanonC1.tdb):

Hi guys I have a problem with Samba 4.0 shares covered by scannedonly VFS. Example configuration of one of those shares: path = /foo/bar/baz read only = No browseable = No vfs objects = scannedonly scannedonly:domain_socket = True scannedonly:socketname = /var/lib/scannedonly/scan scannedonly:hide_nonscanned_files = True scannedonly:allow_nonscanned_files = False Whenever I

When I try to establish a trust from SAMBA 3.0.11 to Windows 2003 I get the error: NT_STATUS_INVALID_HANDLE. I have no problem the other way. I had no problem either, when I ran SAMBA 3.0.9, and the problem disappeared when I down-graded to 3.0.9. Here is what happens ('CALYPSO' is the Windows-server and 'KONTOR' is its domain-name): [root@linux /root]# net rpc trustdom

I should use an authenticated proxy with Squid, but I have a problem with winbind. I'm working on a PDC, debian squeeze with samba from backport (ver. 2:3.5.11~dfsg-1~bpo60+1 ) Here the problem: I can authenticate users. /usr/bin/ntlm_auth --username=myname --domain=MYCOMPANY password: XXXX NT_STATUS_INVALID_HANDLE: Invalid handle (0xc0000008) wbinfo -a myname Enter myname's

I'm trying to setup a FreeRADIUS (version 1.1.6 w/ LDAP support) server on our new server here at home, which in turn should authenticate against the Samba server (also on the same host - version 3.0.25) which in turn uses an OpenLDAP server (CVS version HEAD as of 20070719). Samba works perfectly against the OL server. Authentication etc is a-ok. But regarding winbind, the first problem is

I've been stuck on this one for days and can't seem to find anything referencing the same problem; help would be greatly appreciated. I have a functioning Samba 3.5.4-63 installation acting as a PDC - users can log in from Windows 7 machines without problems etc. etc. The issue is with using wbinfo -a to authenticate users (without going into too much detail, I'm trying to use the

smbclient/mount.cifs stopped working when connecting to a Windows 7 server. The Windows machine is not part of a domain and smbclient is authenticating with one of its local accounts. Upon uninstalling the January Windows security patch (KB4480970) from the server, everything works again. The tests below are with a custom compiled copy of the latest smbclient (4.9.4) for troubleshooting purposes

On 05/17/12 11:15, prabu.murugan at emc.com wrote: > > Hi, > > As a security concern we are upgrading samba to 3.4.17. > > I tried all possible option to compile samba 3.4.17 on Solaris 10_U10. > But it is not going through. > > > > User requirement is to compile samba 3.4.17 to support their > application. 3.4.17 is working on Solaris 9 and Solaris 10_U5. But

I'm try-ing on samba-2.2.x and samba-3.x, with tls or ssl support but didn't work and my machine says "Failed to issue the StartTLS instruction: Connect error" and this my conf : ldap admin dn = "cn=root,dc=langitan" ldap server = 127.0.0.1 ldap suffix = "dc=langitan" ldap port = 389 ldap ssl = start tls with compile options : ./configure \