similar to: openldap migration script fails...

so, i just installed CentOS on our server and set up NIS using the same configuration as on our other server, but the clients' ypbind services complain that although they can find the correct server, the server does not respond to requests. to debug this, i've: * pinged the server using its ip and it's name * ssh'ed to the server using it's ip and name *

I've upgrade to Samba 3.0.4 a System wich it's running SLES 8. The System is working with LDAP and smbldap-tools 0.8.4 for managing users and groups. I'd like to manage the user and group with usrmgr.exe running into a Windows 2000. When I tried adding new user the programs didn't work and it's reported an error. The log system running in the PDC [SLES 8], reporting:

I just installed NUT and my UPS is an APC Back-UPS ES 500. I looked in the list of drivers and found APC Back-UPS ES 350 listed in "drivers.txt" -- that list said I should use either the newhidups or hidups driver. I looked in the installation and I found headers and c files to create these drivers (I think), but in /usr/local/ups/bin there is no driver named, "newhidups or

Are their issues with Samba and Lustre working together? I remember something about turning oplocks off in samba, and while testing samba I noticed this [2010/08/27 17:30:59, 3] lib/util.c:fcntl_getlock(2064) fcntl_getlock: lock request failed at offset 75694080 count 65536 type 1 (Function not implemented) But I also found out about the flock option for lustre. Should I set flock on all

Hi, I've implemented an LDAPv2 server with samba support but find that smbpasswd does not work as expected. I am using berkeley db-4.1.25_p1, openldap-2.1.26, and samba-3.0.2a. Anybody have any clue why I get the following error when attempting to add samba support for a user (specifically a DB_KEYEXIST error). I get the following output (excerpt) from smbpasswd: ldapsam_add_sam_account:

OK, so I made this file: ------------------------------------------ #!/bin/sh<\n> #chkconfig: 2345 60 99 #description: NUT ups daemon if [ ! -f /usr/local/ups/bin/upsd ] then echo "NUT startup: cannot start" exit fi case "$1" in "start") chmod 0600 /proc/bus/usb/005/002 chown nut:nut /proc/bus/usb/005/002 /usr/local/ups/bin/upsdrvctl

Hi, I'm trying to configure Samba 3.0.5 (3.0.4 earlier) with OpenLDAP 2.1.30: This is what I get when I try to find out more about the user Administrator (who was added with the populate script): aresjr scripts # pdbedit -Lv ak failed to add domain dn= sambaDomainName=ARESJR,dc=smallworld,dc=no with: Already exists Adding domain info for ARESJR failed with NT_STATUS_UNSUCCESSFUL failed to

This is really hot. I manage a lab of 25 dual boot computers in the school where I teach, running fedora and (cough) win2k. Last year all went very well for the Windows users in my lab, but this year every time the users attempt to change their samba passwords using smbpasswd they get this error message: ---- console dialog for a user trying to change their samba password will logged on to the

Dear friends: I have been trying to install MSOffice using Crossover. I have an old license from 2002, which entitled me to install the Crossover Plugin and the CrossoverOffice Set up. Support for them has expired, but both programs uinstalled fine into their own directory in KDE. But I do have a problem installing MSOffice. I keep getting the error message "Unable to get a list of

Hi, I have an issues that involves KDC, it is quite complex so I'll try to be really specific. I was running Samba42 with a secondary server replicating all was working fine. After we upgrade to Samba43 we start with the issues: 1. Replication wasn't working anymore error (WERR_LOGON_FAILURE) 2. Kerberos is also broken. On the Primary DC wouldn't allow me to to a kinit

I am new to Samba, but not to Linux. I hope someone here can point me in the right direction. I have installed Samba and it appears to be working, at least as far as I have tested it. However, I have hit a snag in my testing. I have searched Google for several hours but I have not found a solution. On a Linux machine (named "annwn") running Fedora Core 6, I have set up a share, using

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list, please forgive cross posting, but I cannot specify the problem enough to say whether list it fits perfectly, so I'll ask on both. I have some machines based with following specs (see at the end of the email). They run CentOS 5.4 x86_64 with the latest patches applied, Xen-enabled and should host one or more domUs. I put the domUs'

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list, please forgive cross posting, but I cannot specify the problem enough to say whether list it fits perfectly, so I'll ask on both. I have some machines based with following specs (see at the end of the email). They run CentOS 5.4 x86_64 with the latest patches applied, Xen-enabled and should host one or more domUs. I put the domUs'

Hi, I'm a newbie with CentOS. Actually, with this generation Linux. I used it back in the middle 90's (Debian and Slackware) but migrated over to FreeBSD. I got tired of the dependency nightmares and wanted a system that "just worked". The FreeBSD ports system did just that for me. I HATE doing the rpm soup thing. RPM finders are nice but I'd rather just use something

Folks, I''ve been looking at creating a set of man pages for puppet and I''m trying to come up with a reasonable hierarchy. I''d appreciate any suggestions. So far, here''s what I''ve come up with: - puppet(1) - puppetca(1) - puppetdoc(1) - puppetrun(1) - puppetca.conf(5) - puppetd.conf(5) - puppetmasterd.conf(5) - puppetd(8) -

Hi, Today I upgraded my dovecot to a newer version (2.2.9 debian wheezy-backports) At that moment I also reconfigured the whole thing a bit nicer. Now I stumbled on the following issue. In my configuration I use 2 backends (LDAP & passwd-file). passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext

Installed Samba 3.0.10 via 'pkgadd' on Solaris 2.6 - previously running Samba 2.2.8. It starts up and SWAT confirms that it is running and I am using the same smb.conf but I am unable to connect to a share via PC. Message "\\s080 is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access