I have a similar problem, except I get the error NT_STATUS_UNSUCCESSFUL
checking the trust account password. Again downgrading to 3.0.2a worked
fine. Looks like bit rot has creeped into the code between .2a and .3.
Tom
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Two Toms:
Level 10 log files would be very helpful. Please send them
to me off list. I need these pretty fast though since
we're working on 3.0.4 today.
cheers, jerry
Tom Hibbert wrote:
| I have a similar problem, except I get the error
|
To: Tom Hibbert; [EMAIL PROTECTED]
Cc: samba mailing list
Subject: Re: [Samba] Samba 3.0.3 breaks domain somehow.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Two Toms:
Level 10 log files would be very helpful. Please send them
to me off list. I need these pretty fast though since
we're
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Josh Skains wrote:
| PLEASE have a Redhat 8.0 RPM... I'd appreciate it
| really really greatly This password issue is driving me
| up a wall with the user complaints :(
ok. I'll do RH 8.0 RPMS for 3.0.4. However, I've
already posted that RH8
-
From: Gerald (Jerry) Carter [mailto:[EMAIL PROTECTED]
Sent: Friday, May 07, 2004 8:57 AM
To: Josh Skains
Cc: samba mailing list
Subject: Re: [Samba] Samba 3.0.3 breaks domain somehow.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Josh Skains wrote:
| PLEASE have a Redhat 8.0 RPM... I'd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Josh Skains wrote:
| Yes, I got that and appreciate it. I just want to keep pissing
| off our IT department when our PDC (Software Engineering Team
| - Independent network) stays up for 2 years using Samba as our
| PDC, and their Windows 2003 server
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 7 May 2004, Tom Hibbert wrote:
I have a similar problem, except I get the error NT_STATUS_UNSUCCESSFUL
checking the trust account password. Again downgrading to 3.0.2a worked
fine. Looks like bit rot has creeped into the code between .2a
