NextCloud LDAP Error
-
@Dashrender said in NextCloud LDAP Error:
@scottalanmiller said in NextCloud LDAP Error:
@wirestyle22 said in NextCloud LDAP Error:
@scottalanmiller said in NextCloud LDAP Error:
@wirestyle22 said in NextCloud LDAP Error:
@scottalanmiller said in NextCloud LDAP Error:
@wirestyle22 said in NextCloud LDAP Error:
@scottalanmiller said in NextCloud LDAP Error:
Start with... what is the base of your AD?
CN=<username>,CN=FCC,CN=Divison of Information Technology,CN=administration,CN=Departments,DC=domaincontroller.domain,DC=orgSo when you join a Windows desktop to the domain, you put domaincontroller.domain.org?
That's not normal.
I tried it both ways
Before we try things, let's be systematic. What do you put onto Windows machines to do this? Ignore NextCloud for the moment.
The last time I've ever had to do anything with LDAP was like 7 years ago working at the hospital. It's been a really long time for me.
So you are joining NextCloud to AD that you've never even joined a Windows desktop to? What's the NAME of your AD Domain?
Right.
Let's assume we are talking about NTG here. They domainname might be ntg.co so when adding a computer, you would type in ntg.co, not servername.ntg.co
Or more commonly, because that would be a blunder that NTG would not make, it would be something like ad.ntg.co as the domain and a DC would be something like ny-win-dc1.ad.ntg.co.
-
@scottalanmiller said in NextCloud LDAP Error:
@Dashrender said in NextCloud LDAP Error:
@scottalanmiller said in NextCloud LDAP Error:
@wirestyle22 said in NextCloud LDAP Error:
@scottalanmiller said in NextCloud LDAP Error:
@wirestyle22 said in NextCloud LDAP Error:
@scottalanmiller said in NextCloud LDAP Error:
@wirestyle22 said in NextCloud LDAP Error:
@scottalanmiller said in NextCloud LDAP Error:
Start with... what is the base of your AD?
CN=<username>,CN=FCC,CN=Divison of Information Technology,CN=administration,CN=Departments,DC=domaincontroller.domain,DC=orgSo when you join a Windows desktop to the domain, you put domaincontroller.domain.org?
That's not normal.
I tried it both ways
Before we try things, let's be systematic. What do you put onto Windows machines to do this? Ignore NextCloud for the moment.
The last time I've ever had to do anything with LDAP was like 7 years ago working at the hospital. It's been a really long time for me.
So you are joining NextCloud to AD that you've never even joined a Windows desktop to? What's the NAME of your AD Domain?
Right.
Let's assume we are talking about NTG here. They domainname might be ntg.co so when adding a computer, you would type in ntg.co, not servername.ntg.co
Or more commonly, because that would be a blunder that NTG would not make, it would be something like ad.ntg.co as the domain and a DC would be something like ny-win-dc1.ad.ntg.co.
Correct the current Microsoft recommended standard is ad.yourrealdomain.tld
The old standard of domain.local has been not a standard for years and years.
So my test AD infrastructure (because we do not use AD for anything real) is ad.bundystl.com and the DC is bundydc01.ad.bundystl.com
-
@JaredBusch said in NextCloud LDAP Error:
@scottalanmiller said in NextCloud LDAP Error:
@Dashrender said in NextCloud LDAP Error:
@scottalanmiller said in NextCloud LDAP Error:
@wirestyle22 said in NextCloud LDAP Error:
@scottalanmiller said in NextCloud LDAP Error:
@wirestyle22 said in NextCloud LDAP Error:
@scottalanmiller said in NextCloud LDAP Error:
@wirestyle22 said in NextCloud LDAP Error:
@scottalanmiller said in NextCloud LDAP Error:
Start with... what is the base of your AD?
CN=<username>,CN=FCC,CN=Divison of Information Technology,CN=administration,CN=Departments,DC=domaincontroller.domain,DC=orgSo when you join a Windows desktop to the domain, you put domaincontroller.domain.org?
That's not normal.
I tried it both ways
Before we try things, let's be systematic. What do you put onto Windows machines to do this? Ignore NextCloud for the moment.
The last time I've ever had to do anything with LDAP was like 7 years ago working at the hospital. It's been a really long time for me.
So you are joining NextCloud to AD that you've never even joined a Windows desktop to? What's the NAME of your AD Domain?
Right.
Let's assume we are talking about NTG here. They domainname might be ntg.co so when adding a computer, you would type in ntg.co, not servername.ntg.co
Or more commonly, because that would be a blunder that NTG would not make, it would be something like ad.ntg.co as the domain and a DC would be something like ny-win-dc1.ad.ntg.co.
Correct the current Microsoft recommended standard is ad.yourrealdomain.tld
The old standard of domain.local has been not a standard for years and years.
So my test AD infrastructure (because we do not use AD for anything real) is ad.bundystl.com and the DC is bundydc01.ad.bundystl.com
I do the same even for my Linux stuff. My house is pa.jhbcomputers.com
-
@stacksofplates said in NextCloud LDAP Error:
@JaredBusch said in NextCloud LDAP Error:
@scottalanmiller said in NextCloud LDAP Error:
@Dashrender said in NextCloud LDAP Error:
@scottalanmiller said in NextCloud LDAP Error:
@wirestyle22 said in NextCloud LDAP Error:
@scottalanmiller said in NextCloud LDAP Error:
@wirestyle22 said in NextCloud LDAP Error:
@scottalanmiller said in NextCloud LDAP Error:
@wirestyle22 said in NextCloud LDAP Error:
@scottalanmiller said in NextCloud LDAP Error:
Start with... what is the base of your AD?
CN=<username>,CN=FCC,CN=Divison of Information Technology,CN=administration,CN=Departments,DC=domaincontroller.domain,DC=orgSo when you join a Windows desktop to the domain, you put domaincontroller.domain.org?
That's not normal.
I tried it both ways
Before we try things, let's be systematic. What do you put onto Windows machines to do this? Ignore NextCloud for the moment.
The last time I've ever had to do anything with LDAP was like 7 years ago working at the hospital. It's been a really long time for me.
So you are joining NextCloud to AD that you've never even joined a Windows desktop to? What's the NAME of your AD Domain?
Right.
Let's assume we are talking about NTG here. They domainname might be ntg.co so when adding a computer, you would type in ntg.co, not servername.ntg.co
Or more commonly, because that would be a blunder that NTG would not make, it would be something like ad.ntg.co as the domain and a DC would be something like ny-win-dc1.ad.ntg.co.
Correct the current Microsoft recommended standard is ad.yourrealdomain.tld
The old standard of domain.local has been not a standard for years and years.
So my test AD infrastructure (because we do not use AD for anything real) is ad.bundystl.com and the DC is bundydc01.ad.bundystl.com
I do the same even for my Linux stuff. My house is pa.jhbcomputers.com
any linux server on the network with my AD environment are setup as nc.ad.bundystl.com for example.
-
I apologize for not coming back. Came home to a power outage last night unfortunately.
For some reason they have two separate domains--one for e-mail and one for everything else. This was set up by the company before us. My company has basically been trying to undo the misconfigurations over time as the state allows.
Side note: Government is even more strict fiscally than the non-profits I've worked for. Getting them to even purchase a google domain for the web server is difficult.
-
Let us know when you are ready to tackle this again.
-
I'm "ready". I'm wondering if my boss set this to require SSL or something. I sent an e-mail asking.
-
@wirestyle22 said in NextCloud LDAP Error:
I'm "ready". I'm wondering if my boss set this to require SSL or something. I sent an e-mail asking.
Set what to require SSL? AD authentication? It should be using Kerberos I would think. (note - Kerberos might be wrong here).
What version of Windows Server are you using? what Domain/Forest levels are you at?
-
@Dashrender said in NextCloud LDAP Error:
@wirestyle22 said in NextCloud LDAP Error:
I'm "ready". I'm wondering if my boss set this to require SSL or something. I sent an e-mail asking.
Set what to require SSL? AD authentication? It should be using Kerberos I would think. (note - Kerberos might be wrong here).
What version of Windows Server are you using? what Domain/Forest levels are you at?
https://s28.postimg.org/cvzn90xjx/ldapssl.jpg?2
2008 R2. Root domain
I attempted to do this on port 636 for SSL but it still didn't work.
Always comes back with the Base DN appears to be wrong.
-
Can this be an issue with LDAP server signing requirements?
"If you set the server to Require Signature, you must also set the client. Not setting the client results in loss of connection with the server."
-
@wirestyle22 said in NextCloud LDAP Error:
Can this be an issue with LDAP server signing requirements?
"If you set the server to Require Signature, you must also set the client. Not setting the client results in loss of connection with the server."
Yes
-
i'm going to spin up a Server 2008 R2 VM tonight and attempt to create all of this.
-
@wirestyle22 said in NextCloud LDAP Error:
i'm going to spin up a Server 2008 R2 VM tonight and attempt to create all of this.
Why something so old?
-
@scottalanmiller said in NextCloud LDAP Error:
@wirestyle22 said in NextCloud LDAP Error:
i'm going to spin up a Server 2008 R2 VM tonight and attempt to create all of this.
Why something so old?
They don't want to spend money. That is the OS version we are running.
-
@wirestyle22 said in NextCloud LDAP Error:
@scottalanmiller said in NextCloud LDAP Error:
@wirestyle22 said in NextCloud LDAP Error:
i'm going to spin up a Server 2008 R2 VM tonight and attempt to create all of this.
Why something so old?
They don't want to spend money. That is the OS version we are running.
Ouch.
-
@wirestyle22 said in NextCloud LDAP Error:
@scottalanmiller said in NextCloud LDAP Error:
@wirestyle22 said in NextCloud LDAP Error:
i'm going to spin up a Server 2008 R2 VM tonight and attempt to create all of this.
Why something so old?
They don't want to spend money. That is the OS version we are running.
Better start telling them now that 2008 R2 support (i.e. security updates) is almost over.
Just a hair over 3 years, just like Windows 7.
-
@wirestyle22 said in NextCloud LDAP Error:
@scottalanmiller said in NextCloud LDAP Error:
@wirestyle22 said in NextCloud LDAP Error:
i'm going to spin up a Server 2008 R2 VM tonight and attempt to create all of this.
Why something so old?
They don't want to spend money. That is the OS version we are running.
If they didn't want to spend money, they'd be running on Linux for AD since 2008 R2 functionality is free. Running on Windows means that they want to spend money. Nothing wrong with running Windows, but there is something wrong with running anything you can't afford to maintain.
-
@Dashrender That's SQL Server. And SQL Server 2008 is much older than Windows Server 2008 R2 (which is 2010.)
-
Tell them this now! It's only 2.7 years away. That will be here before you know it. Who knows how long you'll need to prepare migrations, etc.
-
@scottalanmiller said in NextCloud LDAP Error:
@Dashrender That's SQL Server. And SQL Server 2008 is much older than Windows Server 2008 R2 (which is 2010.)
Updated.
