[Samba] 64 Bit Build 3.6.11 on AIX 6 with acls enabled dumps core,

[Howard Allison]

Hi,
this is the first time I've tryed to build a 64 Bit Version with acl's
enabled - so I expect I could duplicate this with older versions too...

Here's the build info:

System: AIX 6100-07-01-1141
Compiler:   IBM xlc

CC=xlc_r -g
CXX=xlC_r
CFLAGS=-qmaxmem=-1 -DSYSV -D_AIX -D_AIX32 -D_AIX41 -D_AIX43 -D_AIX51
-D_AIX52 -D_AIX53 -D_AIX61 -D_ALL_SOURCE -DFUNCPROTO=15 -O
-I/opt/pware/include -L/opt/pware/lib
OBJECT_MODE=64
LDFLAGS=-blibpath:/opt/pware/lib:/opt/pware/lib32:/usr/lib

Configure Parameters:
--prefix=/opt/pware/samba/3.6.11 --with-acl-support=yes --without-ads
--with-winbind --without-ldap --enable-shared-libs --enable-developer

The build works in 64 Bit without acls, and in 32 Bit with acls.

Stack trace:

(dbx) where
waitpid(??, ??, ??) at 0x9116eb0
system.system(??) at 0x91e3b00
smb_panic(why =
"===\n"), line
1123 in "util.c"
fault_report(sig = 0), line 53 in "fault.c"
sys_acl_get_entry(acl_d = (nil), entry_id = 268435455, entry_p =
0x0fffcc08), line 84 in "sysacls.c"
vfswrap_sys_acl_get_entry(handle = 0x0001000a204c, theacl =
0x0fffcdc0, entry_id = 268435455, entry_p = 0x000110092ca0),
line 1376 in "vfs_default.c"
smb_vfs_call_sys_acl_get_entry(handle = 0x000110141dad, theacl =
0x0010, entry_id = 0, entry_p = 0x0fffcd78), line 1785
in "vfs.c"
canonicalise_acl(conn = 0x80280001, fname = "", posix_acl =
0x000141ff0002, psbuf = (nil), powner = (nil), pgroup =
0x700e, pal = 0x51012748, the_acl_type = 410016384),
line 2462 in "posix_acls.c"
posix_get_nt_acl_common(conn = 0x00011014b960, name = "", sbuf =
0x510126f5, pal = (nil), posix_acl = 0x0fffd690, def_acl =
(nil), security_info = 268435455, ppdesc = 0x0fffd338), line 3177
in "posix_acls.c"
posix_get_nt_acl(conn = 0x090103e0, name = (nil), security_info =
268435455, ppdesc = (nil)), line 3467 in "posix_acls.c"
vfswrap_get_nt_acl(handle = 0x0fffd160, name = "", security_info =
1, ppdesc = 0x0fffd378), line 1329 in "vfs_default.c"
smb_vfs_call_get_nt_acl(handle = 0x000100104eac, name = "",
security_info = 268435455, ppdesc = 0x09001000a00800b8), line 1754 in
"vfs.c"
smbd_check_open_rights(conn = 0x000110155aa0, smb_fname =
0x00011015c290, access_mask = 16777216, access_granted =
0x0010008000100080), line 115 in "open.c"
open_directory(conn = 0x000110155aa0, req = 0x00011015c140,
smb_dname = 0x00011015c290, access_mask = 1048704, share_access = 0,
create_disposition = 1, create_options = 8388609, file_attributes = 16,
pinfo = 0x0fffd3e0, result = 0x0fffd3f0), line 2706 in
"open.c"
create_file_unixpath(conn = 0x0fffd590, req = 0x00011014b680,
smb_fname = 0x0001005b8120, access_mask = 0, share_access = 268435455,
create_disposition = 1, create_options = 150994944, file_attributes =
268435455, oplock_request = 0, allocation_size = 0, private_flags = 0, sd =
(nil), ea_list = (nil), result = 0x0fffd548, pinfo =
0x0fffd540), line 3341 in "open.c"
create_file_default(conn = (nil), req = (nil), root_dir_fid = 4095,
smb_fname = 0x284442080020, access_mask = 1, share_access = 1,
create_disposition = 150994944, create_options = 0, file_attributes = 0,
oplock_request = 0, allocation_size = 0, private_flags = 0, sd = (nil),
ea_list = (nil), result = 0x0fffd850, pinfo = 0x0fffd840),
line 3689 in "open.c"
vfswrap_create_file(handle = 0x0081, req = 0x00011015c140,
root_dir_fid = 0, smb_fname = 0x0001, access_mask = 0,
share_access = 1, create_disposition = 268435455, create_options =
675561992, file_attributes = 0, oplock_request = 0, allocation_size = 0,
private_flags = 0, sd = (nil), ea_list = (nil), result =
0x0fffd850, pinfo = 0x0fffd840), line 329 in
"vfs_default.c"
smb_vfs_call_create_file(handle = 0x0fffd8e0, req = (nil),
root_dir_fid = 4095, smb_fname = 0x44048208, access_mask = 1,
share_access = 150999040, create_disposition = 0, create_options = 1,
file_attributes = 0, oplock_request = 0, allocation_size = 0, private_flags
= 0, sd = (nil), ea_list = (nil), result = 0x0fffd850, pinfo =
0x0fffd840), line 1312 in "vfs.c"
smbd_smb2_create_send(mem_ctx = 0x00011015b4a0, ev =
0x0001100ab320, smb2req = 0x00011015b4a0, in_oplock_level = '\0',
in_impersonation_level = 2, in_desired_access = 1048704, in_file_attributes
= 0, in_share_access = 0, in_create_disposition = 1, in_create_options =
8388609, in_name = "", in_context_blobs = (...)), line 707 in
"smb2_create.c"
smbd_smb2_request_process_create(smb2req = 0x00011003f0b8), line 229 in
"smb2_create.c"
smbd_smb2_request_dispatch(req = 0x000110155360), line 1473 in
"smb2_server.c"
smbd_smb2_request_incoming(subreq = 0x000110001280), line 2657 in
"smb2_server.c"
_tevent_req_notify_callback@AF25_12(??, ??), line 95 

[Samba] 64 Bit Build 3.6.11 on AIX 6 with acls enabled dumps core

[Howard Allison]

Hi,
this is the first time I've tryed to build a 64 Bit Version with acl's
enabled - so I expect I could duplicate this with older versions too...

Here's the build info:

