security = server error: NT_STATUS_NO_TRUST_SAM_ACCOUNT

Andy Burleigh aburleigh at eaglept.com
Thu Apr 20 18:02:01 GMT 2000


Hi,

I'm attempting to free up some addresses here at work so I've got a red hat 
6.2 machine setup which can properly forward the machines (windows nt 
workstations and soon a few amigas) behind it out for network access, (mail 
and web browsing), but I also need to set up some shares off of the 
internal machines to our windows network and have access to some shares, so 
I've installed samba.

Currently when my internal machine boots up I receive an error that the PDC 
for the network cannot be reached so I am logging in by my cached settings. 
 This was happening before setting up samba, and still happening with samba 
running.

I was hoping that by correctly setting up samba I could do the following:
1) have my internal machines login validated through the linux/samba server 
against the current WNTSrv PDC. [this is not working]
2) let my internal machines browse the rest of the network [this works 
sometimes]
3) share internal resources out to the external network by setting up sh  
ared mounts on the linux/samba server.[this is not working]

Right now I am working on getting the validation done through the PDC, i've 
set security = server (and tried security = domain) i've set the password 
server = <netbios name> and <ip> and <*>.  None of these work.

This is the error I get with the bios name set:
[2000/04/20 11:31:41, 0] rpc_client/cli_netlogon.c:cli_net_auth2(160)
  cli_net_auth2: Error NT_STATUS_NO_TRUST_SAM_ACCOUNT
[2000/04/20 11:31:41, 0] rpc_client/cli_login.c:cli_nt_setup_creds(72)
  cli_nt_setup_creds: auth2 challenge failed
[2000/04/20 11:31:41, 0] smbd/password.c:domain_client_validate(1413)
  domain_client_validate: unable to setup the PDC credentials to machine *. 
Error was : NT_STATUS_NO_TRUST_SAM_ACCOUNT.

This is the error I get uisng *:
[2000/04/20 12:06:30, 1] lib/util_sock.c:open_socket_out(926)
  error connecting to 192.###.#.18:139 (No route to host)
[2000/04/20 12:06:30, 0] 
smbd/password.c:connect_to_domain_password_server(1153)
  connect_to_domain_password_server: unable to connect to SMB server on 
machine EPT71. Error was : code 0.
[2000/04/20 12:06:33, 1] lib/util_sock.c:open_socket_out(926)
  error connecting to 92.#.###.71:139 (No route to host)
[2000/04/20 12:06:33, 0] 
smbd/password.c:connect_to_domain_password_server(1153)
  connect_to_domain_password_server: unable to connect to SMB server on 
machine 92.#.###.71. Error was : code 0.
[2000/04/20 12:06:33, 0] smbd/password.c:domain_client_validate(1392)
  domain_client_validate: Domain password server not available.
Interesting thing here is that the first ip is not the PDC, the second is 
the correct netbios name, the following ips are incomplete, should start 
out 192.....

Any suggestions would be great, I've read a considerable amount of the docs 
and tried many configs to try and get this to work, I can set up samba for 
the internal machines using user level security and the smbpasswd file, but 
I'm getting nowhere fast....

Thanks,
Andy
 



More information about the samba-ntdom mailing list