similar to: Samba 3 PDC - client unable to join domain

Hello, I want to migrate from an old NT4 PDC to a Samba version 3.0.26a. My BDC configuration for migration is [global] workgroup = DOMAIN server string = %h server Samba %v interfaces = eth0, 192.168.1.0/24, lo bind interfaces only = Yes security = DOMAIN map to guest = Bad User passdb backend = tdbsam passwd program =

High there ... I cannot join my Samba PDC any longer with my XP-machines, I mean I'm not be able to create new machine accounts. The existing machine-accounts in the tdb-database works properly, all the existing XP-machines are joined without any problems. Only it isn't possible to joint the Samba PCD with new machines... My first Samba PDC-Configuration with this tdbsam as the passwd

Hi there ... I have a problem with my tdb-database after I've migrated from Debian-Samba-3.2.5-4lenny6 to Samba-3.2.5-4lenny7. All the old directories /etc/samba with the smb.conf and /var/lib/samba with the tdb-database has been hold. Now I've inexplicable effects with my tdb-database. - I cannot list my admin - user, which is the domain-administrator, in my passwd.tdb. - I cannot

Hi All, I have just joined this list, and this is my first post - so please bear with me. I am running debian testing (sarge) with a 2.4.23-1-686 kernel, and a self compiled samba-3.0.0final (--with-quotas), deployed from self built *.debs. It is running as a PDC (smb.conf at bottom of post), and I have successfully mapped "Domain Users" to unixgroup users, "Domain Admins"

Dear Samba Friends, I've a problem to join with Windows2000-Clients a Samba-PDC. When I join the samba-pdc with a WinNT4.0-Client it is no problem, first I create a machine-account for the machine: 1. in /etc/group exists the group: machines:x:515: 2. useradd -g machines -d /dev/null -c nickname -s /bin/false neuch205$ 3. pdbedit -a -m -u neuch205 In this way, it isn't a problem to join

I've installed a samba PDC with ldap database, but I can't join the domain with my windows XP machines. I populated the Database with smbldap-tools. When I try to log in as Root in the log file is written: log.0.0.0.0 1 [2006/12/29 11:49:24, 0] lib/util_sock.c:get_peer_addr(1229) 2 getpeername failed. Error was Der Socket ist nicht verbunden 3 [2006/12/29 11:49:24, 0]

Debian 2.6.18 smb.conf: [global] workgroup = DOMAIN server string = %h server interfaces = eth0 passdb backend = tdbsam passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessfully* . syslog = 0 log file = /var/log/samba/log.%m max

Hello, I'm running running samba 3.0.14a on a Gentoo 2005.1 Linux box. I have first set up Gentoo 2005.0 with Samba 3.0.10 (I think) and everything went fine. After an update to Samba 3.0.14a it will not work as it should. I'm running winbindd and samba with the following configuration: [global] workgroup = CDE server string = %h server (Samba %v) security =

Hi, i have a problems with windows clients when they try to change the password, windows respond with "Please enter valid character..." but the pass get changed. i have this in smb.conf passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n . when i change that to: passwd chat = *New*UNIX*password* %n *Re*ype*new*UNIX*password* %n

Hi all!! I'd set up my samba 2.2.7 to auth with "security=domain" mode, but my clients cannot auth successfully never because the samba server cannot "talk" correctly with my PDC(w2k adv. Server). In the computer manager event, I see authentication request but with empty usernames......so the PDC reject the authentication request. Is this a know

Hi, I have successfully setup a Samba PDC using a local LAP as the password backend. After I have added the first user 'testing' through pdbedit, some entries is added to the LDAP server too. However, when I tried to execute the 'net' commands(any) or smbmount or testing out the winbind(pam), all I get is error. So I just don't know how to proceed from here. Do I have to

Hi, We experience an every-now-and-then problem with our samba PDC. For a couple of days or so, the PDC runs just fine. Then, one after another, the workstations (Win9x, NT4/SP6a, Win2000/SP3) complain about the PDC not being there and refuse to logon users (naturally). The only workstation that's still able to see and connect to the PDC is the one that's on the same broadcast domain. An

Hi list, We are in the process of replacing our current Windows 2k file server with a Debian Linux one running Samba. I am running Samba 2.999+3.0.Alpha21 which is packaged for Debian in the Unstable tree. I believe I have configured everything correctly however when I login from a Windows client it is creating the users profile under there home directory rather than in the profile directory

Hi, I am running Samba 3.0.1 on a Debian/Sid machine. I have installed winbind to access the AD of the local network, which I want to use for UNIX logons. wbinfo -u shows all the users of the AD, but "getent passwd" only shows the contents of the file /etc/passwd. I have been following the instruction for winbind (Chapter 21) in the Samba-HOWTO-Collection. Any comments would be

I have set up samba to be a AD member and no other linux boxes. It worked well. I set up samba to be a PDS with no other linux boxes. It worked well. Now, I need to make a samba client that works with the samba PDS. I can join the domain. winbind can list users and such. getent doesnt work. I can see the authentication succeeding on the PDS but I cant access any shares. smbclient -L DOMAIN

I have a problem with a Member Server on Samba 3.0.28a running on Ubuntu Heady. Both systems were recently upgraded using Ubuntu's automated upgrade. It's also possible I broke a working configuration by accident. The shares on the Member server are visible on the XP clients and some users can authenticate properly. At least one user on one XP desktop cannot. The shares are visible

I have set samba server as PDC and I can see the network in others computers but not in the server, any idea? thx for advance my smb.cnf: # Samba config file created using SWAT # from 0.0.0.0 (0.0.0.0) # Date: 2007/03/09 22:38:36 [global] workgroup = DOMINI server string = %h Domain server (Samba, Ubuntu) obey pam restrictions = Yes passdb backend = tdbsam

Hello all! We recently upgraded from Samba 2.2.3 to Samba 2.999+3.0.alpha20-3 on debian 3.0. Ever since then users are unable to change their own passwords on their W2k machine. What happens is when they try to change it a process (passwd) gets stuck with the users name. The only way to fix this is to kill the passwd process the user started. I haven't changed the "passwd chat"

Hi! I have a samba 2.2.3a-12 on a Linux Debian box (lets call it pdcMachine) with a 2.4.16 kernel acting as a PDC of some domain (lets call it myDomain). I have a samba 2.999+3.0.alpha20-4 workstation (debian,kernel 2.4.19) (lets call it wstMachine) and i'm trying to join wstMachine to myDomain. I added: workgroup = myDomain password server = * security = domain encrypt passwords =

Hello everyone! I'm trying (unsuccessfully until now) configure two Samba servers: - Server A. Acting as PDC in a Windows 2000/XP domain and as profile server. - Server B. Acting as profile server. I have users whose profiles are in server A and others whose profiles are in the server B. The server where each user's profile lives is identified by the main group (GID) of the user (that