OK, I'm trying to get Samba working with LDAP. And I have it... sort of.
I have a Samba server TESTBOX, and I can authenticate to it just fine.
It seems taht if I change the "netbios name" (which I was doing to
simulate "connecting from some other samba server in our network"), I
get:
$ smbclient //FS01/files 'foo' -U dballing -I
testbox.byramhealthcare.com -N -d 4
added interface ip=10.15.49.49 bcast=10.15.49.255 nmask=255.255.255.0
Client started (version 3.0.0beta1-1 for Debian).
Connecting to 10.15.49.46 at port 445
session request ok
Serverzone is 14400
Doing spnego session setup (blob length=58)
got OID=1 3 6 1 4 1 311 2 2 10
got principal=NONE
session setup failed: NT_STATUS_INTERNAL_DB_ERROR
... if I set the "netbios name" back to "TESTBOX", it works
just fine:
$ smbclient //TESTBOX/files 'foo' -U dballing -I
testbox.byramhealthcare.com -N -d 4
added interface ip=10.15.49.49 bcast=10.15.49.255 nmask=255.255.255.0
Client started (version 3.0.0beta1-1 for Debian).
Connecting to 10.15.49.46 at port 445
session request ok
Serverzone is 14400
Doing spnego session setup (blob length=58)
got OID=1 3 6 1 4 1 311 2 2 10
got principal=NONE
OS=[Unix] Server=[Samba 3.0.0beta2-1 for Debian]
session setup ok
tconx ok
smb: \>
... is the NETBIOS name stored in the LDAP password info in such a way
that it would be impossible to connect from two different netbios
hosts? This seems like it would be counterproductive as a "centralized
authentication database" for more than one server. Am I doing something
wrong?
