similar to: RSAT Error - not enough memory to move object

Displaying 20 results from an estimated 11000 matches similar to: "RSAT Error - not enough memory to move object"

2023 Dec 28
2
RSAT Error - not enough memory to move object
On 20/12/2023 14:54, Paul Littlefield via samba wrote: > When trying to move a user to a different OU on the domain, the RSAT tool came back with this error ... > > "Windows cannot move object because: Not enough memory resources are available to complete this operation." > > A screenshot of the pop-up is here:- > > https://ibb.co/qgGMRkK > > Thanks in
2023 Dec 28
1
RSAT Error - not enough memory to move object
On Thu, 28 Dec 2023 12:23:13 +0000 Paul Littlefield via samba <samba at lists.samba.org> wrote: > On 20/12/2023 14:54, Paul Littlefield via samba wrote: > > When trying to move a user to a different OU on the domain, the > > RSAT tool came back with this error ... > > > > "Windows cannot move object because: Not enough memory resources > > are
2020 Nov 03
4
DNS /16 reverse zone issues with children and octets
Hello Samba List, I have 2 problems with dns - seeing the child entries and a zone with an extra octet. First... I have created a /16 reverse zone as per the wiki page (https://wiki.samba.org/index.php/DNS_Administration#To_create_a_.2F24_reverse_zone)... $ samba-tool dns zonecreate dc3 130.130.in-addr.arpa $ samba-tool dns zonelist --reverse dc3 pszZoneName :
2018 Mar 10
3
Delete second IP address from aipServerAddrs and aipListenAddrs DC
On 09/03/18 13:30, lingpanda101 via samba wrote: > On 3/9/2018 5:30 AM, Paul Littlefield via samba wrote: >> For some reason, the provision picked up 2 network IP addresses in my VM. >> >> Snipped output below... >> >> >> root at dc1.example.com ~ $ (screen) samba-tool dns serverinfo dc1 >>   dwVersion                   : 0xece0205 >>  
2020 Mar 03
4
samba_dnsupdate
Sorry Paully, I thought i already replied it. The configs look good. Did a look back in time.. And Ahh.. Now this i missed. * yesterday, we changed the IP addresses of our DCs and the Wiki page did not mention (IMHO) 2 critical things... ... So you even missed more. Review all DNS entries for the problem DC and review your AD again. rgrep /etc and /var for all the old ip numbers and/or
2020 Mar 02
3
samba_dnsupdate
Can you run the debug script, that might give me more info. https://github.com/thctlo/samba4/raw/master/samba-collect-debug-info.sh Anonimze where needed. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > L.P.H. van Belle via samba > Verzonden: maandag 2 maart 2020 16:23 > Aan: samba at lists.samba.org >
2018 Mar 09
2
Delete second IP address from aipServerAddrs and aipListenAddrs DC
For some reason, the provision picked up 2 network IP addresses in my VM. Snipped output below... root at dc1.example.com ~ $ (screen) samba-tool dns serverinfo dc1 dwVersion : 0xece0205 fBootMethod : DNS_BOOT_METHOD_DIRECTORY fAdminConfigured : FALSE fAllowUpdate : TRUE fDsAvailable : TRUE
2020 Feb 11
3
Failover DC did not work when Main DC failed
On 03/02/2020 18:49, Kris Lou via samba wrote: > > From windows: > echo %logonserver% \\DC3 > nltest /dsgetdc:<domain> DC:\\DC3 Address: \\192.168.0.218 Dom Guid: bla bla bla ... The command completed successfully. > From a *nix domain member (i.e. client, not DC): > wbinfo --getdcname=<domain> > winbind --ping-dc wbinfo --getdcname=MYDOMAIN DC3 wbinfo
2013 May 30
4
Samba4 Secondary DC Replication Concerns
Hi Folks If I have 2 x Samba4 AD DCs, a primary and secondary, am I correct in assuming that if I add a Windows Client to the DOMAIN it should eventually replicate to the secondary DC? Paully
2020 Feb 17
3
Failover DC did not work when Main DC failed
On 16/02/2020 15:03, Paul Littlefield via samba wrote: > 1) finding a way for ALL 70+ desktops to look up the DCs properly and switch to a running one if one is not available (otherwise what's the point right?) Hello Samba Mailing List, Just to be clear, I am using Ubuntu Server 18.04.4 LTS running Samba 4.7.6 on both DCs. Is this the Samba version I should be using for this
2020 Feb 01
4
Failover DC did not work when Main DC failed
On 01/02/2020 15:10, Rowland penny via samba wrote: > Not really, all Samba AD DC's are global catalogs ;-) Ah, OK... so we don't need to worry about that then? -- Paul Littlefield Telephone: 07801 125705 Email: info at paully.co.uk Wiki: http://wiki.indie-it.com/wiki/Special:AllPages LinkedIn: https://www.linkedin.com/in/paullittlefield Paul Littlefield is environmentally
2004 Aug 24
2
Connected, but what now?
Hi Gavin and I appear to have successfully connected our Linux and Windows machines via Tinc, but cannot seem to do anything else. We cannot ping each other's vpn network. Gavin would like to be able to: * browse my local SMB (Windows and Samba) network * collect his email via my local mail server Are asking too much of a VPN here? Have we missed something? All details, Linux output and
2020 Nov 03
0
DNS /16 reverse zone issues with children and octets
Hi Paully I can help with showing the "subgroup" 0: instead of @ use 0 samba-tool dns query dc3 130.130.in-addr.arpa 0 ALL the additional 0 might be a bug in 4.7, which is end of life; I would suggest to upgrade first......but Rowland will know more about it probably. br Mani On 03.11.2020 11:24, Paul Littlefield via samba wrote: > Hello Samba List, > > I have 2 problems
2015 Jan 26
3
Moving DC1 to a Virtual Machine
On 26/01/15 15:16, Paul Littlefield wrote: > On 26/01/15 15:08, Rowland Penny wrote: >> Yes, set up a new DC with your new OS and join this to the domain, >> once up and running, transfer the seven (yes, there are 7) FSMO roles >> to the new DC. Once everything is running ok, turn off the old DC and >> remove *all* mention of it from the domain. > > Hi Rowland
2020 Mar 02
3
DNS add - Python error when record exists
Hello, When I run the following command... $ samba-tool dns add dc3 mydomain.com V-INT A 130.130.0.202 ...I get the following error... ERROR(runtime): uncaught exception - (9711, 'WERR_DNS_ERROR_RECORD_ALREADY_EXISTS') File "/usr/lib/python2.7/dist-packages/samba/netcmd/__init__.py", line 176, in _run return self.run(*args, **kwargs) File
2020 Mar 01
3
OpenVPN using LDAP Auth and Samba 4 AD
Hello All, I would like to use OpenVPN with Samba 4 AD using the LDAP Auth plugin. However, my tests come up with the following errors in the OpenVPN... LDAP bind failed: Strong(er) authentication required (BindSimple: Transport encryption required.) Unable to bind as CN=VPN Connect,CN=Users,DC=MYDOMAIN,DC=COM LDAP connect failed. PLUGIN_CALL: POST
2020 Feb 13
2
Failover DC did not work when Main DC failed
On 13/02/2020 13:11, Paul Littlefield wrote: > On 12/02/2020 13:08, Rowland penny via samba wrote: >> The first is that a DC must use itself as its nameserver and if >> something goes wrong e.g. Samba has fallen over, then there isn't >> much point having another nameserver, Samba isn't going to use it >> >> The second is, it will not hurt having a second
2020 Nov 16
1
Joining Samba to Upgraded 2003 domain failing
Hi Rowland I am trying to follow the article but am having the error. That's why I am trying to clean up this bad subdomain. I don't know if these lists allow image attachments. So I uploaded a screenshot here. https://ibb.co/Ct3BLjL I built a new domain for this problem in our lab. The domain listed with #1 is the one created by the domain provision. However the one listed with the #2
2020 Mar 02
6
samba_dnsupdate
On 02/03/2020 11:51, Paul Littlefield via samba wrote: > On 02/03/2020 10:49, Rowland penny via samba wrote: >> Does your DC have a fixed IP and if not, why not ? > > Yes, using netplan in Ubuntu 18.04... > > network: > ? ethernets: > ??? ens18: > ????? addresses: > ????? - 130.130.0.218/16 > ????? gateway4: 130.130.0.1 > ????? nameservers: > ???????
2005 Sep 20
1
2 samba servers on different subnets
Hi All Network #1 has been running successfully for a year using Samba as a PDC and file share with roaming profiles for about a dozen Windows XP clients. I have just set up Network #2 and would now like to give these clients access to the file share on Network #1 (via the Tinc VPN)... AND... still keep a local PDC with roaming profiles. NETWORK #1 Range: 192.168.0.0/24 Tinc/Samba PDC