Quantcast
Channel: Software Communities : Popular Discussions - All Things Unix
Viewing all articles
Browse latest Browse all 1046

Failed getting defaultNamingContext for domain

$
0
0
Hi,

I'm trying to setup mod_auth_vas on RHEL5. The box is running vasclnt-3.3.1-94.
While running the setup-mod_auth_vas script to create the service account, I get the following error:

2008-05-26 17:17:06: _is_nss_mapped_user: pwd ptr was NULL for adadmin Password for adadmin@SOMEAD.DOM.COM:
2008-05-26 17:17:14: vasadmin_service_create: Creating service account for HTTP/myserver.fqdn.com@SOMEAD.DOM.COM
2008-05-26 17:17:15: _is_nss_mapped_user: pwd ptr was NULL for myserver-HTTP
2008-05-26 17:17:15: vasadmin_service_create: Service account created for upn HTTP/myserver.fqdn.com@SOMEAD.DOM.COM
2008-05-26 17:17:15: vasadmin_service_create: Creating keytab for HTTP/myserver.fqdn.com@SOMEAD.DOM.COM at /etc/opt/quest/vas/HTTP.keytab
2008-05-26 17:17:15: libvas_attrs_get_rootDSE_attr: vas_attrs_find() failed, result=4(VAS_ERR_LDAP: Unable to connect to any server that matches uri: "DC://@adroot.dom.com" for domain: ADroot.dom.com
Caused by:
LDAP: Could not connect to LDAP server)
ERROR: Service creation failed for upn "HTTP/"
VAS_ERR_LDAP: Failed getting defaultNamingContext for domain adroot.dom.com

Our AD infrastructure includes a Root and Child domain. My server is joined to the Child domain.

Has anybody experienced difficulties getting the HTTP.keytab (in this case) or NFS.keytab created with such type of AD setup (Root and Child domains)?

Thanks for your feedback,

Viewing all articles
Browse latest Browse all 1046

Trending Articles