On Sat, Oct 04, 2008 at 10:30:28PM +1000, Jake Carroll wrote:
Hi all,
We are currently upgrading some core infrastructure and authentication
hosts (Mac OS X 10.4.11 Open Directory/OpenLDAP/KDC -- 10.5.5). We've
run into an interesting snag however.
The Sun host that we use for sharing
Hi all,
We are currently upgrading some core infrastructure and authentication
hosts (Mac OS X 10.4.11 Open Directory/OpenLDAP/KDC -- 10.5.5). We've
run into an interesting snag however.
The Sun host that we use for sharing out files over Samba 3.0.28a
(Sun's currently shipped, supported
Hi Paul, thanks for your advice.
I succeded in avoiding password server is not connected introducing
security=domain instead of security=server and 2.2.12.
About our choice on samba2 vs 3: compiling 3.x with Openldap was my
first try but I encurred in the known problem on supplemtary groups
Hi,
we are rolling out a big Samba 2.2.8a installation.
I used that version because I succeded in compiling it with Sun Directory Server 5.2
(ldap) libraries without any source modification.
We are using security=server, which is an Active Directory.
During our test we get a lot of random
We are using security=server, which is an Active Directory.
I'm pretty sure that 2.2.x doesn't do active directory well, if at all.
In any case, I would suggest 2.2.12 if you must use the old unsupported
version.
To compile 3.0.x to run against Sun's LDAP server, the stated procedure
is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am trying to troubleshoot a problem where users who were
authenticated fine are now unable to be authenticated.
Looking at the logs I see password server is not connected
note the 2 spaces between server and is, I checked line 1101 of
On Wed, 2003-01-29 at 14:13, David Bear wrote:
bringing the discussion back online -- thanks jerry for the responses.
please see below..
On Tue, Jan 28, 2003 at 10:56:24AM -0600, Gerald (Jerry) Carter wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 27 Jan 2003, David
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 22 Jan 2003, David Bear wrote:
I have installed samba 2.2.7a on FreeBSD from the ports collection. I
have used an existing samba config file which worked with samba 2.0.x.
I am using security = server
Use security = domain and your
I have installed samba 2.2.7a on FreeBSD from the ports collection. I
have used an existing samba config file which worked with samba 2.0.x.
I am using security = server
Yesterday, a user attempting to use a print share started getting
rejected with the message:
[2003/01/22 13:52:21, 1]