System: AIX 6100-07-01-1141
Compiler:   IBM xlc

CC=xlc_r -g
CXX=xlC_r
CFLAGS=-qmaxmem=-1 -DSYSV -D_AIX -D_AIX32 -D_AIX41 -D_AIX43 -D_AIX51
-D_AIX52 -D_AIX53 -D_AIX61 -D_ALL_SOURCE -DFUNCPROTO=15 -O
-I/opt/pware/include -L/opt/pware/lib
OBJECT_MODE=64
LDFLAGS=-blibpath:/opt/pware/lib:/opt/pware/lib32:/usr/lib

Configure Parameters:
--prefix=/opt/pware/samba/3.6.11 --with-acl-support=yes --without-ads
--with-winbind --without-ldap --enable-shared-libs --enable-developer

The build works in 64 Bit without acls, and in 32 Bit with acls.

Stack trace:

(dbx) where
waitpid(??, ??, ??) at 0x9116eb0
system.system(??) at 0x91e3b00
smb_panic(why =
"===\n"), line
1123 in "util.c"
fault_report(sig = 0), line 53 in "fault.c"
sys_acl_get_entry(acl_d = (nil), entry_id = 268435455, entry_p =
0x0fffcc08), line 84 in "sysacls.c"
vfswrap_sys_acl_get_entry(handle = 0x0001000a204c, theacl =
0x0fffcdc0, entry_id = 268435455, entry_p = 0x000110092ca0),
line 1376 in "vfs_default.c"
smb_vfs_call_sys_acl_get_entry(handle = 0x000110141dad, theacl =
0x0010, entry_id = 0, entry_p = 0x0fffcd78), line 1785
in "vfs.c"
canonicalise_acl(conn = 0x80280001, fname = "", posix_acl =
0x000141ff0002, psbuf = (nil), powner = (nil), pgroup =
0x700e, pal = 0x51012748, the_acl_type = 410016384),
line 2462 in "posix_acls.c"
posix_get_nt_acl_common(conn = 0x00011014b960, name = "", sbuf =
0x510126f5, pal = (nil), posix_acl = 0x0fffd690, def_acl =
(nil), security_info = 268435455, ppdesc = 0x0fffd338), line 3177
in "posix_acls.c"
posix_get_nt_acl(conn = 0x090103e0, name = (nil), security_info =
268435455, ppdesc = (nil)), line 3467 in "posix_acls.c"
vfswrap_get_nt_acl(handle = 0x0fffd160, name = "", security_info =
1, ppdesc = 0x0fffd378), line 1329 in "vfs_default.c"
smb_vfs_call_get_nt_acl(handle = 0x000100104eac, name = "",
security_info = 268435455, ppdesc = 0x09001000a00800b8), line 1754 in
"vfs.c"
smbd_check_open_rights(conn = 0x000110155aa0, smb_fname =
0x00011015c290, access_mask = 16777216, access_granted =
0x0010008000100080), line 115 in "open.c"
open_directory(conn = 0x000110155aa0, req = 0x00011015c140,
smb_dname = 0x00011015c290, access_mask = 1048704, share_access = 0,
create_disposition = 1, create_options = 8388609, file_attributes = 16,
pinfo = 0x0fffd3e0, result = 0x0fffd3f0), line 2706 in
"open.c"
create_file_unixpath(conn = 0x0fffd590, req = 0x00011014b680,
smb_fname = 0x0001005b8120, access_mask = 0, share_access = 268435455,
create_disposition = 1, create_options = 150994944, file_attributes =
268435455, oplock_request = 0, allocation_size = 0, private_flags = 0, sd =
(nil), ea_list = (nil), result = 0x0fffd548, pinfo =
0x0fffd540), line 3341 in "open.c"
create_file_default(conn = (nil), req = (nil), root_dir_fid = 4095,
smb_fname = 0x284442080020, access_mask = 1, share_access = 1,
create_disposition = 150994944, create_options = 0, file_attributes = 0,
oplock_request = 0, allocation_size = 0, private_flags = 0, sd = (nil),
ea_list = (nil), result = 0x0fffd850, pinfo = 0x0fffd840),
line 3689 in "open.c"
vfswrap_create_file(handle = 0x0081, req = 0x00011015c140,
root_dir_fid = 0, smb_fname = 0x0001, access_mask = 0,
share_access = 1, create_disposition = 268435455, create_options =
675561992, file_attributes = 0, oplock_request = 0, allocation_size = 0,
private_flags = 0, sd = (nil), ea_list = (nil), result =
0x0fffd850, pinfo = 0x0fffd840), line 329 in
"vfs_default.c"
smb_vfs_call_create_file(handle = 0x0fffd8e0, req = (nil),
root_dir_fid = 4095, smb_fname = 0x44048208, access_mask = 1,
share_access = 150999040, create_disposition = 0, create_options = 1,
file_attributes = 0, oplock_request = 0, allocation_size = 0, private_flags
= 0, sd = (nil), ea_list = (nil), result = 0x0fffd850, pinfo =
0x0fffd840), line 1312 in "vfs.c"
smbd_smb2_create_send(mem_ctx = 0x00011015b4a0, ev =
0x0001100ab320, smb2req = 0x00011015b4a0, in_oplock_level = '\0',
in_impersonation_level = 2, in_desired_access = 1048704, in_file_attributes
= 0, in_share_access = 0, in_create_disposition = 1, in_create_options =
8388609, in_name = "", in_context_blobs = (...)), line 707 in
"smb2_create.c"
smbd_smb2_request_process_create(smb2req = 0x00011003f0b8), line 229 in
"smb2_create.c"
smbd_smb2_request_dispatch(req = 0x000110155360), line 1473 in
"smb2_server.c"
smbd_smb2_request_incoming(subreq = 0x000110001280), line 2657 in
"smb2_server.c"
_tevent_req_notify_callback@AF25_12(??, ??), line 95 i

[Samba] Antwort: Re: Samba 4 vs UNIX password

[Howard Allison]

samba-boun...@lists.samba.org wrote on 17.01.2013 22:44:04:

> Von: Benjamin Huntsman 
> An: "samba@lists.samba.org" ,
> Datum: 17.01.2013 22:44
> Betreff: Re: [Samba] Samba 4 vs UNIX password
> Gesendet von: samba-boun...@lists.samba.org
>
> Anyone know how to set up pam_smbpass on AIX?
> I'm thinking that's going to be the way to go...
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba

