trustdom and NT_STATUS_INVALID_COMPUTER_NAME

Stefan Gohmann gohmann at univention.de
Fri Mar 3 10:23:41 GMT 2006


Hello,

we have got a problem using Samba 3.0.20b and winbind in a trustdom setup to a 
Windows NT 4 domain.

The samba domain consists of 1 PDC and about 10 BDCs and a lot of memberserver 
(Samba 2.2, Samba 3, Windows NT, Windows 2k, Windows 2k3), the windows nt 
domain consists 1 pdc and 3 bdc. 
The DCs are distributed  over a lot of subnetworks, but all domain members 
(Samba domain and windows domain) are using the samba pdc as wins server.

For a while (a few days) everything worked fine and  then the 
authentication fails against a samba dc. The problem appears when a user from 
the windows domain starts the authentication against a domain member of the 
samba domain. The part of the logfile from the pdc:

[2006/03/02 18:00:20, 5] rpc_parse/parse_prs.c:prs_ntstatus(672)
       0034 status      : NT_STATUS_INVALID_COMPUTER_NAME
 [2006/03/02 18:00:20, 0] 
 auth/auth_domain.c:domain_client_validate(199)
   domain_client_validate: unable to validate password for user 
 stefan in domain
 WINDOWSNT to Domain controller \\Samba01. Error was 
 NT_STATUS_INVALID_COMPUTER_NAME. 

If we restart samba and winbind on all samba DCs ethen verything works good 
again.

Another problem in this domain is, that the windows explorer shows about 2300 
domain members from the samba domain. It should be about 2900. The strange 
behaviour is, that the listed computers are those whose names are starting 
with a letter in [a-f] or a number, lexicographical later names are not 
listed.

Any suggests? Please let me know if you need more infomration.

Best regards,
Stefan

-- 
** Besuchen Sie uns auf der CeBIT: Halle 5, Stand F58/2 im LinuxPark! **

Stefan Gohmann     <gohmann at univention.de>       fon: +49 421 22 232- 0
Entwicklung        Linux for Your Business
Univention GmbH    http://www.univention.de/     fax: +49 421 22 232-99



More information about the samba-technical mailing list