similar to: winbindd and NT_STATUS_INVALID_COMPUTER_NAME

samba-3.0.21b on FreeBSD 6.0 and NT4.0 as a PDC. After joining to a domain I can get a users list and a groups list with wbinfo -u|-g but authentication does not work and when I try wbinfo -t I've got the message: checking the trust secret via RPC calls failed error code was NT_STATUS_INVALID_COMPUTER_NAME (0xc0000122) Could not check secret Just one time it worked after I've restarted

Hi i have 3 PDC on my network, and after reboot the first PDC, my winbindd can't call with it : [root@gw squid]# wbinfo -t checking the trust secret via RPC calls failed error code was NT_STATUS_INVALID_COMPUTER_NAME (0xc0000122) Could not check secret [2005/06/07 10:20:30, 3] nsswitch/winbindd_misc.c:winbindd_interface_version(261) [22308]: request interface version [2005/06/07

Hi, i've migrated a debian box into ads, most people can work as they should, some users eg which are not part of the domain can not authenticate themself, the log says NT_STATUS_INVALID_COMPUTER_NAME . After reading all the howtos i noticed that wbinfo -t doesn work, the output is: #wbinfo -t checking the trust secret via RPC calls failed error code was NT_STATUS_INVALID_COMPUTER_NAME

On Fri, Jul 24, 2009 at 09:13:07AM -0500, Lukasz Szybalski wrote: > > Try to add "-S delldebian2" to that command line > > > > net rpc join -I xx.x.x.xx -UAdministrator -w mydomainname -S delldebian2 > Enter Administrator's password: > [2009/07/24 08:46:47, 0] utils/net_rpc_join.c:net_rpc_join_newstyle(393) > Error in domain join verification

Hello, I'm trying to use ntlm_auth and winbindd to authenticate users against a Windows 2003 AD server. Despite having "disable netbios yes", winbindd insists on doing one NetBIOS exchange on UDP port 138 on startup. If I block this port "wbinfo -t", "wbinfo -a username", and ntlm_auth request fail with: error code was NT_STATUS_INVALID_COMPUTER_NAME

When I try and join my AD domain, I get the following error: root at mat-desktop:~# net join -I 10.252.159.137 -U Administrator Enter Administrator's password: [2010/11/02 10:38:01.176096, 0] utils/net_rpc_join.c:406(net_rpc_join_newstyle) Error in domain join verification (credential setup failed): NT_STATUS_INVALID_COMPUTER_NAME Unable to join domain SECLAB. In my smb.conf, my

We want to join out Linux-Server: SLES 10 SP1 x86 with Samba (samba-client-3.0.24-2.23) to our W2000 Domain. so i use the command: net join -S TQ-NET.DE -UAdministrator and i get the following Errormessage: Failed to join domain! ADS join did not work, falling back to RPC... [2008/03/12 12:07:29, 0] utils/net_rpc_join.c:net_rpc_join_newstyle(350) Error in domain join verification

I just updated to samba-3.0.9 on suse 9.1. All packages from the suse ftp server were installed including the heimdal rpm updates. I am using "security=ads". The new smbd, nmbd and winbindd started OK but I ran into the following errors: filesrv1:~ # wbinfo -t checking the trust secret via RPC calls failed error code was NT_STATUS_INVALID_COMPUTER_NAME (0xc0000122) Could not check

Hello, I am trying to make a RHEL6 box (samba-winbind-3.5.10-125.el6.x86_64) accept logins from a trusted domain; all is working fine for the primary domain, pam_winbind+pam_mkhomedir allow logins for domain users, when checking the trusted one though # net rpc trustdom list -Utest%pass Trusted domains list: TRUSTED S-1-2-5-etcetc Unable to find a suitable server for domain TRUSTED domain

If either the domain member or the domain controller causes the connection to break, winbind doesn't reconnect to the controller afterwards so authentication doesn't work properly. For more information, what I basically get is the following: - Connect to the domain controller --> everything works fine. - either reboot the domain member or domain controller - when whichever comes

Hi All, I have configured Samba 3.0.23 to work with Active Directory. Based on all the tests shown here: http://us3.samba.org/samba/docs/man/Samba-Guide/unixclients.html#adssdm Things are working as expected. Most machines and users are working as expected. I do have some Windows machines on another subnet, NOT joined to the domain that are giving me grief. Going to

Hi. I am trying to configure Samba in Domain security mode. I am on a Sun box running Solaris 9 and Samba 3.0.23. A computer account for this Unix Box is configured in the AD Domain (FAFIDDOM) but I am having issues running net rpc join. I am not planning to use winbind as the samba shares that I want to create are going to be used by ClearCase (Rational Configuration Management Tool). ClearCase

Hi All, I have configured Samba 3.0.23 to work with Active Directory. Based on all the tests shown here: http://us3.samba.org/samba/docs/man/Samba-Guide/unixclients.html#adssdm Things are working as expected. Most machines and users are working as expected. I do have some Windows machines on another subnet, NOT joined to the domain that are giving me grief. Going to

I actually did it successfully on a test network (the Win2K is mixed-mode), but when I took the same Samba server and plugged it into the real network, I could't get "smbpasswd -j bottlerocket.com" to fly. Now realize when I did this in a test network, I set up a dummy Win2K DC for this same domain, same IP address, etc. So I think something has a conflicting, duplicate entry. I

hi, after compiling samba30b1 on suse82 i try to join the domain: different commands, different responses but always the machine account was sucessfully created what doeas this mean ? a) net join -I 192.168.1.20 -U Administrator [2003/06/17 15:14:50, 0] rpc_client/cli_netlogon.c:cli_nt_setup_creds(249) cli_nt_setup_creds: request challenge failed [2003/06/17 15:14:50, 1]

Please cc me on replies. My employer recently upgraded to W2K3. I have no control over the employer's set up and limited access to information. Under the old server, everything was working fine. Now I can't mount the shared drive anymore. I'm running Debian sid; samba 3.0.6-3. ################################################ # mount shared_drive cli_negprot: SMB signing is

I have replaced several NT servers with SAMBA on FreeBSD 4.7. The versions of SAMBA vary from 2.2.7a to 2.2.8. The SAMBA servers have been joined to the domain and show up as Windows NT 4.9 Server under Server Manager on NT. I am now down to two remaining NT4 servers that are domain controllers. I am experiencing two issues; NetBIOS resolution seems to have gotten messed up and the logs on the NT

Since upgrading from CentOS 4.3 to CentOS 5 the smbclient tar commands seem to be broken. The version on 4.3 was 3.0.10 I believe, while on 5 it is 3.0.23c-2. Here's what happens. Running the command: $ /usr/bin/smbclient \\\\host.domain.com\\backup -A /tmp/ntcredentials works fine. It connects no problem. But: $ /usr/bin/smbclient \\\\host.domain.com\\backup -A /tmp/ntcredentials -Tc

I have read through previous posts but still cant connect to samba shares - any help much appreciated. Running Samba 3.0.10-1 on fedora Core 2. Dont know anything about AD as it's looked after by the big boys and they wont share their secrets with the linux team. I do know the server I need to authenticate with is acting as some sort of time server so I assume that is not an issue.

All - We are using 3.0.20a on SLES 9 and are trying to configure a member server for our NT4 domain. The wbinfo commands (-u and -g) show correct information. The getent commands (passwd and group) work fine also. If Samba is running without winbind, I can see the shares in the config file (net view \\xxxxxxxx) from a PC. With winbind running I get an error message about the computer name