On 2010-09-02 at 11:14 -0400 Gaiseric Vandal sent off:
> I found compiling Samba on Solaris to be quite a challenge. I did
> get EVENTUALLY get 3.4.8 compiled but not 3.5.2. I had to symlink
> /usr/ccs/bin/ld to gld. I also used gcc not Sun cc.
http://build.samba.org/?function=View+Host;host=s
Solaris 10 (with latest patches) should have samba 3.0.37 already included.
"smbd -b" indicates it was built with ADS support. I don't know if it
really works reliably or not, since I am not integrating with active
directory.
Sunfreeware.com samba did not include either zfs or nsswitch
sup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/01/2010 11:11 AM, prabu.muru...@emc.com wrote:
> Hi,
>
>
>
> I am trying to configure samba 3.0.21b with ads support on Solaris 10 U5
> SPARC.
>
> ./configure is failing with the following error.
>
> Error:
>
> Using libraries:
> LIBS
Hi,
I am trying to configure samba 3.0.21b with ads support on Solaris 10 U5
SPARC.
./configure is failing with the following error.
Error:
Using libraries:
LIBS = -lresolv -lnsl -lsocket -liconv
LDAP_LIBS = -lldap -llber
AUTH_LIBS =
checking configure summary... configure: e
I am using
Samba Version 3.0.26a
On -SUSE-SLES9
I had to
server schannel = on
client schannel = on
in the smb.conf
before I could run the net rpc join below and have it join the domain.
net rpc join -S domain controller -U root
Joined domain
Regards,
Ian.
On Thursday 18 January 2007 12:55 am, Stefan Kok wrote:
> Hi List
>
> We have a samba 3.0.21b running.
>
> When typing \\nlasrv in win98 run. We get a response like this:
>
> "The computer or sharename could not be found"
>
Do you get the same result when typing in the IP address?
--
Fedora Cor
Hi List
We have a samba 3.0.21b running.
When typing \\nlasrv in win98 run. We get a response like this:
"The computer or sharename could not be found"
We have used lmhost files on the win98 machines with the correct
details.
Win XP can see the shares if you type \\nlasrv in run.
Also nlasr
pdbedit --pwd-must-change-time 0 username
see everything in pdbedit --help
see ya.
daniel parkes wrote:
Yes i am triying to make this work also,
Please help!.
Thnx
On 8/18/06, User 1 <[EMAIL PROTECTED]> wrote:
Dear Expert,
I am running samba 3.0.21b-2 as PDC on my FC5, how to set "User
Yes i am triying to make this work also,
Please help!.
Thnx
On 8/18/06, User 1 <[EMAIL PROTECTED]> wrote:
Dear Expert,
I am running samba 3.0.21b-2 as PDC on my FC5, how to set "User must
change
password at next logon" and also "Password expired in xx days" ..
pls help
Thanks & regards
Wi
Dear Expert,
I am running samba 3.0.21b-2 as PDC on my FC5, how to set "User must change
password at next logon" and also "Password expired in xx days" ..
pls help
Thanks & regards
Winanjaya
***
No virus was detected in the attachment (no filename).
Your mail has been sca
samba@lists.samba.org
cc:
Subject: [Samba] Samba 3.0.21b binaries on AIX 5.2 ML7 fails to
join ADS domain
After installing Samba3.0.21b, on AIX 5.2 ML7 I get the following error
trying to join a domain, can anyone offer any advice?
Thanks
Mark
[wmsprod2:root]/usr/l
After installing Samba3.0.21b, on AIX 5.2 ML7 I get the following error
trying to join a domain, can anyone offer any advice?
Thanks
Mark
[wmsprod2:root]/usr/local/samba> testparm
Load smb config files from /opt/Samba/3.0.21b/lib/smb.conf
Loaded services file OK.
WARNING: passdb expand explici
] Samba 3.0.21b / Security = Server / Windows 2003 or
XP clients / AIX 5.3 = Problems...
On Thu, Feb 23, 2006 at 11:55:44AM -0600, [EMAIL PROTECTED]
wrote:
>
> Wondering if any one has seen the following issues with Samba 3.0.21b
> with Windows XP and 2003 clients:
>
> [2006/02/23 11:4
TED]> To
Sent by: Ray Gebbie <[EMAIL PROTECTED]>
samba-bounces+ray cc
[EMAIL PROTECTED] samba@lists.samba.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ray Gebbie wrote:
> On our AIX 5.2 system we have Samba 3.0.4 and 3.0.21b. The smb.conf files
> are identical for both versions. The 3.0.4 version runs fine, but with
> 3.0.21b, we get errors like the following when trying to run smbclient:
...
> Wha
ubject
[Samba] Samba 3.0.21b is not able
to connect to password server
03/01/2006 02:01
On our AIX 5.2 system we have Samba 3.0.4 and 3.0.21b. The smb.conf files
are identical for both versions. The 3.0.4 version runs fine, but with
3.0.21b, we get errors like the following when trying to run smbclient:
[2006/02/28 22:03:05, 0]
rpc_client/cli_pipe.c:cli_rpc_pipe_open_schannel(2641
- Original Message -
From: <[EMAIL PROTECTED]>
To:
Sent: Monday, February 27, 2006 11:16 AM
Subject: [Samba] Samba 3.0.21b binaries on AIX 5.2 ML4,fails to run after
install
> After installing the prbuilt binaries from samba.org for AIX 5.2, and
> installing, I get t
After installing the prbuilt binaries from samba.org for AIX 5.2, and
installing, I get the following running testparm or smbstatus :-
[WMSTRAIN:root]/opt/Samba/3.0.21b/bin> smbstatus
exec(): 0509-036 Cannot load program smbstatus because of the following
errors:
0509-130 Symbol resolution
Hi jerry.
So what do you suggest, upgrade glib, but i have the latest
Red Hat Enterprise Linux ES release 4 (Nahant) .
kernel version 2.6.9-5.ELsmp .
and the glibc version that i have is
glibc-kernheaders-2.4-9.1.87
glibc-profile-2.3.4-2
glibc-devel-2.3.4-2
compat-glibc-2.3.2-95.30
glibc-2.3.4-2
g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
mallapadi niranjan wrote:
> Hi jerry.
>
> This particular error happens only when make a user member of more
> than 50 groups, and when he logins it crashes. saying "Remote
> procedure was cancelled in windows". and in samba is there any
> limit of
Hi jerry.
This particular error
happens only when make a user member of more than 50 groups, and when he
logins
it crashes. saying "Remote procedure was cancelled in windows". and
in samba is there any limit of user being member of number of groups. if how
much.
if the user is in 10 or 20 groups,
Jeremy Allison wrote:
On Sat, Feb 25, 2006 at 12:35:07AM +0100, Thomas Limoncelli wrote:
FWIW, 3.0.21c (binary RPMs for SuSE 9.3 Pro) still crashes upon startup
when processing the very same winbindd_cache.tdb file. Jerry should have
the file.
I though you'd sent it to Jerry already. It works
On Sat, Feb 25, 2006 at 12:35:07AM +0100, Thomas Limoncelli wrote:
> Gerald (Jerry) Carter wrote:
> >Lars Müller wrote:
> >>On Wed, Feb 22, 2006 at 11:50:36AM +0100, Thomas Limoncelli wrote:
> >>>Is there anything else I can do to help tracking this down?
> >>Run the upcoming 3.0.21c release as soo
Gerald (Jerry) Carter wrote:
Lars Müller wrote:
On Wed, Feb 22, 2006 at 11:50:36AM +0100, Thomas Limoncelli wrote:
Is there anything else I can do to help tracking this down?
Run the upcoming 3.0.21c release as soon as it is out.
[...]
For what it's worth, the SAMBA_3_0_RELEASE is ready for
On Fri, Feb 24, 2006 at 04:38:49PM +0100, Thomas Limoncelli wrote:
> It has crashed for me again -- this time unrelated to winbindd_cache.tdb
> processing as it seems, since it happened at runtime (during "getent
> group somegroup", IIRC):
>
> [2006/02/24 14:10:39, 0] lib/util_sock.c:write_data(
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
mallapadi niranjan wrote:
> Hi all
>
> I have samba 3.0.21b with openldap 2.3.19 on Redhat Enterprise Linux 4 ES
> with Kernel Version 2.6.9-5.
> i have allready posted this error in bugzilla, bug 3545
>
> i have created 70 groups, (test1-test70), an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Limoncelli wrote:
> It has crashed for me again -- this time unrelated to winbindd_cache.tdb
> processing as it seems, since it happened at runtime (during "getent
> group somegroup", IIRC):
I'm pretty sure this is now fixed in 3.0.21c which ha
It has crashed for me again -- this time unrelated to winbindd_cache.tdb
processing as it seems, since it happened at runtime (during "getent
group somegroup", IIRC):
[2006/02/24 14:10:39, 0] lib/util_sock.c:write_data(559)
write_data: write failure. Error = Connection reset by peer
[2006/02/
With the same environment/config as described in the "Samba 3.0.21b
winbind crash" thread
http://lists.samba.org/archive/samba/2006-February/118057.html
I've ran into the next issue (now that I have a clean
winbindd_cache.tdb). The primary domain XXX that Samba/winbind is a
domain member se
Hi all
I have samba 3.0.21b with openldap 2.3.19 on Redhat Enterprise Linux 4 ES
with Kernel Version 2.6.9-5.
i have allready posted this error in bugzilla, bug 3545
i have created 70 groups, (test1-test70), and created a user "nir" and made
"nir" member to these
70 groups.
>From Windows system
...
Lamar
-Original Message-
From: Jeremy Allison [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 23, 2006 3:16 PM
To: Saxon, Lamar
Cc: samba@lists.samba.org
Subject: Re: [Samba] Samba 3.0.21b / Security = Server / Windows 2003 or
XP clients / AIX 5.3 = Problems...
On Thu, Feb 23, 2006 at 11
On Thu, Feb 23, 2006 at 11:55:44AM -0600, [EMAIL PROTECTED] wrote:
>
> Wondering if any one has seen the following issues with Samba 3.0.21b
> with Windows XP and 2003 clients:
>
> [2006/02/23 11:47:58, 1] libsmb/ntlmssp.c:ntlmssp_update(252)
> Failed to parse NTLMSSP packet, could not extract
Wondering if any one has seen the following issues with Samba 3.0.21b
with Windows XP and 2003 clients:
[2006/02/23 11:47:58, 1] libsmb/ntlmssp.c:ntlmssp_update(252)
Failed to parse NTLMSSP packet, could not extract NTLMSSP command
[2006/02/23 11:47:58, 1] libsmb/ntlmssp.c:ntlmssp_update(252)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Limoncelli wrote:
> Gerald (Jerry) Carter wrote:
>>> I still have the original (problematic) tdb file around, so I could
>>> easily verify if winbindd still crashes upon *reading* this file. Would
>>> you be interested?
>>
>> No. That's ok. I
Gerald (Jerry) Carter wrote:
I still have the original (problematic) tdb file around, so I could
easily verify if winbindd still crashes upon *reading* this file. Would
you be interested?
No. That's ok. I have a tool to corrupt tdbs for tests like this.
:-)
But then, given that tdbtool appa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Limoncelli wrote:
> I agree that this'd be a useful generic change to limit the
> *consequences* of any tdb cache file corruption (which winbindd should
> still avoid to contribute to in the first place, of course).
>
> Are you saying that we'l
Gerald (Jerry) Carter wrote:
Lars Müller wrote:
On Wed, Feb 22, 2006 at 11:50:36AM +0100, Thomas Limoncelli wrote:
Shall I file a bugzilla entry and assign to the SuSE package maintainer?
Please as soon as you have the same problem again. See the details for
bug reporting at http://en.opensus
Gerald (Jerry) Carter wrote:
But since winbindd from 3.0.21b was the only process ever maintaining
this file, wouldn't this still make it a significant bug worth looking
into?
Yes. But the only real solution is to have winbindd remove
the corrupted file automatically and reopen it. It's a rob
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lars Müller wrote:
> On Wed, Feb 22, 2006 at 11:50:36AM +0100, Thomas Limoncelli wrote:
> [snip]
>> Is there anything else I can do to help tracking this down?
>
> Run the upcoming 3.0.21c release as soon as it is out.
>
>> Shall I file a bugzilla en
On Wed, Feb 22, 2006 at 11:50:36AM +0100, Thomas Limoncelli wrote:
[snip]
> Is there anything else I can do to help tracking this down?
Run the upcoming 3.0.21c release as soon as it is out.
> Shall I file a bugzilla entry and assign to the SuSE package maintainer?
Please as soon as you have the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Limoncelli wrote:
> Gerald (Jerry) Carter wrote:
>>> At least, erasing winbindd_cache.tdb with tdbtool fixes the crashes
>>> for the
>>> moment.
>>
>> Sounds like and assert() firing in the caching code caused by
>> a failure to open the winbind
Gerald (Jerry) Carter wrote:
At least, erasing winbindd_cache.tdb with tdbtool fixes the crashes for the
moment.
Sounds like and assert() firing in the caching code caused by
a failure to open the winbindd_cache.tdb file. I doubt there's
anything else for you to do right now.
But since winbi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 22 Feb 2006, Thomas Limoncelli wrote:
> At least, erasing winbindd_cache.tdb with tdbtool fixes the crashes for the
> moment.
Sounds like and assert() firing in the caching code caused by
a failure to open the winbindd_cache.tdb file. I doub
Thomas Limoncelli wrote:
Unfortunately the backtrace doesn't look too meaningful (like in the
original level 10 debug) although I've installed the samba-debuginfo
package.
myserver# gdb winbindd 24887
[...]
(gdb) bt
#0 0xe410 in ?? ()
strace reveals that winbind segfaults when reading w
Jeremy Allison wrote:
On Wed, Feb 22, 2006 at 01:07:32AM +0100, Thomas Limoncelli wrote:
I'm using Samba 3.0.21b on SuSE 9.3 Pro (x86) with the binary RPMs from
samba.org/suse.com (3.0.21b-1.1.2-SUSE-SL9.3) on a Domain Member Server in ADS
mode with winbind against W2K3 SP1 AD servers and idma
On Wed, Feb 22, 2006 at 01:07:32AM +0100, Thomas Limoncelli wrote:
> I'm using Samba 3.0.21b on SuSE 9.3 Pro (x86) with the binary RPMs from
> samba.org/suse.com (3.0.21b-1.1.2-SUSE-SL9.3) on a Domain Member Server in
> ADS mode with winbind against W2K3 SP1 AD servers and idmap uids/gids stored
I'm using Samba 3.0.21b on SuSE 9.3 Pro (x86) with the binary RPMs from
samba.org/suse.com (3.0.21b-1.1.2-SUSE-SL9.3) on a Domain Member Server in ADS
mode with winbind against W2K3 SP1 AD servers and idmap uids/gids stored in a
central OpenLDAP directory.
Unfortunately, winbind gives me a hard
Does anybody here have a RPM Samba-3.0.21b for Linux Conectiva 10 ?
I tried to compile from source but it returned an error .
Thanks in advance
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
All,
The SAMBA version 3.0.21b expired password pam_winbind.so section
perhaps might still have an issue. It seems to just be in some kind of
loop and
never completes the section in pam_winbind.c of pam_sm_chauthtok.
See ssh (Solaris 4.2.p1 ssh) sequence below:
ssh hermione
Password:
Cha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
===
Chef: Bon appétit!
Donkey: Oh, Mexican food! My favorite.
-- Shre
51 matches
Mail list logo
