How about some thread necromancy.
Here's the issue I was working to resolve back in December of '04.
http://lists.samba.org/archive/samba/2004-December/097804.html
Until today I never really resolved this problem to my satisfaction.
Samba worked with ADS, and that was fine. Today I was attempti
Though I'm still concerned about the error, it looks like everything
is actually working. Winbind is authing users no problem, domain users
can gain access, so all seems well.
--
Andrew S. Zbikowski | http://andy.zibnet.us
A password is like your underwear; Change it
frequently, don't share it
On Mon, 3 Jan 2005, Andrew Zbikowski wrote:
> > I don't know if it might also work in your case. After defining an
> > uppercased netbios name on smb.conf, the segfault warnings stopped.
>
> netbios name = TTLNX01
>
> Mine was already uppercased, so that's not it.
>
>
I've seen similar error mess
> I don't know if it might also work in your case. After defining an
> uppercased netbios name on smb.conf, the segfault warnings stopped.
netbios name = TTLNX01
Mine was already uppercased, so that's not it.
--
Andrew S. Zbikowski | http://andy.zibnet.us
A password is like your underwear; Ch
The netbios name is defined as:
l%h
so I don't think it is a problem, but I'll try.
thx
On Thu, 30 Dec 2004 14:28:18 +0100 (CET), [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> On 30 Dec, Pau Capdevila wrote:
>
> > Authentication does work but it does not permission resolution (we use
> > win
I'm afraid it is no the issue (that about ACLs).
Winbind resolves local permission with Windows IDs. That not works in
local files with a winbind user.
The smbclient thing is a proof that something goes wrong.
Thank you anyway.
On Thu, 30 Dec 2004 05:40:22 -0800, Thomas M. Skeren III
<[EMAIL PR
Pau Capdevila wrote:
Authentication does work but it does not permission resolution
Huh? Do you mean that there's file access permission issues? If so
have you set up acl's? Remeber posix permissions are User, Group,
Other. All clients authenticating via W2K3 are Other.
(we use
winbind).
On 30 Dec, Pau Capdevila wrote:
> Authentication does work but it does not permission resolution (we use
> winbind). Neither smbclient -U domain user.
>
> I don't know the solution yet.
>
> We also use Debian but I'm afraid it is not Debian related because
> I've tried to compile Samba and MIT k
Authentication does work but it does not permission resolution (we use
winbind). Neither smbclient -U domain user.
I don't know the solution yet.
We also use Debian but I'm afraid it is not Debian related because
I've tried to compile Samba and MIT kerberos from source and it keeps
failing.
What
Andrew Zbikowski wrote:
Commented out passdb backend
abrams:/etc/samba# net ads testjoin
Join is OK
abrams:/etc/samba# net ads join
[2004/12/28 20:00:31, 0] libads/ldap.c:ads_add_machine_acct(1368)
ads_add_machine_acct: Host account for ttlnx01 already exists -
modifying old account
Using short do
Commented out passdb backend
abrams:/etc/samba# net ads testjoin
Join is OK
abrams:/etc/samba# net ads join
[2004/12/28 20:00:31, 0] libads/ldap.c:ads_add_machine_acct(1368)
ads_add_machine_acct: Host account for ttlnx01 already exists -
modifying old account
Using short domain name -- CORP
[2
Andrew Zbikowski wrote:
Since smb.conf is a link..let me try.
I've experienced some strange things as well, the question is, can ADS
users get a share properly? I had similar probs, but the share works.
What does net ads testjoin show?
Also in smb.conf you have a passdb backend. DON'T.
Here's
abrams:~# kinit [EMAIL PROTECTED]
This seems to work just fine.
abrams:~# net ads join "TwinCities\TTAGS\SERVERS"
[2004/12/28 18:52:20, 0] libads/ldap.c:ads_add_machine_acct(1475)
Warning: ads_set_machine_sd: Unexpected information received
Using short domain name -- CORP
[2004/12/28 18:52:23, 0
13 matches
Mail list logo
