similar to: Issues with Joining an NT4 Domain

Trying to set up a SAMBA print server using SlackWare 8.1. Have successfully joined it to the domain, but cannot browse into the shares, as it constantly asks for a password, and refuses to accept any including root and NTamdin accounts. Anybody have any ideas error logs and smb.conf are below. This is from the machine specific log file: [2002/08/21 11:41:56, 0]

I have samba running on RH 8, samba 2.2.7-2, and using winbind.. Want "homes" share to automatically display as users access it. Thought I could use the %u but am having no luck.. Currently, have it set up but when user clicks on home share a username/password dialog displays and will not accept valid credentials for that user? Have my config and log snips from nmbd and machine

What kind of error is "NT_STATUS_OK"? Logs below: [2003/01/29 15:30:46, 3] libsmb/namequery.c:resolve_lmhosts(768) resolve_lmhosts: Attempting lmhosts lookup for name TESTE011<0x20> [2003/01/29 15:30:46, 3] lib/util_sock.c:open_socket_out(845) Connecting to 192.168.100.1 at port 445 [2003/01/29 15:30:47, 0] rpc_client/cli_netlogon.c:cli_net_auth2(157) cli_net_auth2: Error

Quick run down of my setup: NT 4.0 PDC, Samba RedHat 8.0 with samba 2.2.5-10 on it.(Also used RedHat 7.2 with 2.2.6 final as well) with the exact same results. When I run wbinfo -t, I get Secret is bad 0xc000018b. I have been trying to figure this out for a few days now and can't get it working correctly. If I run wbinfo -u, all of the users appears in the list, as well when I run wbinfo

I am in the process of upgrading Samba from version 3.0.1 to 3.0.14a. The AIX team applied maintenance that sent the samba processes into some sort of loop which was impacting the machines. We were able to upgrade one of the unix servers with no issues but I cannot get the other one to work. We have 3 unix machines with samba that are working properly within this domain (the other 2 are still

Hi All, I tried to apply "server=domain" for a samba server domain member with samba-3.0alpha23 and samba-3.0alpha24. In each cases, " ads_connect: Connection refused .." message appeared when trying to join the domain. But "net rpc testjoin" says ok. The main point of this mail is that " smbclient -L mysamba -U username" will work on

I'm a bit puzzled. I am able to map an account without any problem on Samba 2.2.8a (security=domain). However, access fails with Samba 3.0.14a when everything else is the same (same configuration files). Any advice as to the cause of the problems (and its solution) would be appreciated. >From 2.2.8a logs [2005/08/24 14:59:51, 3, pid=7767] smbd/reply.c:(880) Domain=[americase]

Dear All, What can I do if my Windows PDC won't recognize the machine account it has just created for my samba server? I made sure I followed all instructions in the DOMAIN-SECURITY HOWTO: # smbpasswd -j DOM -r DOMPDC1 -Uadministrator%password Joined domain DOM. # And smb.conf containing the following: [global] security = domain domain logons = yes workgroup = DOM password

I'm trying to use the documentation found with Samba-2.2.4 to set up a samba server under RH linux 7.2 (kernel 2.4.9-21) to join an existing NT domain for a couple of weeks with no success. I obtained the samba 2.2.4 source code, compiled with the following options to configure: --with-winbind --prefix=/usr/local/samba --with-smbwrapper --with-pam --with -pam_smbpass After compiling, I

I've got no responce to my mail with subject 'samba 3.0.7 cannot join NT4 domain', so I dug deeper. I also read carefully these docs: swat/help/Samba-HOWTO-Collection/domain-member.html swat/help/Samba-HOWTO-Collection/winbind.html This is what I observe: 1.I srtart from clean state: PDC has no HUNTER machine account (chkd with L0phtcrack) HUNTER has empty var/{lock,private} samba

We have started to upgrade or Unix servers from Samba 2.0.7 to Samba 2.2.5. I did one machine as test and all worked fine. Today I tried adding two more today and both come up with the "Incorrect password or unknown username" box in Windows Explorer. All the Unix servers are running Solaris 7. I did the make on an NFS file system once and then ran 'make install' on each

Dear all, I have a serious problem that I can't rectify. My smb.conf is as follows. I use Solaris 2.6 on SPARC # Global parameters [global] workgroup = SOME_DOMAIN netbios name = 220R server string = Samba For Backup On Solaris security = SERVER encrypt passwords = Yes update encrypted = Yes obey pam restrictions = Yes password server = *

Hello, Sambas, Recently, I met a problem with my Samba 2.2.3a server. It is configured as a Domain Member, sometimes I couldn't get user list from PDC ( a Win2k server), but it come up again soon , say 5 seconds. I had thought it is PDC's problem, but it seems PDC is fine. Are there any other reasons will cause that? Some log messages attached. [2002/07/08 08:42:44, 0]

I have installed Samba 2.2.3a on a Solaris 2.6 box, and it has been configured with a small smb.conf that sets security = domain, workgroup = GFMNET, password server = GFMNET01, I have succesfully joined domain GFMNET (controlled by GFMNET01). I can attach to resources anywhere in the domain from this new box(E250), but any attempt to connect to its resources results in failed authentication. I

Hi, I want to get my SAMBA-3.0.0 domain to trust W2K AD (mixed mode) both ways. I don't want to make my samba box an AD member, just trust it. Samba-PDC uses ldap as passdb. winbind isn't used. WINS server is running in W2K PDC server. Also created a machine account entry to LDAP base, set samba I flag. Here we go (using mmc @ w2k PDC): I add my samba domain to "Domains trusted by

Hi all, We are having some problems getting a solaris 9(sparc) file server running samba 2.2.2 to authenticate aginst a windows NT 4 PDC. Let me say first that this was all working at one time, then we had some data corrumption on our NFS mounted /usr/local, and had to restore from tape. Due to some issues with solaris ufsdump and ufsrestore, stuff was not quite put back properly. We do

I've set up Samba on Mac OS X to do pass through authentication to the nt domain in AD several times now. No big deal, it usually just works. Now, however, it doesn't appear to be working. Note the relevant part of the transaction below (loglevel 4). Steps to replicate: a) Add pre-Win2K account with AD Users and computers b) sudo smbpasswd -j EXAMPLE -r WINSERVER -U

I have 2.0.7 Samba for Solaris and I tried to join an NT domain but got the following: /opt/samba/bin> smbpasswd -j niaaa01 cli_net_auth2: Error NT_STATUS_NO_TRUST_SAM_ACCOUNT cli_nt_setup_creds: auth2 challenge failed modify_trust_password: unable to setup the PDC credentials to machine NIAAAWMAIL. Error was : NT_STATUS_NO_TRUST_SAM_ACCOUNT. cli_net_auth2: Error

I am having a problem with getting samba 2.2.3a to work with our current set up. I used to have samba 2.0.7 working perfectly, but decided to upgrade to try and get Win2k clients to be able to access the shares on the UNIX system hosting samba. When I try and access any of the shares on samba (it doesn't matter who the client is) I get the following messages produced in the log file:

Hi all, We use samba here at our site as an interop solution for use with ClearCase. I'm afraid I'm just a lowly ClearCase administrator not a Unix administrator. All our solaris servers are running Solaris 8 and we're using Samba version 2.2.2 First Question : Our Unix Admin guy has said that we can't upgrade our version of Samba as 2.2.2 is the latest version that Sun have