similar to: NT_STATUS_RPC_PROCNUM_OUT_OF_RANGE when printing

On 31/10/2019 21:58, Vex Mage wrote: > > > > Have you tried 'net rpc trust create'? ? > > See 'net help rpc trust create' for the syntax. > > > When I attempt this I get the following error message > > SAMBAPDC ~# net rpc trust create > otherserver=sambaad.engineering.college.edu > <http://sambaad.engineering.college.edu>

Hello, we've updated to 3.6.1 yesterday, and since encounter problems with printing for some users. There's a descriptive error in the log.smbd, but I can't see what to do about it really (the rest of the, admittedly fairly ancient system, is the same base system as the previous 3.5.5 - only a couple of security updates were patched in during downtime). The message in log.smbd is:

i86_64 CentOS-6.5 Samba-4.1.4-7 (sernet) MS-Win2000 Advanced Server AD DC I am following the HowTo provided at https://wiki.samba.org/index.php/Samba4/HOWTO/Join_a_domain_as_a_DC. I am at this point: ---> In this case, 737506d0-bfe6-40c8-815d-08c3dff7a67f is the objectGUID of the new DC, we'll query with the following command: # host -t CNAME

Isn't there anybody who can help with this? Just a little hint maybe? -------- Originalnachricht -------- Betreff: samba 3.6.24 domain member as printserver in win2008/2012 domain: Access denied Datum: 2014-11-28 15:03 Von: problem1 at proxyma3.eu An: samba at lists.samba.org Hello everyone on the list, I'm trying to set up a samba server as a print server for a special purpose. The

Hi all, I am attempting to join a Centos7 machine to a Samba NT4 domain. I have created an account on our OpenLDAP server and ensured it has the default password. However trying to join the domain is consistently throwing an error. >From the machine that is trying to join the domain, I get this (edited for brevity): $~ net rpc join -U <user>%<passwd> -d 1 -I

i86_64 CentOS-6.5 sernet-samba-4.1.7 MS Windows Advanced Server 2000 We have a very old MS-Windows Domain Controller running on equally old hardware that we wish to replace with a Samba4 installation running on a virtualised CentOS-6.5 . Other than most user desktops this is the last remaining MS based system here and we would really, really like to shut it down. Our plan is to join two Samba4

Hi, Im running samba4.0.3. I added a new printer named "HP" via CUPS administration interface. I can see the printer as shared and I can print also, but what calls my attention is that on debugging information I keep getting the following constantly: winreg_create_printer: Skipping, SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Printers\HP already exists Below is my smb.conf

Since upgrading to 3.6.1 in Debian testing, I receive a panic/segfault message with each print job. Printing succeeds and continues to work, but an email with the info below is sent each time. The system is standalone. Kernel is 3.1.0-1-686-pae, and the system is fully updated. testparm returns no errors. Does this mean anything to anyone? Dale [Thread debugging using libthread_db

I'm stumped! From within CUPS, I'm able to successfully print test pages. From the Windows machine, I'm able to: * Browse the Samba server's printers via SMB * Add the Samba server's printers * Write to the Samba server's print$ share If I pause the printers via CUPS's interface, then Samba successfully relays this information when I try printing a test page from the

Hello ! I have just upgraded 40 x Samba domain member file server from 4.11.14 to 4.13.2 - No problem with 20 x domain member that are in a unique Samba domain (only samba DC) - But for my other domain (with composed of Windows 2016 DC), all of 20 x Samba domain member failed to desserve file after this upgrade :-/ I have triple check /etc/hosts, hostname, krb5 etc .... And

Hello! I'm trying to create a two way trust between a Samba DC and a Samba NT4 domain both are 4.10.9. The issue I'm seeing is that while I can establish a one way trust from the NT4 PDC to the DC using the following commands; net rpc trustdom add sambaad thepassword net rpc trustdom establish sambaad I enter the password for PDC$ and the trust is established. When I go into Domains and