similar to: Problem since upgrade to 4.5.1

Displaying 20 results from an estimated 10000 matches similar to: "Problem since upgrade to 4.5.1"

2016 Nov 18
1
Problem since upgrade to 4.5.1
Just a though as I was passing in the neighbourhood: does your Terminal Server have related SPN (ServicePrincipalName) created on computer objects? servicePrincipalName: HOST/W7AD-02 servicePrincipalName: HOST/W7AD-02.ad.domain.tld servicePrincipalName: TERMSRV/W7AD-02.ad.domain.tld servicePrincipalName: TERMSRV/W7AD-02 HOST/<hostname> should exist on all computers, that's just to be
2016 Nov 20
2
Problem since upgrade to 4.5.1
Hi Louis, While it wasn't spelled out, it was firmly implied in my previous message that this problem appeared only after the Samba upgrade. Nothing else has changed that might impact RDP. There has been no change to machine names, IP addresses (we use DHCP reservations) or DNS entries. If a dash in the computer's name or DNS entry is behind this issue then it's clearly a rather
2016 Nov 21
2
[Solved?] Problem since upgrade to 4.5.1
Hi Rowland, Thanks for the suggestion. So far, since adding 'ntlm auth' to smb.conf on the DCs we are no longer having this problem. Only time will tell if it stays working but at least I'm no longer getting complaints from the users. regards, John On 21/11/16 10:00, Rowland Penny via samba wrote: > On Mon, 21 Nov 2016 09:31:28 +1100 > John Gardeniers via samba <samba
2016 Nov 20
3
Problem since upgrade to 4.5.1
Hi Rowland, I Upgraded from Samba 4.4.2 and we have tried the FQDN without success. regards, John On 21/11/16 08:02, Rowland Penny via samba wrote: > On Mon, 21 Nov 2016 07:42:30 +1100 > John Gardeniers via samba <samba at lists.samba.org> wrote: > >> Hi Louis, >> >> While it wasn't spelled out, it was firmly implied in my previous >> message that
2016 Nov 21
4
[Solved?] Problem since upgrade to 4.5.1
Hai John,   I saw that this was resolved.   Just interested, are you using SSL/TLS with samba on you servers, and do you have you publish the AD DC/CA Root to your computers?   Did you look here in GPO : Computer Configuration -> Administrative Templates -> System -> Credentials Delegation. Before lowering samba security settings.   Some good info here to read into.
2016 Nov 18
0
Problem since upgrade to 4.5.1
On 17/11/16 21:48, John Gardeniers via samba wrote: > Since upgrading our DCs to Sernet Samba v4.5.1 we are experiencing > problems using Remote Desktop from Windows boxes. The rather useless > and completely misleading error message states: > > "The connection cannot be completed because the remote computer that > was reached is not the one you specified. This could be
2016 Nov 18
0
Problem since upgrade to 4.5.1
What is the hostname of the computer your connection to? If it contains a dash or other special sign, make a cname of that computer without any special signs and try to connect to that cname with rdp client. And ! try connection to : hostname.domain.tld Last, any change the computer your connections has ethernet and wifi? ( so if has 2 ipnumbers and one hostname ) If so, disable the wifi.
2018 Aug 07
2
Failed to modify SPNs
On Tue, 7 Aug 2018 14:59:56 +0100 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Tue, 7 Aug 2018 14:55:24 +0200 > Henry Jensen via samba <samba at lists.samba.org> wrote: > > > On Tue, 7 Aug 2018 12:51:33 +0100 > > Rowland Penny via samba <samba at lists.samba.org> wrote: > > > > > > > > Failed to modify SPNs on
2018 Aug 07
2
Failed to modify SPNs
On Tue, 7 Aug 2018 12:51:33 +0100 Rowland Penny via samba <samba at lists.samba.org> wrote: > > > > Failed to modify SPNs on CN=db1,CN=Computers,DC=mydom,DC=lan: acl: > > > > spn validation failed for spn[TERMSRV/DB1.MYDOM] uac[0x1000] > > > > account[db1$] hostname[(null)] nbname[mydom] ntds[(null)] > > > > forest[mydom.lan] domain[mydom.lan]
2018 Aug 07
2
Failed to modify SPNs
Hi Rowland, On Tue, 7 Aug 2018 09:46:24 +0100 Rowland Penny via samba <samba at lists.samba.org> wrote: > > Failed to modify SPNs on CN=db1,CN=Computers,DC=mydom,DC=lan: acl: > > spn validation failed for spn[TERMSRV/DB1.MYDOM] uac[0x1000] > > account[db1$] hostname[(null)] nbname[mydom] ntds[(null)] > > forest[mydom.lan] domain[mydom.lan] > > > > At
2018 Aug 07
1
Failed to modify SPNs
On Tue, 7 Aug 2018 16:26:36 +0100 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Tue, 7 Aug 2018 17:13:02 +0200 > Henry Jensen via samba <samba at lists.samba.org> wrote: > > > On Tue, 7 Aug 2018 14:59:56 +0100 > > Rowland Penny via samba <samba at lists.samba.org> wrote: > > > > > On Tue, 7 Aug 2018 14:55:24 +0200 >
2018 Nov 20
3
Domain join issues - 4.9.0
Hi, Does anyone have experience of using ldbedit or similar, to remove the duplicates below? (Is that even the right way for me to go?) Can I perhaps query something using ldbsearch, to find the duplicates, before using ldbedit? On Sun, 18 Nov 2018 at 21:37, Jonathan Hunter <jmhunter1 at gmail.com> wrote: > [...] > In my database, as reported by the domain join command above, I have
2018 Aug 07
2
Failed to modify SPNs
Hello, I've got some log entries like these on our DCs: Failed to modify SPNs on CN=db1,CN=Computers,DC=mydom,DC=lan: acl: spn validation failed for spn[TERMSRV/DB1.MYDOM] uac[0x1000] account[db1$] hostname[(null)] nbname[mydom] ntds[(null)] forest[mydom.lan] domain[mydom.lan] At first I thought it was about missing SPN entries, but adding these did not resolve the problem: # samba-tool
2016 Nov 22
1
[Solved?] Problem since upgrade to 4.5.1
Ok so if i understand right.. The production environment is running 4.5.1 ( and needs the "ntlm auth" ) The test environment als running 4.5.1, and this works without the ntlm auth Thats strange yes. About the production env., clean install of 4.5.1 of upgraded from? About this. >and yet a subset of his machines seemingly won't > accept an RDP connection by name,
2019 Jul 23
2
Error after upgrade NT_STATUS_INTERNAL_DB_CORRUPTION
OK, Thanks for all. Regards; On 23/07/2019 12:06, Rowland penny via samba wrote: > On 23/07/2019 16:02, Carlos via samba wrote: >> I haven't more output log, because i need join in dc in last week, >> and i "resolved"(workaround) in used samba 4.6.X -> after -> 4.8.3. >> Sorry..... > > OK, it would have been nice to have the output, this is
2016 Mar 10
2
Failed to modify SPNs on error in module acl: Constraint violation during LDB_MODIFY (19)
Hi all, SPN = servicePrincipalName A simple search returning all servicePrincipalName declared in your AD: ldbsearch -H $sam serviceprincipalname=* serviceprincipalname An extract from result concerning a lambda client: # record 41 dn: CN=win-client345,OU=Machines,DC=ad,DC=domain,DC=tld servicePrincipalName: HOST/MB38W746-0009 servicePrincipalName: HOST/MB38W746-0009.ad.domain.tld
2019 Mar 13
1
SPN and case sensitivity on LMDB backend
Hi everyone, samba-tool dbcheck --reindex Re-indexing... ../ldb_tdb/ldb_index.c:2352: duplicate attribute value in CN=WSTEST,OU=vm,OU=computers,OU=test,DC=ad,DC=test,DC=it for index on servicePrincipalName, duplicate of objectGUID 4c723426-73f8-4991-bf95-88eb57840c2c in @INDEX:SERVICEPRINCIPALNAME:TERMSRV/WSTEST.AD.TEST.IT Looking at the computer entry, I indeed have thoses two SPN (notice
2020 Oct 23
2
Problem with samba-tool --reindex
Hi, I have 2 DC's. One is running 4.10.18 and the other is running 4.11.14. I am planning on upgrading the 4.10.18 DC to 4.11.14 and then both up to 4.12r.latest. In doing this I ran samba-tool dbcheck --reindex and got the following warning: (vdc1 pts8) # samba-tool dbcheck --reindex Re-indexing... ../../lib/ldb/ldb_key_value/ldb_kv_index.c:2413: duplicate attribute value in
2023 Apr 04
1
[EXTERNAL] Fwd: ntlm_auth and freeradius
On Tue, 2023-04-04 at 09:37 +0200, Kees van Vloten wrote: > Op 04-04-2023 om 00:32 schreef Andrew Bartlett: > > > > > On Mon, 2023-04-03 at 15:08 +0000, Tim ODriscoll via samba wrote: > > > > > Unfortunately it's still erroring out: > > > (7) mschap: Creating challenge hash with username: host/SL-6S4BBS3.MYDOMAIN.co.uk > > > (7) mschap:
2020 Oct 23
1
Problem with samba-tool --reindex
On Fri, 23 Oct 2020, Rowland penny via samba wrote: > On 23/10/2020 15:03, Tom Diehl via samba wrote: >> Hi, >> >> I have 2 DC's. One is running 4.10.18 and the other is running 4.11.14. >> I am planning on upgrading the 4.10.18 DC to 4.11.14 and then both up to >> 4.12r.latest. >> >> In doing this I ran samba-tool dbcheck --reindex and got