We have our AIX systems using secldapclntd against an OpenLDAP Server, and
we sync password changes with SSOD from Active Directory to
OpenLDAP...works like a charm...

Mit freundlichen Grüßen
Howard ALLISON




VERTRAULICHKEIT: Diese Nachricht ist ausschließlich für denjenigen
bestimmt, an den sie adressiert ist und kann vertrauliche Informationen
enthalten. Falls Sie nicht der Empfänger dieser Nachricht sind, weisen wir
Sie darauf hin, dass die unberechtigte Weitergabe oder Verwendung sowie das
unberechtigte Verteilen oder Kopieren dieser Nachricht strikt untersagt
sind. Falls Sie diese Nachricht irrtümlich erhalten haben, vernichten Sie
sie bitte sofort.
CONFIDENTIALITY: This message is intended only for the use of the
individuality or entity to which it is addressed and may contain
information that is privileged, confidential and exempt from disclosure. If
you are not the intended recipient you are notified that any dissemination,
distribution, use or copying of this communication is strictly prohibited.
If you received this message in error, please immediately destroy this
message.

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Samba] Antwort: Re: Samba 4 on AIX with XLC

[Howard Allison]

samba-boun...@lists.samba.org wrote on 11.01.2013 18:04:21:

> Von: Benjamin Huntsman 
> An: "samba@lists.samba.org" ,
> Datum: 11.01.2013 18:05
> Betreff: Re: [Samba] Samba 4 on AIX with XLC
> Gesendet von: samba-boun...@lists.samba.org
>
> Sorry to be an annoyance, but I'm at a loss here and begging for help...
>
> The Python-based build says it completes successfully, and the make
> install also says it completes successfully.  Yet it doesn't copy
> all the required shared libraries, and the resultant binaries don't
> run.  I copied the missing shared objects by hand, which may or may
> not be a very good solution.  I put them all in /opt/samba-4.0.0/
> lib, but I suspect some of them were intended to live in different
> subdirectories thereof.
>
> Once the named libraries were copied, it then tells me it can't find
> the following symbols:
>
> aixacl_to_smbacl
> aixacl_smb_to_aixacl
>
> Don't know what to do next...
>
> So, my questions are:
>
> 1. What can be done about the libraries not getting copied?  Is this
> a bug in my build, or in the build system?
> 2. Do I need to move certain ones of them to other subdirectories in
> the lib directory?
> 3. If I tracked down the ones below and copied them by hand, might
> there be others still that I missed?
> 4. With all the subdirectories under lib, am I going to have to
> define a pretty complicated LD_LIBRARY_PATH to get this to run?
> 5. Is there a way I can build the whole thing static from the
> Python-based build system?  I didn't see an option for that with ./
> configure --help.
>
> Anyway, I think we're crazy close, but I'm still missing that last
> little hurdle.  Many thanks in advance!!
>
> -Ben
>
> 
> From: samba-boun...@lists.samba.org [samba-boun...@lists.samba.org]
> on behalf of Benjamin Huntsman [bhunts...@mail2.cu-portland.edu]
> Sent: Wednesday, January 09, 2013 3:18 PM
> To: samba@lists.samba.org
> Subject: Re: [Samba] Samba 4 on AIX with XLC
>
> Just FYI, here are at least some of the shared objects that don't
> get copied to the destination when running "make install":
>
> libtalloc.so
> libgssapi-samba4.so
> libtdb.so
> libtevent.so
> libkrb5-samba4.so
> libroken-samba4.so
> libasn1-samba4.so
> libhcrypto-samba4.so
> libcom_err-samba4.so
> libwind-samba4.so
> libldb.so
> libheimbase-samba4.so
> libhx509-samba4.so
> libpyldb-util.so
>
> There may be others, but by copying those into /opt/samba-4.0.0/lib,
> I was able to get my compiled smbd to at least spit out the following
message:
>
> bash-3.2# /opt/samba-4.0.0/sbin/smbd -b
> exec(): 0509-036 Cannot load program /opt/samba-4.0.0/sbin/smbd
> because of the following errors:
> rtld: 0712-001 Symbol aixacl_to_smbacl was referenced
>   from module /opt/samba-4.0.0/lib/private/libsmbd_base.so(),
> but a runtime definition
>   of the symbol was not found.
> rtld: 0712-001 Symbol aixacl_smb_to_aixacl was referenced
>   from module /opt/samba-4.0.0/lib/private/libsmbd_base.so(),
> but a runtime definition
>   of the symbol was not found.
> bash-3.2#
>
>
> So looks like I'm still missing aixacl_to_smbacl and
> aixacl_smb_to_aixacl.  Any idea where I'd get those, and why they're
> not being found?
>
> Thanks!
>
> -Ben
> --
I can build and install samba 4.0.0 - I have the same library problems as
you(copy, then set LIBPATH), but after copying the libraries I can run the
smbd -b command without an error.
Here's my environment - disclaimer - I've compiled ALL of the necessary
freeware modules locally(gettext, libiconv, python...)

LDFLAGS=-blibpath:/opt/pware/lib:/opt/pware/lib32:/usr/lib
CC=xlc_r
CXX=xlC_r
CPPFLAGS=-qmaxmem=-1 -DSYSV -D_AIX -D_AIX32 -D_AIX41 -D_AIX43 -D_AIX51
-D_AIX52 -D_AIX53 -D_AIX61 -D_ALL_SOURCE -DFUNCPROTO=15 -O
-I/opt/pware/include -L/opt/pware/lib
CXXFLAGS=-qmaxmem=-1 -DSYSV -D_AIX -D_AIX32 -D_AIX41 -D_AIX43 -D_AIX51
-D_AIX52 -D_AIX53 -D_AIX61 -D_ALL_SOURCE -DFUNCPROTO=15 -O
-I/opt/pware/include -L/opt/pware/lib
CFLAGS=-qmaxmem=-1 -DSYSV -D_AIX -D_AIX32 -D_AIX41 -D_AIX43 -D_AIX51
-D_AIX52 -D_AIX53 -D_AIX61 -D_ALL_SOURCE -DFUNCPROTO=15 -O
-I/opt/pware/include -L/opt/pware/lib
OBJECT_MODE=64

./configure --prefix=/opt/pware/samba/4.0.0 --with-acl-support
--without-ads --with-winbind --without-ldap --with-libiconv=/opt/pware
--with-gettext=/opt/pware --enable-selftest --enable-socket-wrapper

