
Hello,
Yoann,
Telnet command isn’t available from the root of the webadm VM appliance. When attempting using putty from my desktop the SSL port I have setup does not time out, it does only give a blank screen, but does not seem to time out.
I have set the servers.xml to the IP and port for that server, still it fails for the ldap proxy user access….It does state during the restart that it is connected to the ldap server
“Connected LDAP Server: SBS (192.168.x.x)”
Which is part of what is confusing me. Any other thoughts\ideas?
Best Regards,
--
You received this message because you are subscribed to a topic in the Google Groups "RCDevs Security Solutions - Technical" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/rcdevs-technical/lb7im2MnkUs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
rcdevs-technic...@googlegroups.com.
To post to this group, send email to
rcdevs-t...@googlegroups.com.
Visit this group at https://groups.google.com/group/rcdevs-technical.
For more options, visit https://groups.google.com/d/optout.
|
||||||||||||||
|
||||||||||||||
|
Here’s an update:
If I change to my 2nd Domain controller (not the Schema Master) it succeeds, but when I login I get the following errors:
Checking LDAP schema
Reading schema objectclasses... Ok
Reading schema attributes... Ok
Checking account objectclass... Missing
Checking group objectclass... Missing
Checking config objectclass... Missing
Checking data attribute... Missing
Checking settings attribute... Missing
Checking type attribute... Missing
Checking LDAP schema
Reading schema objectclasses... Ok
Reading schema attributes... Ok
Checking account objectclass... Missing
Checking group objectclass... Missing
Checking config objectclass... Missing
Checking data attribute... Missing
Checking settings attribute... Missing
Checking type attribute... Missing
Everything else says OK.
What am I missing here?
Best Regards,
Okay, so I determined that it was the port I was using for ldap on the primary DC was wrong….apparently it was not setup as I thought. Which allowed me to restart webadm with no error and accomplish getting the following: Checking LDAP schema
Reading schema objectclasses... Ok
Reading schema attributes... Ok
Checking account objectclass... Ok
Checking group objectclass... Ok
Checking config objectclass... Ok
Checking data attribute... Ok
Checking settings attribute... Ok
Checking type attribute... Ok
So my next dilemma is still:
Checking default LDAP objects
Checking domains container... Missing
Checking clients container... Missing
Checking optionsets container... Missing
Checking adminroles container... Missing
Checking mountpoints container... Missing
Checking webapps container... Missing
Checking websrvs container... Missing
These will not create, even if I change the proxyuser account to be the domain admin. Which is the account that would have been used in creting the original LDAP config on that server.
Thoughts while I continue to beat my head against this issue? (hopefully my ramblings will be helpful to someone else in the future to trouble shoot this same or similar issue) In the meantime, anyone got a pointer in the right direction for the above “missing” containers issue? They won’t create!
Best Regards,
|
||||||
|
|
|
--
# Find below the LDAP containers required by WebADM.
# Change the container's DN to fit your ldap tree base.
# WebADM AdminRoles container
adminroles_container "cn=AdminRoles,cn=WebADM,dc=yorcdevs,dc=com"
# WebADM Optionsets container
optionsets_container "cn=OptionSets,cn=WebADM,dc=yorcdevs,dc=com"
# WebApp configurations container
webapps_container "cn=WebApps,cn=WebADM,dc=yorcdevs,dc=com"
# WebSrv configurations container
websrvs_container "cn=WebSrvs,cn=WebADM,dc=yorcdevs,dc=com"
# Mount points container
mountpoints_container "cn=Mountpoints,cn=WebADM,dc=yorcdevs,dc=com"
# Domain and Trusts container
domains_container "cn=Domains,cn=WebADM,dc=yorcdevs,dc=com"
# Clients container
clients_container "cn=Clients,cn=WebADM,dc=yorcdevs,dc=com"
So I used adsiedit to create the base container for the WebADM. I did so through the LDAP connection. See SS below:


Once connected I create a new object\container and named it. I’m thinking you could probably change the permissions on it using ADUC but with domain admin as the super user it all succeeded and came back with OK.
I’ll continue to post in case I run into anything else. Yoann, you’ve been a big help and giving me the points in the direction I needed to connect the dots.
Thank You!
--