baldnva4
Contributor
Contributor

Active Directory Connection -- Incomplete

Hello Everyone,

We are in the process of trying to update to App Volumes 3.0 and currently are having issues getting the Active Directory connection up and running completely. We start going through the steps to do the initial setup of the App Volumes appliance only to get stuck at the AD connection. We put in the Super Admin (AD Group) and give the system a user/pass to query AD, but it comes back with a status of incomplete (even though it excepts everything that we put in).

1. We can log in with AD credentials

2. We have added the AD certificates to the .pem file

3. Added the Root / Sub certificates to the .pem file

We are stuck here. Can anyone shed some light on the issue in which we are having. Any help is greatly appreciated.

Thank you,

0 Kudos
12 Replies
Smoke14
Hot Shot
Hot Shot

Did you fill out the syntax like this, in all fields?

AV3-004.png

This worked for me multiple times.

Mike_A
0 Kudos
VentziP
Enthusiast
Enthusiast

We have similar problem with AD Connection regarding NetBIOS entry. We are getting this error message and setup is not going any further.

error.jpg

Why is actually needed NetBIOS name?

Thanks

0 Kudos
oelroos
Contributor
Contributor

I worked with support and found out that the documentation is inaccurate.

the problem is in the first two fields:

NETBIOS Name: use your domain (ex: domain.com)

DNS Domain Name: also use your domain (ex: domain.com) the documentation tells you to use the domain controller; that won't work.

0 Kudos
baldnva4
Contributor
Contributor

We have to use LDAPS. But I will change the information based on what you entered below to see if it works.

0 Kudos
VentziP
Enthusiast
Enthusiast

If I entered exactly like you suggested I got this error this time:

error2.jpg

Then I start playing with a different combinations and

The way worked for me was that I enter in these 2 fields the following:

NETBIOS Name: just a domain name (no .com at the end)

DNS Domain Name: I used the domain as (domain.com).

Thanks for your help.

0 Kudos
Jason_Marshall
VMware Employee
VMware Employee

‌you may need to redeploy the OVA if the AD info was corrupted. Please try to redeploy and enter in the info as described In the previous posts.

0 Kudos
baldnva4
Contributor
Contributor

Entering the information as requested did not work.

0 Kudos
baldnva4
Contributor
Contributor

We have redeployed the OVA several times now. It does not seem to make a difference.

0 Kudos
DougStorms
Contributor
Contributor

I am in a somewhat similar situation, can seemingly make the domain bind work and add the domain security group but when

I try to log back in with the account I made the bind with- I cannot
I have managed to log in with another a/c but the AD roles & Permissions section is not complete.

Nothing I do will complete that section.

I have re-deployed 5/6 times.

the documentation is not very clear.

Wondering if special characters in the password of the A/C that made the bind is an issue. !

0 Kudos
DougStorms
Contributor
Contributor

My mistake.

Did not fill in the domain name of the appliance properly during the install.

0 Kudos
Lyghtnin
Enthusiast
Enthusiast

I had the same issue with the Netbios name - here is where you can find it - in your AD just right click your domain and then properties, you'll get the following:

pastedImage_0.png

0 Kudos
baldnva4
Contributor
Contributor

In talking with support and our account team. This is an issue with Secure LDAP and they are working to get a fix out for it. If I hear anything else back, I will let everyone know.

0 Kudos