similar to: Do machine accounts have to be group 100

Hi all, I'm using the latest alpha version (the one that comes with Debian unstable) in domain mode, setting up a member file server, with domain clients authenticating to a W2k machine. I'm trying to use the "add user script" option to create new users automagically, but it never seems to run. The script in this case is a handwritten perl script, and I've added a

Hi, I'm switching between two domains, and I need to make a couple of Linux+Samba machines provide the same shares in both domains. I've set up two sambas in the same machine, listening on different subinterfaces, but I can't make winbind to behave properly. As soon as I start the second winbind, the domain accounts provided by the first one become hidden (that is, 'getent

Greetings- I have not found discussed / documented what to do with machine accounts when moving a Samba PDC to new hardware. I have seen that uid/gid numbers must match between the old/new system. I am thinking to use adduser to accomplish that, then make the numbers on the new server match, using a text editor. After that, can I simply enter the machine account entries by hand with a text

Hello I've stumbled upon a problem for inversion of a matrix with large values, and I haven't found a solution yet... I wondered if someone could give a hand. (It is about automatic optimisation of a calibration process, which involves the inverse of the information matrix) code: ********************* > macht=0.8698965 > coeff=1.106836*10^(-8) >

Sorry everyone for asking this stupid question. I want add a system account to my debian system. I did it on another machine a couple of months ago and it worked fine with this command (I think). Iam typing the command: adduser MACHINENAME$ but I keep on getting this error mssg: adduser: Please enter a username consisting of a lower case letter followed by lower case letters and numbers. Use the

Greetings everyone I finally succeeded in doing the seemingly most difficult thing, "following directions." I got my act together configuring the smb.conf and migrating using net rpc vampire into tdbsam. There are issues with this migration in which computer netbios names which are obviously all uppercase were not being created in /etc/passwd. I put my C cap on and converted the computer

Hi List, I have some issues with user manager for domains (srvtools.exe from MS) and the scripts mentioned in the subject. The examples from the samba howto collection seem to cause serious issues here. I am on debian etch and tried to create my own scripts but till now to now avail. With the examples from the docs I could add groups, but could not add users to groups. There was the option -A

Hi all The trouble I am still having is creating the machine account. I get an error saying that the dir /dev/null cannot be created because a file by the name of null exists in /dev. Does the machine account need to be in /dev/null or can I change it to something else. I am running redhat 7.2. and using this script to try and create accounts /usr/sbin/useradd -g machines -d /dev/null -s

I have client running windows 2000 which is part of a domain with a samba (2.2.3a) server running as PDC. Authentication works fine. On the _same_ client I have added a partition that boots into Win XP, it has the same machine name. However I cannot get it to join the domain. I can use the administrator account to look at objects on the pdc, but when I try to create a user account I get a

I read in the Samba HOWTO Collection that every machine in the domain needs to have a corresponding UNIX account. Does this mean whenever I add a machine to the network, I must create a UNIX account for each one?? Am I supposed to create Unix accounts for my users as well? Doesn't this defeat the purpose of using a centralized authentication backend such as LDAP or MySQL?

Hello everybody, I'm asking myself a rather simple issue (i hope it hasn't already be explained somewhere). I'm using ldapsam_compat on 3.0.1pre3(+Debian patches & smbldap-tools 0.8.1) to store both user accounts and machine accounts. It works just fine, but there still is something that i find quite odd. My smb.conf contains: add machine script =

Hi. I'm still having problems to login with Windows 2000 SP2 into my Samba PDC. The idealx howto says: "user and group rids must be given in hexadecimal in LDAP", however it also says: "However, the rids were written in decimal in LDAP. So at least 2.2.3-pre, Samba do not read them as hexadecimal anymore.". What's the case for 2.2.4? hex or dec? Alexander Skwar --

Howdy :) I just have a little question regarding PDC and domain logons... my setup is working nicely with roaming profiles, logging onto the Samba 2.2.3 PDC, but I find that I am still able to find the server from a new machine, supply a user/password and access the shares on the server. Is this correct operation? Surely allowing this completely defeats the object of machine accounts and a

Hi, To add a user to the system on the commandline, I usually use the adduser command. # adduser newuser And that's it. I've been using that command probably out of an old habit, since I've been a long-time Slackware user before. But now I wanted to dig a bit deeper, and some details puzzle me. Whereas on Slackware, 'adduser' is an interactive shell script to create a

Hello! adduser(8) perl script uses crypt(3) to generate encrypted passwords, as pointed in /usr/sbin/adduser itself. Currently in /etc/login.conf password format is MD5 as default but adduser always generates encrypted passwords in DES format. IMHO adduser script should read value of passwd_format in /etc/login.conf to decide what kind of salt (DES, MD5 or somewhat else) he gives to crypt. At

Hi, I am trying to set a samba server as my fileserver in a Win2k network with a AD domain Controller. Authentication is already done against an unix KDC, trusted by the DC and everything work fine from now. When trying to connect i have two problem. first is not that related to Samba, as i get a UNKNOWN_SERVER as the reply for the TGS-REQ sent by Win2k client. Excuse me if it is ununderstanble

Hi, Ive got winbind and samba working great (version 2.2.3) on our RH 7.1 box's. But as we have about 200 users on our domain, we want to restrict ssh access on our linux box's. So I created a group on the NT PDC called: Winbind In this group, Ive only put our developers and us, the sy admins. In the /etc/ssh/sshd_config, I entered the line: AllowGroups MMEBS+Winbind. Thus, allowing

at http://wiki.openpbx.org/tiki-index.php?page=Easy+route+to+building+OpenPBX.org there is the following adduser command: adduser --no-create-home --ingroup openpbx --disabled-password --disabled-login openpbx This does NOT seem to be the right format for Centos. So far, using man, I have come up with; adduser -M -g openpbx What else do I need?

I installed CentOS 3.3 some time ago and the first thing I did after the install was to run a little script that adds my user plus a few other things. The script adds my user like this USER="ulrik" PASSWD="<mypasswd>" /usr/sbin/adduser $USER -p $PASSWD It seemed to work fine except I couldn't login? I searched Google for reasons why I could only login via ssh as

Hello, We have a windows 2003 server hosting ADS. We also have a fedora core 2 file server running samba 3.0.2a. We have it currently configured to join the ADS domain. We Can use Winbind to see users, groups, etc. We can even browse samba shares from windows computers. However one thing we don't know: What we want to do is when a user is added to ADS for samba to create a user