similar to: Microsoft Windows Network: The local device name is already in use.

Displaying 20 results from an estimated 2000 matches similar to: "Microsoft Windows Network: The local device name is already in use."

2012 Nov 21
1
Failure demoting 2008_R2 DC (S4rc5)
Hello, We are currently testing S4rc5 for an upcoming S3 to S4 migration. I am able to duplicate this issue with both classicupgrade and a new provision (both cases using internal DNS). I am able to join a 2008R2 system to the domain and promote it to a DC, however I am unable to demote it. The problem appears to be that the 2008R2 server fails replicating to the S4 DC. The specific error that I
2019 Aug 30
2
backup AD content
On 30.08.19 11:01, Andrew Bartlett wrote: > I'm very sorry to advise that this script is not race-free in the > locking done on the AD databases, which is why we have written the > 'samba-tool domain backup offline' tool which holds the correct locks. > > You should only need to back up the domain on one DC as long as you are > confident the DC is correctly
2017 Dec 28
1
2nd samba DC: NT_STATUS_NO_LOGON_SERVERS
Am 2017-12-28 um 15:55 schrieb L.P.H. van Belle via samba: > Hai Stephan, > > You need also this in smb.conf > > # enable offline logins > winbind offline logon = yes On which server(s)? The DCs? the DM? > I did also test my logins with one DC turned off. > And login on the DM is no problem or my pcs, no problem. > > I did not test the AD logins thats
2019 Nov 26
2
4.9.x -> 4.10.x : any major things to consider?
Am 26.11.19 um 20:53 schrieb Stefan G. Weichinger via samba: > Am 26.11.19 um 20:50 schrieb Rowland penny via samba: >> On 26/11/2019 19:44, Stefan G. Weichinger via samba wrote: >>> Am 26.11.19 um 20:39 schrieb Rowland penny via samba: >>> >>>>> I assume I have to start over: demote that DC2 etc >>>>> >>>>> Should have left
2008 Jan 30
1
net ads join : ads_connect: No logon servers
I've been able to use security = ads in smb.conf, and connect OK, but it must be falling back to domain. When I run net ads join I get the error (debug trace below): ads_connect: No logon servers Here is my krb5.conf: [logging] default = FILE:/var/log/krb5libs.log kdc = FILE:/var/log/krb5kdc.log admin_server = FILE:/var/log/kadmind.log [libdefaults] default_realm = BEER [realms] BEER
2019 Nov 26
0
4.9.x -> 4.10.x : any major things to consider?
On 26/11/2019 20:23, Stefan G. Weichinger via samba wrote: > Am 26.11.19 um 20:53 schrieb Stefan G. Weichinger via samba: >> Am 26.11.19 um 20:50 schrieb Rowland penny via samba: >>> On 26/11/2019 19:44, Stefan G. Weichinger via samba wrote: >>>> Am 26.11.19 um 20:39 schrieb Rowland penny via samba: >>>> >>>>>> I assume I have to start
2019 Nov 26
2
4.9.x -> 4.10.x : any major things to consider?
On 26/11/2019 19:29, Stefan G. Weichinger via samba wrote: > Am 25.11.19 um 16:07 schrieb Stefan G. Weichinger via samba: >> Am 25.11.19 um 11:49 schrieb L.P.H. van Belle via samba: >>> Hai Stefan, >>> >>> Yes, i do recommend the setup from 4.9 to 4.10 first. >>> >>> If you plan is to upgrade to buster. >>> 1) on stretch, update samba
2017 Dec 28
2
2nd samba DC: NT_STATUS_NO_LOGON_SERVERS
I added a 2nd DC (ADC2) to a samba-ADS today. debian-9.3, samba-4.6.11 from Louis followed https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory replication works afai see - We wanted to test services after turning off the first DC, and running ADC2 and a DM file-server only. DC1/backup: 10.0.0.224 ADC2: 10.0.0.230 We then get NT_STATUS_NO_LOGON_SERVERS On the
2019 Nov 26
2
4.9.x -> 4.10.x : any major things to consider?
On 26/11/2019 19:44, Stefan G. Weichinger via samba wrote: > Am 26.11.19 um 20:39 schrieb Rowland penny via samba: > >>> I assume I have to start over: demote that DC2 etc >>> >>> Should have left office when I could an hour ago. >>> >> Definitely sounds like you should, you are probably tired and it is >> easy? to make mistakes when you are
2018 Jul 20
0
Debian Stretch Samba Packages 4.8.3 available (amd64/i386)
Am 2018-07-19 um 14:18 schrieb L.P.H. van Belle via samba: > Hi guys, >   > It's finaly done... >   > The samba 4.8.3 packages for Debian Stretch are available on my apt : http://apt.van-belle.nl > The buildlogs are here :  http://downloads.van-belle.nl/samba4/Buildlogs/stretch/  >   > No changes, from my side. check the Samba change log for whats changed. >
2018 Jul 20
0
Debian Stretch Samba Packages 4.8.3 available (amd64/i386)
Hai Stefan, > upgraded a DC (one of two) from 4.8.2 to 4.8.3 (including some debian > jessie upgrades, did reboot) ?? Can you explain that process a bit more? As i understand you did the following. 1) upgrade a debian Jessie to Debian stretch. ? 2) upgrade samba from jessie to stretch. ? Is that correct ? Im asking because i did not build any jessie samba 4.8.2.. The cache entry,
2020 Feb 27
0
Samba AD - Different IP than the existing one assigned
J?en ai profit? pour desactive VPN et autre. Du coup, je n?ai que : root at TransmitCorp~# ifconfig -a eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9001 inet 172.31.6.15 netmask 255.255.240.0 broadcast 172.31.15.255 inet6 fe80::bf:52ff:fe4a:fe3c prefixlen 64 scopeid 0x20<link> ether 02:bf:52:4a:fe:3c txqueuelen 1000 (Ethernet)
2017 Nov 24
0
Samba 4.7.1 Switching from SAMBA_INTERNAL to BIND_DLZ failed
Hi Rowland! I've uninstalled the samba packages and their dependencies, and now the error is: Nov 24 23:29:16 testdc1.mytestdom.testsamba.com named[9501]: samba_dlz: Failed to connect to /usr/local/samba/private/dns/sam.ldb Nov 24 23:29:16 testdc1.mytestdom.testsamba.com named[9501]: dlz_dlopen of 'AD DNS Zone' failed Nov 24 23:29:16 testdc1.mytestdom.testsamba.com named[9501]: SDLZ
2020 Feb 27
0
Samba AD - Different IP than the existing one assigned
?Ok, so now : Content of /etc/hosts 127.0.0.1 localhost 172.31.6.15 adc1.transmitcorp.com adc1 Now, stop samba. Cleanup current data and now setup samba and provision again. cleanup /var/lib/samba /var/cache/samba Rename smb.conf Then provision again, the base is wrong so the AD-DB has wrong data. > > I removed smb.conf from /etc/samba > un the interactive
2020 Feb 28
0
Samba AD - Different IP than the existing one assigned
Try this. systemctl stop smbd nmbd winbind systemctl disable smbd nmbd winbind systemctl mask smbd nmbd winbind systemctl unmask samba-ad-dc systemctl enable samba-ad-dc systemctl start samba-ad-dc Reboot server. Check again. > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Lionel Monchecourt via samba
2020 Feb 27
0
Samba AD - Different IP than the existing one assigned
Hi, Thanks for helping. Answers in line : Log.smbd : [2020/02/24 10:02:22.602083, 0] ../source3/smbd/server.c:1815(main) server role = 'active directory domain controller' not compatible with running smbd standalone. You should start 'samba' instead, and it will control starting smbd if required Really big hint there, you are not starting
2017 Nov 24
2
Samba 4.7.1 Switching from SAMBA_INTERNAL to BIND_DLZ failed
Hi List! Im trying to switch from using the samba internal dns to bind. Im running a self-compiled samba 4.7.1 pair of DCs on Centos 7.2. After following the steps in the wiki, named refuses to start with this error: ● named.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled) Active: failed (Result:
2013 Jul 25
0
DsGetDomainControllerInfoW fails with level 2008+, works with 2003
Hello, I stumbled on this problem while troubleshooting a time synchronization problem. The Windows commands "w32tm /monitor" and "nltest /dclist:domain" appear to both use the same call to query the domain for a list of domain controllers. When the DC is Samba4 (2003 domain & forest level) these commands complete successfully. After raising the levels to 2008 or 2008_R2
2019 Sep 18
2
LDAP bind to AD fails
Am 18.09.19 um 19:16 schrieb Kris Lou via samba: > More than likely, certificate issues. > > If you use the IP in pfsense, then the Samba certificate needs to have the > IP as the CN. So you suggest to contact the dc via hostname ... googled this query command: # openssl s_client -connect adc1:636 tells me ... CONNECTED(00000003) depth=0 O = Samba Administration, OU = Samba -
2020 Feb 27
0
Samba AD - Different IP than the existing one assigned
Hi Louis Here we go for the output of the script Collected config --- 2020-02-27-14:28 ----------- Hostname: adc1 DNS Domain: FQDN: localhost ipaddress: 172.31.6.15 172.17.0.1 172.18.0.1 172.19.0.1 ----------- Kerberos SRV _kerberos._tcp. record verified ok, sample output: Server: 172.31.6.15 Address: 172.31.6.15#53 Non-authoritative answer: *** Can't find