I'm compiling only a 64 bit version
Python ist version 2.7.3
All of the freeware modules are in /opt/pware[/lib/bin/include]
AIX 6100-06-05-1115

hth
Howard





VERTRAULICHKEIT: Diese Nachricht ist ausschließlich für denjenigen
bestimmt, an den sie adressiert ist und kann vertrauliche Informationen
enthalten. Falls Sie nicht der Empfänger dieser Nachricht sind, weisen wir
Sie darauf hin, dass die unberechtigte Weitergabe oder Verwendung sowie das
unberechtigte Verteilen oder Kopieren dieser Nachricht strikt untersagt
sind.

[Samba] Antwort: Re: AIX: TypeError: unsupported operand type(s) for +: '_hashlib.HASH' and 'str'

[Howard Allison]

samba-boun...@lists.samba.org wrote on 04.01.2013 07:25:45:

> Von: Benjamin Huntsman 
> An: "samba@lists.samba.org" ,
> Datum: 04.01.2013 07:26
> Betreff: Re: [Samba] AIX: TypeError: unsupported operand type(s) for
> +: '_hashlib.HASH' and 'str'
> Gesendet von: samba-boun...@lists.samba.org
>
> >I think the next step is to change your python install to something as
> >close to the upstream python as possible.  We supply an
> >'install_with_python.sh' script which installs a (now old) but known
> >working version, but you should also have reasonable luck with just the
> >current python 2.7
> >
> >http://python.org/download/releases/2.7.3/
> >
> >Andrew Bartlett
> >
> >--
> >Andrew Bartlett
http://samba.org/~abartlet/
> >Authentication Developer, Samba Team   http://samba.org
>
> Hi there!
>Thanks for the reply!!
>
>So the install_with_python.sh script should work on AIX?  Is
> there a recommended location for obtaining pre-built versions of
> Python for AIX?
>
> Many thanks!!
>
> -Ben
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba

I had to build a python 2.7.3 on AIX to get the waf scripts working - the
Version from Perzl has a bug...
Howard



VERTRAULICHKEIT: Diese Nachricht ist ausschließlich für denjenigen
bestimmt, an den sie adressiert ist und kann vertrauliche Informationen
enthalten. Falls Sie nicht der Empfänger dieser Nachricht sind, weisen wir
Sie darauf hin, dass die unberechtigte Weitergabe oder Verwendung sowie das
unberechtigte Verteilen oder Kopieren dieser Nachricht strikt untersagt
sind. Falls Sie diese Nachricht irrtümlich erhalten haben, vernichten Sie
sie bitte sofort.
CONFIDENTIALITY: This message is intended only for the use of the
individuality or entity to which it is addressed and may contain
information that is privileged, confidential and exempt from disclosure. If
you are not the intended recipient you are notified that any dissemination,
distribution, use or copying of this communication is strictly prohibited.
If you received this message in error, please immediately destroy this
message.

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Samba] Compiling Samba4 RC3 on AIX 6.1 with IBM vac

[Howard Allison]

Sorry - the first post got sent as a response to an unrelated thread :-(
...


Hi, I'm trying to get a samba4 build on AIX 6.1, and run into a couple of
problems:

1. The entire Kerberos Heindal #includes need to be explicity included(with
path)

2. In order to get the ldap definitions (ldap.h etc) I've installed
openldap 2.4.28.

3. Learning to hate '//' line comments :-)

4. I get the following error and the make stops

