similar to: (no subject)

Hi List: My setup: cups-1.3.5 nss_ldap-259 openldap-2.4.7 openslp-1.2.1 perl-5.10.0 samba-3.0.28 I have an application that is a Win32 app. We share the application on a Samba server. The application has 3 DLLs that it opens and uses code from. Originally we were running a 2.x version of Samba and all users had local accounts. Samba was not acting in a domain controller role. Users had

Looking for some help on this. (like everyone else). This appears to be a very well asked about problem and the advise is always the same... Check permissions here and there. My set up is: OpenSLP 1.2.1 OpenLDAP 2.4.7 Samba 3.0.28 nss_ldap CUPS 1.3.5 I've got everything working except the ability to add a "New Driver" from Windows XP Pro. Samba is running as a PDC / Domain

Hi, I've just moved a second Samba domain to LDAP -- it works great! However, the first domain is now dead in the water. It refuses to autenticate, and from the logs it looks like it's not find the SambaDomainName entry in the LDAP tree. Here is a diagram of how my LDAP tree is set up. dc=mycompany,dc=com |___ ou=computers |___ ou=people |___ ou=groups |___ sambaDomain=domain1 |___

I finally ran across the following post: http://lists.samba.org/archive/samba/2006-May/120798.html Turns out my earlier post to this list for help stems from the NSCD problem like this person had. I changed the negative TTLs in nscd.conf to 3s and changed the -t argument to 15 in my add machine script. This solved my join domain problem. Before all this, NSCD was not running. When NSCD is

Hi, i've some problems with winbind in Samba 3.0 Beta1. The configuration: Samba 3.0 Beta1 installed under Sles8 on IBM z800 (s390) compiled with gcc 3.2 and installed pam-devel-0.76-32 configure options: ./configure --with-pam --with-winbind --with-acl-support --with-tdbsam --with-libsmbclient --with-smbwrapper --with-utmp --with-quotas NT PDC with SP6a NT workstation with SP6a i try

Thank you, Louis, for your reply. By simply asking me to provide outputs of the aforementioned files, I found the cause of my first problem (auth failing). It was my /etc/hosts file on dc1. All of them should look like this, and indeed DC2 and DC3's *did* look like this: # cat /etc/hosts > 127.0.0.1 ? ? ? localhost.samdom.mycompany.net ?localhost > 192.168.3.201

And, BTW, right now, I am able to see my problem via the following 3 ways... 1) Through Windows DNS Manager, I cannot add, change or delete any DNS records from: mycompany.loc samdom.mycompany.net mycompany.net I *can* add, change and delete DNS records from: _msdcs.samdom.mycompany.net mycompany.com 7.168.192.in-addr.arpa 5.168.192.in-addr.arpa 3.168.192.in-addr.arpa

No, this is not needed. Solution here in this is simple. search primary.domain.tld # optional extra search domains after the primary. nameserver IP_AD-DC_OF_THIS_SERVER_FIRST nameserver IP_AD-DC_others Run : samba_upgradedns --dns-backend=BIND9_DLZ And your done, all needed records are fixed/updated. This goes wrong if the IP of the running server isnt the first and/or if search is setup

Louis, I appreciate your efforts with my predicament. I'm very sorry to say that your advice hasn't gotten me to a solution. After updating my /etc/network/interfaces to put my localhost IP address first (192.168.3.201, for example), saving, restarting services, rebooting, running "samba_upgradedns --dns-backend=BIND9_DLZ", saving, rebooting, etc., I still cannot add, edit or

Hi everyone, I'm relatively new to Samba - at least for more in-depth installations. Big Thank-You from my company to the brilliant developers responsible for this software. We have our Samba server integrated with our Windows 2003 AD domain users via Winbind - a working installation with some issues described below. getent passwd works as the many docs show (one entry below):

Hi, I'm not a seasoned samba user but I do have a little experience with it (mostly small setups with plain smbpasswd file and a few workstations). I also have some experience with OpenLDAP and I've even written some objectclasses and attributes when the standard ones weren't enough However, I'm trying to set up a midsized network using LDAP for SSO and I can't make samba

I am trying to set up samba server that trusts the local NT domain, so users who are logged intot the domain to not need to re-authenticate, nor have unix accounts set up. Config snipit: [global] workgroup = DC2DEV3 server string = DC2DEV3 netbios name = DC2DEV3 interfaces = en0 bind interfaces only = Yes smb passwd file =

Just tried with Samba3.0beta2 as PDC with LDAP backend. Machine still cannot automatically join domain. Workstation entry added to LDAP via add machine script but got access denied during the join. A join immediately following the first join succeeded. Here is the trace in the smbd log. [2003/07/07 11:43:06, 5] auth/auth_util.c:debug_unix_user_token(494) UNIX token of user 0 Primary group is

Hello everybody, I am not sure which DNS setup will fit best for my suites. I can imagine, that there are a lot of users out there using also BIND9 servers in their environment and can share their experience. In my case I am running following setup: I have two existing hosts running with DNS and DHCP services. I have setup a DHCP-Cluster with isc-dhcp-server on both machines, that means I have a

Hi, I have a LDAP backend for my Samba 3.0.2, and everything seems to work except adding XP machines to the domain, and unix logins with a ldap client. Since this mail is very long, I have created a small index, so you don't get exhaustet in the middle of all the logs... ;) 1. LDAP user-creation 2. Group info 3. pam/nss info 4. smb.conf [global] 5. Log from trying to add machine to

Add functions implementing MSI-X support. First user will be virtio-pci. Note that platform must set a flag to declare MSI supported. For PC this will be set by APIC. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Makefile.target | 2 +- hw/msix.c | 423 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ hw/msix.h | 35 +++++ hw/pci.h | 20 +++ 4

Add functions implementing MSI-X support. First user will be virtio-pci. Note that platform must set a flag to declare MSI supported. For PC this will be set by APIC. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Makefile.target | 2 +- hw/msix.c | 423 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ hw/msix.h | 35 +++++ hw/pci.h | 20 +++ 4

Add functions implementing MSI-X support. First user will be virtio-pci. Note that platform must set a flag to declare MSI supported: this is a safety measure to avoid breaking platforms which should support MSI-X but currently lack this in the interrupt controller emulation. For PC this will be set by APIC. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Makefile.target | 2

Add functions implementing MSI-X support. First user will be virtio-pci. Note that platform must set a flag to declare MSI supported: this is a safety measure to avoid breaking platforms which should support MSI-X but currently lack this in the interrupt controller emulation. For PC this will be set by APIC. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Makefile.target | 2

Add functions implementing MSI-X support. First user will be virtio-pci. Note that platform must set a flag to declare MSI supported: this is a safety measure to avoid breaking platforms which should support MSI-X but currently lack this in the interrupt controller emulation. For PC this will be set by APIC. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Makefile.target | 2