[Samba] Samba 3.0.21b is not able to connect to password server
Ray Gebbie
Ray.Gebbie at fds.com
Thu Mar 2 16:33:08 GMT 2006
I am still awaiting some assistance with this. I need to upgrade from
3.0.4, but every time I try 3.0.21b, I get these problems. I have no idea
even what to look at. Please help if you can.
Thank you.
Ray Gebbie
Federated Systems Group
San Francisco, CA 94102
415-422-1662
Ray Gebbie
<Ray.Gebbie at fds.c
om> To
Sent by: samba at lists.samba.org
samba-bounces+ray cc
.gebbie=fds.com at l
ists.samba.org Subject
[Samba] Samba 3.0.21b is not able
to connect to password server
03/01/2006 02:01
PM
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)
cli_rpc_pipe_open_schannel: failed to get schannel session key from
server FD0
00XSFED01 for domain FEDERATED.
[2006/02/28 22:03:05, 0]
auth/auth_domain.c:connect_to_domain_password_server(11
2)
connect_to_domain_password_server: unable to open the domain client
session to
machine FD000XSFED01. Error was : NT_STATUS_CANT_ACCESS_DOMAIN_INFO.
[2006/02/28 22:03:05, 0]
rpc_client/cli_pipe.c:get_schannel_session_key(2417)
get_schannel_session_key: could not fetch trust account password for
domain 'F
EDERATED'
[2006/02/28 22:03:06, 0]
rpc_client/cli_pipe.c:cli_rpc_pipe_open_schannel(2641)
cli_rpc_pipe_open_schannel: failed to get schannel session key from
server FD0
00XSFED01 for domain FEDERATED.
[2006/02/28 22:03:06, 0]
auth/auth_domain.c:connect_to_domain_password_server(11
2)
connect_to_domain_password_server: unable to open the domain client
session to
machine FD000XSFED01. Error was : NT_STATUS_CANT_ACCESS_DOMAIN_INFO.
[2006/02/28 22:03:06, 0] auth/auth_domain.c:domain_client_validate(206)
domain_client_validate: Domain password server not available.
I don't understand why it would make a difference which version we use. If
it did not work with either version, then the configuration would be
suspect. Here is the Global part of smb.conf.
# Samba config file created using SWAT
# from 11.16.153.117 (11.16.153.117)
# Date: 2006/02/08 14:34:33
# Global parameters
[global]
workgroup = FEDERATED
netbios name = CCASEMCOM4
server string = MCOM4 Samba Server
security = DOMAIN
update encrypted = Yes
password server = fd000xsfed01
smb passwd file = /var/samba/private/smbpasswd
passwd program = /usr/bin/passwd
log file = /usr/local/samba/var/log.%m
large readwrite = No
max xmit = 65535
time server = Yes
unix extensions = No
deadtime = 30
max open files = 15000
dns proxy = No
kernel oplocks = No
ldap ssl = no
create mask = 0775
directory mask = 0775
mangle case = Yes
map archive = No
oplocks = No
level2 oplocks = No
strict locking = No
What is missing, or wrong, that would cause 3.0.21b to fail?
Thank you.
Ray Gebbie
Federated Systems Group
San Francisco, CA 94102
415-422-1662
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
More information about the samba
mailing list