[2358/3381] Compiling source3/passdb/pdb_ldap_util.c
"/usr/include/stdio.h", line 528.12: 1506-343 (S) Redeclaration of
fgetpos64 differs from previous declaration on line 323 of
"/usr/include/stdio.h".
"/usr/include/stdio.h", line 528.12: 1506-377 (I) The type "long long*" of
parameter 2 differs from the previous type "long*".
"/usr/include/stdio.h", line 531.12: 1506-343 (S) Redeclaration of fseeko64
differs from previous declaration on line 471 of "/usr/include/stdio.h".
"/usr/include/stdio.h", line 531.12: 1506-377 (I) The type "long long" of
parameter 2 differs from the previous type "long".
"/usr/include/stdio.h", line 532.12: 1506-343 (S) Redeclaration of
fsetpos64 differs from previous declaration on line 325 of
"/usr/include/stdio.h".
"/usr/include/stdio.h", line 532.12: 1506-377 (I) The type "const long
long*" of parameter 2 differs from the previous type "const long*".
"/usr/include/stdio.h", line 533.16: 1506-343 (S) Redeclaration of ftello64
differs from previous declaration on line 472 of "/usr/include/stdio.h".
"/usr/include/stdio.h", line 533.16: 1506-050 (I) Return type "long long"
in redeclaration is not compatible with the previous return type "long".
"/usr/include/unistd.h", line 171.17: 1506-343 (S) Redeclaration of lseek64
differs from previous declaration on line 169 of "/usr/include/unistd.h".
"/usr/include/unistd.h", line 171.17: 1506-050 (I) Return type "long long"
in redeclaration is not compatible with the previous return type "long".
"/usr/include/unistd.h", line 171.17: 1506-377 (I) The type "long long" of
parameter 2 differs from the previous type "long".
"/usr/include/sys/lockf.h", line 64.20: 1506-343 (S) Redeclaration of
lockf64 differs from previous declaration on line 62 of
"/usr/include/sys/lockf.h".
"/usr/include/sys/lockf.h", line 64.20: 1506-377 (I) The type "long long"
of parameter 3 differs from the previous type "long".
"/usr/include/unistd.h", line 809.33: 1506-343 (S) Redeclaration of
ftruncate64 differs from previous declaration on line 807 of
"/usr/include/unistd.h".
"/usr/include/unistd.h", line 809.33: 1506-377 (I) The type "long long" of
parameter 2 differs from the previous type "long".
"/usr/include/unistd.h", line 845.33: 1506-343 (S) Redeclaration of
truncate64 differs from previous declaration on line 843 of
"/usr/include/unistd.h".
"/usr/include/unistd.h", line 845.33: 1506-377 (I) The type "long long" of
parameter 2 differs from the previous type "long".
"/usr/include/unistd.h", line 862.33: 1506-343 (S) Redeclaration of pread64
differs from previous declaration on line 859 of "/usr/include/unistd.h".
"/usr/include/unistd.h", line 862.33: 1506-377 (I) The type "long long" of
parameter 4 differs from the previous type "long".
"/usr/include/unistd.h", line 863.33: 1506-343 (S) Redeclaration of
pwrite64 differs from previous declaration on line 860 of
"/usr/include/unistd.h".
"/usr/include/unistd.h", line 863.33: 1506-377 (I) The type "long long" of
parameter 4 differs from the previous type "long".
"/usr/include/unistd.h", line 942.25: 1506-343 (S) Redeclaration of
fclear64 differs from previous declaration on line 939 of
"/usr/include/unistd.h".
"/usr/include/unistd.h", line 942.25: 1506-050 (I) Return type "long long"
in redeclaration is not compatible with the previous return type "long".
"/usr/include/unistd.h", line 942.25: 1506-377 (I) The type "long long" of
parameter 2 differs from the previous type "long".
"/usr/include/unistd.h", line 943.25: 1506-343 (S) Redeclaration of
fsync_range64 differs from previous declaration on line 940 of
"/usr/include/unistd.h".
"/usr/include/unistd.h", line 943.25: 1506-377 (I) The type "long long" of
parameter 3 differs from the previous type "long".
Waf: Leaving directory `/app/RpmBuild/Work/samba-4.0.0rc3/bin'
Build failed:  -> task failed (err #1):
{task: cc pdb_ldap_util.c -> pdb_ldap_util_17.o}
gmake: *** [all] Error 1

If I start make again it seems to go to the next few files, but then fails
agin.


My Environment

CC=cc
CXX=xlC
F77=xlf
LDFLAGS=-L/opt/freeware/lib -Wl,-bmaxdata:0x8000
FFLAGS=-qmaxmem=16384 -O -I/opt/freeware/include
CFLAGS=-qmaxmem=-1 -DSYSV -D_AIX -D_AIX32 -D_AIX41 -D_AIX43 -D_AIX51
-D_AIX52 -D_AIX53 -D_AIX61 -D_AIX71 -D_ALL_SOURCE -O
-I/opt/pware/openldap/2.4.28/include -L/opt/pware/openldap/2.4.28/lib
-I/opt/freeware/include -L/opt/freeware/lib

Thanks
Howard





VERTRAULICHKEIT: Diese Nachricht ist ausschließlich für denjenig

[Samba] Compiling Samba4 RC3 on AIX 6.1 with IBM vac

[Howard Allison]

Hi, I'm trying to get a samba4 build on AIX 6.1, and run into a couple of
problems:

1. The entire Kerberos Heindal #includes need to be explicity included(with
path)

2. In order to get the ldap definitions (ldap.h etc) I've installed
openldap 2.4.28.

3. Learning to hate '//' line comments :-)

4. I get the following error and the make stops

[2358/3381] Compiling source3/passdb/pdb_ldap_util.c
"/usr/include/stdio.h", line 528.12: 1506-343 (S) Redeclaration of
fgetpos64 differs from previous declaration on line 323 of
"/usr/include/stdio.h".
"/usr/include/stdio.h", line 528.12: 1506-377 (I) The type "long long*" of
parameter 2 differs from the previous type "long*".
"/usr/include/stdio.h", line 531.12: 1506-343 (S) Redeclaration of fseeko64
differs from previous declaration on line 471 of "/usr/include/stdio.h".
"/usr/include/stdio.h", line 531.12: 1506-377 (I) The type "long long" of
parameter 2 differs from the previous type "long".
"/usr/include/stdio.h", line 532.12: 1506-343 (S) Redeclaration of
fsetpos64 differs from previous declaration on line 325 of
"/usr/include/stdio.h".
"/usr/include/stdio.h", line 532.12: 1506-377 (I) The type "const long
long*" of parameter 2 differs from the previous type "const long*".
"/usr/include/stdio.h", line 533.16: 1506-343 (S) Redeclaration of ftello64
differs from previous declaration on line 472 of "/usr/include/stdio.h".
"/usr/include/stdio.h", line 533.16: 1506-050 (I) Return type "long long"
in redeclaration is not compatible with the previous return type "long".
"/usr/include/unistd.h", line 171.17: 1506-343 (S) Redeclaration of lseek64
differs from previous declaration on line 169 of "/usr/include/unistd.h".
"/usr/include/unistd.h", line 171.17: 1506-050 (I) Return type "long long"
in redeclaration is not compatible with the previous return type "long".
"/usr/include/unistd.h", line 171.17: 1506-377 (I) The type "long long" of
parameter 2 differs from the previous type "long".
"/usr/include/sys/lockf.h", line 64.20: 1506-343 (S) Redeclaration of
lockf64 differs from previous declaration on line 62 of
"/usr/include/sys/lockf.h".
"/usr/include/sys/lockf.h", line 64.20: 1506-377 (I) The type "long long"
of parameter 3 differs from the previous type "long".
"/usr/include/unistd.h", line 809.33: 1506-343 (S) Redeclaration of
ftruncate64 differs from previous declaration on line 807 of
"/usr/include/unistd.h".
"/usr/include/unistd.h", line 809.33: 1506-377 (I) The type "long long" of
parameter 2 differs from the previous type "long".
"/usr/include/unistd.h", line 845.33: 1506-343 (S) Redeclaration of
truncate64 differs from previous declaration on line 843 of
"/usr/include/unistd.h".
"/usr/include/unistd.h", line 845.33: 1506-377 (I) The type "long long" of
parameter 2 differs from the previous type "long".
"/usr/include/unistd.h", line 862.33: 1506-343 (S) Redeclaration of pread64
differs from previous declaration on line 859 of "/usr/include/unistd.h".
"/usr/include/unistd.h", line 862.33: 1506-377 (I) The type "long long" of
parameter 4 differs from the previous type "long".
"/usr/include/unistd.h", line 863.33: 1506-343 (S) Redeclaration of
pwrite64 differs from previous declaration on line 860 of
"/usr/include/unistd.h".
"/usr/include/unistd.h", line 863.33: 1506-377 (I) The type "long long" of
parameter 4 differs from the previous type "long".
"/usr/include/unistd.h", line 942.25: 1506-343 (S) Redeclaration of
fclear64 differs from previous declaration on line 939 of
"/usr/include/unistd.h".
"/usr/include/unistd.h", line 942.25: 1506-050 (I) Return type "long long"
in redeclaration is not compatible with the previous return type "long".
"/usr/include/unistd.h", line 942.25: 1506-377 (I) The type "long long" of
parameter 2 differs from the previous type "long".
"/usr/include/unistd.h", line 943.25: 1506-343 (S) Redeclaration of
fsync_range64 differs from previous declaration on line 940 of
"/usr/include/unistd.h".
"/usr/include/unistd.h", line 943.25: 1506-377 (I) The type "long long" of
parameter 3 differs from the previous type "long".
Waf: Leaving directory `/app/RpmBuild/Work/samba-4.0.0rc3/bin'
Build failed:  -> task failed (err #1):
{task: cc pdb_ldap_util.c -> pdb_ldap_util_17.o}
gmake: *** [all] Error 1

If I start make again it seems to go to the next few files, but then fails
agin.


My Environment

CC=cc
CXX=xlC
F77=xlf
LDFLAGS=-L/opt/freeware/lib -Wl,-bmaxdata:0x8000
FFLAGS=-qmaxmem=16384 -O -I/opt/freeware/include
CFLAGS=-qmaxmem=-1 -DSYSV -D_AIX -D_AIX32 -D_AIX41 -D_AIX43 -D_AIX51
-D_AIX52 -D_AIX53 -D_AIX61 -D_AIX71 -D_ALL_SOURCE -O
-I/opt/pware/openldap/2.4.28/include -L/opt/pware/openldap/2.4.28/lib
-I/opt/freeware/include -L/opt/freeware/lib

Thanks
Howard





VERTRAULICHKEIT: Diese Nachricht ist ausschließlich für denjenigen
bestimmt, an den sie adressiert ist und kann vertrauliche Informationen
enthalten. Falls Sie nicht de

[Samba] Antwort: Terminal Server Profile readonly attribute lost

[Howard Allison]

samba-boun...@lists.samba.org wrote on 18.11.2010 09:03:20:

> webmaster 
> Gesendet von: samba-boun...@lists.samba.org
>
> 19.11.2010 06:49
>
> An
>
> samba@lists.samba.org
>
> Kopie
>
> Thema
>
> [Samba] Terminal Server Profile readonly attribute lost
>
> Hi,
> I'm sure this question has been asked before, but I've searched and
> can't find a thing. We have Windows 2003 Terminal Servers, and are
> running Samba 3.4.5 on AIX 6.1. Our Terminal Server Profiles are kept on
> a samba share. When a user creates a file locally in C:\Documents and
> Settings(or whatever it's called in english :-) ), sets the file to
> readonly, and then logs out, the read-only flag isn't preserved on the
> AIX Server. Is this expected behavior? The file ends up with an 765
mask
>
>
> create mask = 0664
> directory mask = 0775
> inherit permissions = Yes
> profile acls = Yes
>
> Thanks in advance.
> Howard Allison
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba

sorry... must have been blind... inherit permissions was the culprit...

Mit freundlichen Grüßen
Howard ALLISON

--
VERTRAULICHKEIT: Diese Nachricht ist ausschließlich für denjenigen
bestimmt, an
den sie adressiert ist und kann vertrauliche Informationen enthalten. Falls
Sie nicht
der Empfänger dieser Nachricht sind, weisen wir Sie darauf hin, dass die
unberechtigte Weitergabe oder Verwendung sowie das unberechtigte Verteilen
oder
Kopieren dieser Nachricht strikt untersagt sind. Falls Sie diese Nachricht
irrtümlich
erhalten haben, vernichten Sie sie bitte sofort.

CONFIDENTIALITY: This message is intended only for the use of the
individuality or
entity to which it is addressed and may contain information that is
privileged,
confidential and exempt from disclosure. If you are not the intended
recipient you are
notified that any dissemination, distribution, use or copying of this
communication is
strictly prohibited. If you received this message in error, please
immediately destroy
this message.
--
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Antwort: Re: Antwort: Re: [Samba] Samba 3.3.4 Umlaut in Share comment

[Howard Allison]

> Christian Perrier 
> Gesendet von: samba-bounces+howard.allison=pva.sozvers...@lists.samba.org
>
> 03.06.2009 19:22
>
> An
>
> samba@lists.samba.org
>
> Kopie
>
> Thema
>
> Re: Antwort: Re: [Samba] Samba 3.3.4 Umlaut in Share comment
>
> Quoting Howard Allison (howard.alli...@pva.sozvers.at):
>
> > > How is the smb.conf file encoded? Is it UTF-8 or ISO-8859-1?
> > >
> > >
> > > --
> > I assume ISO8859-1(In the smitty 'convert flat file' menu UTF-8 isn't
an
> > option for the target - there are a few issues with the utf-8 packages
for
> > AIX 6... they don't seem to exist...
>
>
>
>
> > In any case it's the same smb.conf that worked in 3.0.32...with
umlauts...
>
>
> IIRC, full Unicode-only internal handling on strings has only been
> completed in 3.2 (samba developers would probably better confirm this
> than me) so it wouldn't be surprising that it doesn't work anymore.
>
> You really should convert that file to UTF-8:
>
> iconv -f iso-8859-1 -t utf-8 smb.conf.new
>
> Hopefully, AIX 6 has iconv..:-)...otherwise you need to edit the file
> on an UTF-8 enabled system (any recent Linux distro is probably well
> suited).
>
> at worst, just try replacing the umlauts with ASCII characters, just
> to see (of course that will lead to Ugly German...).
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
Thanks Christian, as William Jojo suggested - the AIX iconv isn't up to the
task - I've built a gnu iconv on AIX 6.1 here - and it does fix the
problem, but the umlaut isn't legible anymore with vi - looks like we'll be
sticking with the 'ugly German' solution :-)

thanks both for your help!


--
VERTRAULICHKEIT: Diese Nachricht ist ausschließlich für denjenigen
bestimmt, an
den sie adressiert ist und kann vertrauliche Informationen enthalten. Falls
Sie nicht
der Empfänger dieser Nachricht sind, weisen wir Sie darauf hin, dass die
unberechtigte Weitergabe oder Verwendung sowie das unberechtigte Verteilen
oder
Kopieren dieser Nachricht strikt untersagt sind. Falls Sie diese Nachricht
irrtümlich
erhalten haben, vernichten Sie sie bitte sofort.

CONFIDENTIALITY: This message is intended only for the use of the
individuality or
entity to which it is addressed and may contain information that is
privileged,
confidential and exempt from disclosure. If you are not the intended
recipient you are
notified that any dissemination, distribution, use or copying of this
communication is
strictly prohibited. If you received this message in error, please
immediately destroy
this message.

To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Antwort: Re: [Samba] Samba 3.3.4 Umlaut in Share comment

[Howard Allison]

>
> Re: [Samba] Samba 3.3.4 Umlaut in Share comment
>
> Quoting Howard Allison (howard.alli...@pva.sozvers.at):
> >
> >
> > Hi, I just upgraded from 3.0.32 to 3.3.4 on Aix 6.1, and noticed that a
> > 'net view' command from a windows xp workstation fails with a system
error
> > 1745. The share works perfectly fine, just the net view command
doesn't.
> > This occurs when there is an umlaut in the comment line of the share.
Is
> > this WAD?
>
> How is the smb.conf file encoded? Is it UTF-8 or ISO-8859-1?
>
>
> --
I assume ISO8859-1(In the smitty 'convert flat file' menu UTF-8 isn't an
option for the target - there are a few issues with the utf-8 packages for
AIX 6... they don't seem to exist...
In any case it's the same smb.conf that worked in 3.0.32...with umlauts...


--
VERTRAULICHKEIT: Diese Nachricht ist ausschließlich für denjenigen
bestimmt, an
den sie adressiert ist und kann vertrauliche Informationen enthalten. Falls
Sie nicht
der Empfänger dieser Nachricht sind, weisen wir Sie darauf hin, dass die
unberechtigte Weitergabe oder Verwendung sowie das unberechtigte Verteilen
oder
Kopieren dieser Nachricht strikt untersagt sind. Falls Sie diese Nachricht
irrtümlich
erhalten haben, vernichten Sie sie bitte sofort.

CONFIDENTIALITY: This message is intended only for the use of the
individuality or
entity to which it is addressed and may contain information that is
privileged,
confidential and exempt from disclosure. If you are not the intended
recipient you are
notified that any dissemination, distribution, use or copying of this
communication is
strictly prohibited. If you received this message in error, please
immediately destroy
this message.

To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Samba] Samba 3.3.4 Umlaut in Share comment

[Howard Allison]

Hi, I just upgraded from 3.0.32 to 3.3.4 on Aix 6.1, and noticed that a
'net view' command from a windows xp workstation fails with a system error
1745. The share works perfectly fine, just the net view command doesn't.
This occurs when there is an umlaut in the comment line of the share. Is
this WAD?
here are the debug lines...from Samba 3.3.3, but it's the same error.
Thanks,
Howard

[2009/06/02 08:25:53,  4] rpc_server/srv_pipe.c:api_rpcTNP(2353)
  api_rpcTNP: srvsvc op 0xf - api_rpcTNP: rpc command:
SRVSVC_NETSHAREENUMALL
[2009/06/02 08:25:53,  6] rpc_server/srv_pipe.c:api_rpcTNP(2379)
  api_rpc_cmds[15].fn == 2001763c
[2009/06/02 08:25:53,  5]
rpc_server/srv_srvsvc_nt.c:_srvsvc_NetShareEnumAll(1299)
  _srvsvc_NetShareEnumAll: 1299
[2009/06/02 08:25:53,  5]
rpc_server/srv_srvsvc_nt.c:init_srv_share_info_ctr(515)
  init_srv_share_info_ctr
[2009/06/02 08:25:53,  3] smbd/sec_ctx.c:push_sec_ctx(224)
  push_sec_ctx(19668, 10057) : sec_ctx_stack_ndx = 1
[2009/06/02 08:25:53,  3] smbd/uid.c:push_conn_ctx(388)
  push_conn_ctx(100) : conn_ctx_stack_ndx = 0
[2009/06/02 08:25:53,  3] smbd/sec_ctx.c:set_sec_ctx(324)
  setting sec ctx (0, 0) - sec_ctx_stack_ndx = 1
[2009/06/02 08:25:53,  5] auth/token_util.c:debug_nt_user_token(522)
  NT user token: (NULL)
[2009/06/02 08:25:53,  5] auth/token_util.c:debug_unix_user_token(548)
  UNIX token of user 0
  Primary group is 0 and contains 0 supplementary groups
[2009/06/02 08:25:53,  8] smbd/service.c:load_registry_shares(302)
  load_registry_shares()
[2009/06/02 08:25:53,  3] smbd/sec_ctx.c:pop_sec_ctx(432)
  pop_sec_ctx (19668, 10057) - sec_ctx_stack_ndx = 0
[2009/06/02 08:25:53,  5]
rpc_server/srv_srvsvc_nt.c:_srvsvc_NetShareEnumAll(1313)
  _srvsvc_NetShareEnumAll: 1313
[2009/06/02 08:25:53,  3] lib/charcnv.c:convert_string_internal(242)
  convert_string_internal: Conversion error: Incomplete multibyte sequence
(ü)
[2009/06/02 08:25:53,  1] librpc/ndr/ndr.c:ndr_push_error(493)
  ndr_push_error(5): Bad char conversion
[2009/06/02 08:25:53,  0] rpc_server/srv_pipe.c:api_rpcTNP(2382)
  api_rpcTNP: srvsvc: SRVSVC_NETSHAREENUMALL failed.



--
VERTRAULICHKEIT: Diese Nachricht ist ausschließlich für denjenigen
bestimmt, an
den sie adressiert ist und kann vertrauliche Informationen enthalten. Falls
Sie nicht
der Empfänger dieser Nachricht sind, weisen wir Sie darauf hin, dass die
unberechtigte Weitergabe oder Verwendung sowie das unberechtigte Verteilen
oder
Kopieren dieser Nachricht strikt untersagt sind. Falls Sie diese Nachricht
irrtümlich
erhalten haben, vernichten Sie sie bitte sofort.

CONFIDENTIALITY: This message is intended only for the use of the
individuality or
entity to which it is addressed and may contain information that is
privileged,
confidential and exempt from disclosure. If you are not the intended
recipient you are
notified that any dissemination, distribution, use or copying of this
communication is
strictly prohibited. If you received this message in error, please
immediately destroy
this message.

To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Fw: Antwort: RE: [Samba] Re: Samba + Vista Issue

[Howard Allison]

 So it seems we've found the problem - just in case someone else encounters
it.
 We had previously joined the Server with net ads join, and the
 attributes were still present in active directory, and the vista
 client tryed to force a kerberos blob on the samba server -  which
 was promptly ignored/rejected. The solution was deleting the AD
 entry for the server and re-joining.


 Mit freundlichen Grüßen
 Howard ALLISON
>
> samba-bounces+howard.allison=pva.sozvers...@lists.samba.org wrote on
> 26.11.2008 11:02:13:
>
> > Howard Allison 
> > Gesendet von: samba-bounces
+howard.allison=pva.sozvers...@lists.samba.org
> >
> > 26.11.2008 11:02
> >
> > An
> >
> > "samba list" 
> >
> > Kopie
> >
> > Thema
> >
> > RE: [Samba] Re: Samba + Vista Issue
> >
> >  >Hi,
> >  >
> >  >Name resolution is working correctly, this is something I checked
very
> >  >early in my investigation.
> >  >
> >  >If I use net use with the ip address the drive is mapped straight
away.
> >  >If I use net use with the dns name I am prompted to enter my
> >  >credentials.
> >  >
> >  >Regards
> >  >
> >  >Adam
> >  >
> >  >>-Original Message-
> >  >>From: samba-bounces+adam.stirk=brantano.co...@lists.samba.org
> >  >>[mailto:samba-bounces+adam.stirk=brantano.co...@lists.samba.org] On
> >  >>Behalf Of Peter Slickers
> >  >>>Sent: 18 November 2008 23:34
> >  >>To: samba list
> >  >>Subject: [Samba] Re: Samba + Vista Issue
> >  >>
> >  >>Adam Stirk wrote:
> >  >>
> >  >> I'm experiencing a problem with samba v3.2.4 and windows vista. If
I
> >  >> access my samba share via the ip address e.g. \\192.168.0.1\share
> >  >>   windows will authenticate against
the
> >  >> samba server and bring the share up, but if I use the dns name e.g.
> >  >> \\server.domain.local\share 
i'm
> >  >> faced with the logon box.
> >  >
> >  >I guess that name resolution is not working properly.
> >  >
> >  >Please open the command line interface on your Vista box and
> >  >type the following commands:
> >  >
> >  >   ping server.domain.local
> >  >   ping server
> >  >
> >  >If that is successful, try the 'net use' command:
> >  >   net use server
> >
> >
> >  >Peter
> >  >--
> >  >To unsubscribe from this list go to the following URL and read the
> >  >instructions:  https://lists.samba.org/mailman/listinfo/samba
> >
> > Hi, we're having exactly the same problem here - only with Vista... and

> > solutions found? I've tryed all of the usual Vista fixes to no avail,
> > DNS works fine
> > Thanks
> > Howard
> >
> >
> >
> > --
> > To unsubscribe from this list go to the following URL and read the
> > instructions:  https://lists.samba.org/mailman/listinfo/samba


--
VERTRAULICHKEIT: Diese Nachricht ist ausschließlich für denjenigen
bestimmt, an
den sie adressiert ist und kann vertrauliche Informationen enthalten. Falls
Sie nicht
der Empfänger dieser Nachricht sind, weisen wir Sie darauf hin, dass die
unberechtigte Weitergabe oder Verwendung sowie das unberechtigte Verteilen
oder
Kopieren dieser Nachricht strikt untersagt sind. Falls Sie diese Nachricht
irrtümlich
erhalten haben, vernichten Sie sie bitte sofort.

CONFIDENTIALITY: This message is intended only for the use of the
individuality or
entity to which it is addressed and may contain information that is
privileged,
confidential and exempt from disclosure. If you are not the intended
recipient you are
notified that any dissemination, distribution, use or copying of this
communication is
strictly prohibited. If you received this message in error, please
immediately destroy
this message.

To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

RE: [Samba] Re: Samba + Vista Issue

[Howard Allison]

>Hi,
>
>Name resolution is working correctly, this is something I checked very
>early in my investigation.
>
>If I use net use with the ip address the drive is mapped straight away.
>If I use net use with the dns name I am prompted to enter my
>credentials.
>
>Regards
>
>Adam
>
>>-Original Message-
>>From: [EMAIL PROTECTED]
>>[mailto:[EMAIL PROTECTED] On
>>Behalf Of Peter Slickers
>>>Sent: 18 November 2008 23:34
>>To: samba list
>>Subject: [Samba] Re: Samba + Vista Issue
>>
>>Adam Stirk wrote:
>>
>> I'm experiencing a problem with samba v3.2.4 and windows vista. If I
>> access my samba share via the ip address e.g. \\192.168.0.1\share
>>   windows will authenticate against the
>> samba server and bring the share up, but if I use the dns name e.g.
>> \\server.domain.local\share   i'm
>> faced with the logon box.
>
>I guess that name resolution is not working properly.
>
>Please open the command line interface on your Vista box and
>type the following commands:
>
>   ping server.domain.local
>   ping server
>
>If that is successful, try the 'net use' command:
>   net use server


>Peter
>--
>To unsubscribe from this list go to the following URL and read the
>instructions:  https://lists.samba.org/mailman/listinfo/samba

Hi, we're having exactly the same problem here - only with Vista... and 
solutions found? I've tryed all of the usual Vista fixes to no avail, 
DNS works fine

Thanks
Howard



--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] LDAP user search request includes domain

[Howard Allison]

 Original message 
>>Date: Fri, 19 Sep 2008 07:34:39 +0200
>>From: Howard Allison <[EMAIL PROTECTED]> 
>>Subject: [Samba] LDAP user search request includes domain 
>>To: samba@lists.samba.org

>>
>>Hi,
>>I'm running a Samba 3.0.32 server on AIX 6.1, AIX is authorizing with
>>secldapclntd to an OpenLDAP Server.
>>The Clients are coming from a Windows 2003 Terminal Server Thin Client
>>session, logged in to the domain.
>>I see in the logs that secldapclntd tries 3 times to authorize using
>>DOMAIN\USER as identification, and then finally uses USER(which works).
>>Is this Samba behavior, or AIX? Is there any way to convince Samba that
>>he should use just the User name for File Access?
>>Thanks
>>

>Have you looked at "winbind use default domain" ?


Yup, I've used yes and no, doesn't affect the process in the slightest 
unfortunately...


--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Samba] LDAP user search request includes domain

[Howard Allison]

Hi,
I'm running a Samba 3.0.32 server on AIX 6.1, AIX is authorizing with 
secldapclntd to an OpenLDAP Server.
The Clients are coming from a Windows 2003 Terminal Server Thin Client 
session, logged in to the domain.
I see in the logs that secldapclntd tries 3 times to authorize using 
DOMAIN\USER as identification, and then finally uses USER(which works). 
Is this Samba behavior, or AIX? Is there any way to convince Samba that 
he should use just the User name for File Access?

Thanks

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba