similar to: pwdump for ASU (Advanced Server for Unix) needed!

Hi, I've compiled the SAMBA 3.0 alpha18 with all default options and installed well. Then I would join my NT 4.0 machine using the following steps (manual, not On the fly): # useradd -g groupid -d /dev/null -c "comment" -s /bin/false -m machine_name$ # passwd -l machine_name$ # smbpasswd -a -m machine_name$ after that I tried to join my NT4.0 to the Samba PDC, but it failed

Hi all, I repost the message about the signatur because I've not had any response. This time I hopefuly to get some ideas. When we put the parameter "server signing = auto or Yes" in smb.conf, the Windows XP clients can no longer connect to the samba (3.0.2), the "net use \\server\ipc$ /u:user password" return error 64. If I disabled the "server signing" the

On Tue Feb 17 11:14:15 GMT 2004, Andrew Bartlett wrote: >> Any suggestions for things to try (or even a guaranteed solution ;-) ) would >> be very much appreciated. >> server signing = no >Try this as yes. How did you get it work? I've tried the "server signing = yes or auto", but it didn't work. Could you kindly tell us how to set the XP to get it

Hi, Is there a way in which i can run pwdump on Linux (without dosemu or wine). I have a cron job on NT which runs rdist /S to generate the Sam backup in the Repair folder. I Then copy this file to Linux. I need to run pwdump now and get the userid's. I also need to extract the group information. I dont think pwdump extracts that. Is there some way i can get this info too. The reason for

Hi, I had trouble getting the pwdump program to work correctly on a german version of NT4SP3. I believe the problem is based on the fact that the german group 'Administrators' is called 'Administratoren', and Administrators is hard-coded into the utility. Would it be possible to make that an optional parameter? Unfortunately, I have no access to a C-Compiler on an NT-station, so

Hi, 1. I want to migrate NT to Samba 3 domain without needing to rejoin all machine (using same domain name and SID). just curious, machine account should belong to what group sid? does it matter if belong to any value? 2. I just examine output of pwdump, some of member domain or even NT BDC is has "*****" in password field which means this account was disabled. I've verified that

Anyone dare to explain? For #2 I'm not using rpc vampire because it can't migrate hash password. ---- Hi, 1. I want to migrate NT to Samba 3 domain without needing to rejoin all machine (using same domain name and SID). just curious, machine account should belong to what group sid? does it matter if belong to any value? 2. I just examine output of pwdump, some of member domain or even

This is very frustrating. I have a number of print shares defined in smb.conf. Some of the printer shares open from the windows interface and display the correct status. Other open with the message "access denied" but printing continues to work. I spent an hour going over the latest smb.conf man page and found two possible solutions: 1) using "dissable spoolss = yes" 2)

Hi all, I'm having some problems getting a fedora core 4 box to work as file server into a windows domain. pdc is a hp unix with asu installed. i managed to get the linux box to join the domain, and i can see the box when i browse the network from a windows machine. but, i cannot map any shares... wbinfo -g is telling me it got an "error looking up domain groups", wbinfo -u shows

Found the solution to my 2.0.6 dying on me on SGI - SYSV_IPC needed to be #undef'ed in source/include/includes.h in favor of MMAP, seems to have fixed it. If I run the daemon in server mode, no prob. If I switch to domain mode (and use smbpasswd to join into the domain, per the instructions), I get the error indicating that the username/password pair was incorrect, as if I typed in a wrong

I''m beginning to believe that the use of the last column in the rules file to designate redirection/forwarding is too subtle for many users. For 1.3, I think I''ll do something like the following: Current rule: ACCEPT net loc:192.168.1.3 tcp 80 - all New rule: FORWARD net loc:192.168.1.3 tcp 80 Current rule: ACCEPT net fw::3128 tcp 80 - all New rule: REDIRECT net

The rule: ACCEPT loc $FW::3128 tcp www doesn''t work propertly, the http access does not redirect to squid but directly exit. what''s wrong? Thanks ------- Dario Lesca (d.lesca@ivrea.osra.it) -------------------------------------- @@@@@@@ this is my shorewall-1.2.13 config: #[/etc/shorewall/common.def]-----------------------------------------------

Fun, fun. I suggest checking the corresponding MTA configuration :) Return-Path: <David.Bear@asu.edu> Delivered-To: rohrbach@mail.webmonster.de Received: (qmail 56434 invoked by uid 801); 24 Sep 2004 15:51:37 -0000 Delivered-To: vrohrbach-karsten@rohrbach.de Received: (qmail 56429 invoked from network); 24 Sep 2004 15:51:36 -0000 Received: from post5.inre.asu.edu (129.219.110.120) by

Hello all, I hope this is an easy one, I've read all the howtos but I'm still very hazy on how to do this. What I want to do is replace my NT4 PDC with a Samba 3.0 PDC with an LDAP backend. I've got my OpenLDAP up and running with the basic People, Computers and Groups ou's. I've put the builtin NT groups in too. I have Samba 3.0 functioning as a BDC The trouble is

Hi, I would like to migrate from NT PDC to a Samba PDC. My main concern is that all my users have local profile (i.e. there is no roaming profiles). It seems that users profiles on a workstation are not valide when migrating to the Samba PDC. It seams that the users cannot keep the same identity. On the other hand, I would really like to change PDC without users noticing anything. Tools

Hi, on a system RedHat 8.0, only on this, not on other various RedHat8.0, I have see the follow strange error in /var/log/{messages,boot.log} ..... After the boot all it seems to work, the modules is loads.... I have already tried to install other versions of kernel but the problem is always the same one :-(( Someone has some idea of what is happening? Thanks... Dario Lesca

Hi, I tried to upgrade samba on a Linux from 2.2.8a to 3.0.0, and after the upgrade the printer sharing fails. I would like to participate in the search for the bug (if it is a bug), but I don't know how to start. If this is not a bug I would like to know why not, and how to work around, that the printer does not work with the attached smb.conf, while it works with samba version 2.2.8a

Warning .... The two interface samples contain samples of the three interface... [root@multilinux temp]# tar xvfz samples-1.4.4/two-interfaces.tgz three-interfaces/ three-interfaces/interfaces three-interfaces/routestopped three-interfaces/masq three-interfaces/policy three-interfaces/rules three-interfaces/zones ------- Dario Lesca (d.lesca@ivrea.osra.it)

Hi, we tried to migrate an NT4 Domain to Samba3.0.4. We took the easy aproach and started to dump the NT PW Database with "pwdump" and the groups with "addusers" which were used to build the initial LDAP DB for the Samba Server. The SID was set and the Samba PDC was started as a replacement for the NT one. Loggin on to the Domain with Windows 200x and XP machines works

I am trying to use the syntax: rsync -av -e "ssh -l ssh-user" rsync-user@host::module /dest found at http://rsync.samba.org/ftp/rsync/rsync.html but am getting the following: rsync -av -e "ssh -l sshuser" rhost.asu.edu::home uc-sirc1/home/ rsync: connection unexpectedly closed (0 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at