similar to: Using rpcclient or samedit to randomise trust account passwords

ftp://samba.org/pub/samba/alpha and mirror sites 1) i fixed a problem with nmbd's GETDC response, it is responding better but still not perfectly (and 2.0.x and cvs main need to be fixed, as well) as there exists no explanation for the correct response to locate a Domain Controller using GETDC. the upshot of fixing this is that joining an nt workstation to a TNG domain is now _extremely_

ftp://samba.org/pub/samba/alpha and mirror sites rpcclient and samedit etc. on sun ultras were failing because getopt cannot be reused. evidence of this is by doing a samedit "createuser username -p password" and the reported password on-screen is total garbage. this was fixed by using the GNU getopt and getopt_long functions (hooray!) in the same way that rsync does. i have access

ftp://samba.org/pub/samba/alpha or mirror sites. this version has security = domain tested and, shock-horror, working. it is possible to do SMB connections with WORKSTATIONNAME\username (wow) and actually, this is _necessary_, because otherwise, how are you going to join it to a domain? :-) :-) as root: samedit -S . -U root% -l log [] createuser root -p rootpassword [] exit samedit -S thepdc

I've followed the instructions in the DUAL-SAMBA-HOWTO to try to install a Dual Samba system. I'm running Redhat 7.0 (awaiting my 7.3 in the post). I've installed it, added the user `CSMSRV-HEAD$' to both linux and also, using 'samedit' to TNG. This is the name of my HEAD samba server running. I've changed the security = share, and the server works on the network.

Hi everyone, First of all, could you please CC me, I am not (yet) subscribed to this list. Now my problem: I created a test setup at my office that uses winbind to authenticate linux users to a Windows NT server (they log in with DOMAIN+username), as described in the winbindd manpage. I followed their setup completely. (at my work I am using RedHat 7.1 and the winbindd daemon found in the

rpcclient sound cool. I am running 2.0.6 Samba. 'rpcclient' exists with it but a call to 'man rpcclient' gets no results. Could it be that the man pages are in a later release? Dan dmalcolm@hiwaay.net ----- Original Message ----- From: "Luke Kenneth Casson Leighton" <lkcl@samba.org> To: "Multiple recipients of list SAMBA-NTDOM"

anyone want to work next to a lake? i went to ntbugtraq / canada day party / conference last month and had a great time meeting interesting peole in a relaxed atmosphere. i thought i'd forward this on to the samba mailing lists as a lot of the people involved with samba have to deal with heavy duty nt environments. luke p.s don't bug russ if you don't cover the job requirements,

There seems to be some discrepancy between rpcclient's man page and "rpcclient --help" in regards to the servername. It seems that the proper usage of rpcclient is rpcclient [options] server this is the format that is specified in "rpcclient --help." rpcclient's man page, however specifies that the servername should come directly after rpcclient. I.E.

Hi I am trying to use rpcclient's addprinter to install a printer automatically in a large number of XP workstations (+100) But I get the following: 1) connecting to a XP workstation works fine rpcclient -U root sim31%xxxx rpcclient $> 2) adddriver also works fine. Enumdrivers shows this: rpcclient $> enumdrivers [Windows NT x86] Printer Driver Info 1: Driver Name:

First thanks for your quick reply, I may have explained myself improperly. By default - from my understanding- on any windows domain you're allowed to anonymously connect to : - rootDSE of the LDAP with an Anonymous bind ; -Connect to the IPC$ with a NULL session if allowed in the registry. But indeed you're not allowed to perform any method on the IPC$ neither to list the

Hello, I have an RHEL 4 Update 3 machine connected to a Active Directory. I'm running samba 3.0.21c, compiled from an SRPM: # rpm -q samba samba-3.0.21c-1 Does any one knows why I'm getting a 'segmentation fault' when I try to get the forms from a printer? # rpcclient -U <user> -W <domain> -c "setform <printer> <form>" localhost

Hello, We previously had Win2008 R2 DCs which we have begun to replace with Win2012 servers (forest is still at 2008 level however). I was able to query DFS via rpcclient but now I find that I am unable to. I know that SMB3 was introduced in Win2012 but I believe that it should auto-negotiate earlier versions. I did however test from v4.1.9 as well, unfortunately that still fails. From Samba3

Hi Kurt, You are absolutely right (as always). After restarting smb, rpcclient setdriver works fine. May be - in the next future release - cupsaddsmb will work. Thank you very much. Bernhard -----Urspr?ngliche Nachricht----- Von: Kurt Pfeifle [mailto:kpfeifle@danka.de] Gesendet: Samstag, 8. M?rz 2003 12:06 An: samba@lists.samba.org Betreff: [Samba] rpcclient setdriver fails:

Hi all!! We have 2 printers shared via samba with good results. Nowadays, we have the cups postscript driver in the server for windowsNT/2000/XP and it works fine, but i want to put the hp postscript driver as we have 2 hp printers. I put the postscript driver via rpcclient without no problem: rpcclient -U'admin%pass' -c 'adddriver \ "Windows NT x86" \

ftp://samba.org/pub/samba/alpha and mirrors. due to some confusion about how to use samedit's createuser command, i put a warning / security message in whenever createuser hostname$ is used. it basically says, now you can join the workstation to the domain because you have just set the trust account to the insecure, well-known initial value, and you had best join the workstation to the

Hi, I'm having a strange problem with cupsaddsmb ... it fails whenever I try to use it while using the rpcclient command ... the "addriver" command just fails (like below). Does anyone know what is wrong with the command cupsaddsmb is passing to rpcclient? Adding drivers through the windows point and print works fine ... this is samba 2.2.8a, Windows PDC. As far as I can tell,

Hello I've just updated to Samba version 3.0.22 (previously v3.0.4a) and get the following problem: rpcclient enumdrivers fails with WERR_UNKNOWN_PRINTER_DRIVER while rpcclient getdriver works just fine! Can this be? $ rpcclient -c enumdrivers GUTENBERG Password: ******** result was WERR_UNKNOWN_PRINTER_DRIVER $ rpcclient -c 'getdriver lg403-lj5000' GUTENBERG Password: ********

On Mon, Jun 18, 2018 at 2:39 PM, Andrew Bartlett <abartlet at samba.org> wrote: > On Mon, 2018-06-18 at 10:35 -0400, pisymbol via samba wrote: > > Small addendum, I did try: > > > > ./configure --nonshared-binary=ALL > > > > ERROR: source source3/smbd/notify_msg.c is in more than one subsystem of > > target 'smbstatus':

SUSE 9.1 samba-3.0.9-2.6 samba-client-3.0.9-2.6 I am getting some errors that I can't seem to track down in any of the archives. I came across this problem when trying to delete a driver none of the printers are listed in the smb.conf - it is all being generated from the cups and the printcap that cups makes on load First enumprinters works: rpcclient $> enumprinters

I'm running Ubuntu 10.04 LTS and loaded (via apt-get) Samba version 2:3.4.7 as part of the effort to bring up Sambafax. A dpkg-query gives the following: # dpkg-query -l | fgrep samba ii libcrypt-smbhash-perl 0.12-3 generate LM/NT hash of a password for samba ii samba 2:3.4.7~dfsg-1ubuntu3.1 SMB/CIFS file, print, and login server for U ii