Hi Gerrard,
Unfortunately it doesn't. I tried to login as the admin user using the
fqdn. The debug console output gives me:
389-Management-Console/1.1.5 B2010.123.2251
CommManager> New CommRecord
(
http://bla.blablabla.bla:9830/admin-serv/authenticate)
http://bla.blablabla.bla:9830/[0:0] open> Ready
http://bla.blablabla.bla:9830/[0:0] accept>
http://bla.blablabla.bla:9830/admin-serv/authenticate
http://bla.blablabla.bla:9830/[0:0] send> GET \
http://bla.blablabla.bla:9830/[0:0] send> /admin-serv/authenticate \
http://bla.blablabla.bla:9830/[0:0] send> HTTP/1.0
http://bla.blablabla.bla:9830/[0:0] send> Host: bla.blablabla.bla:9830
http://bla.blablabla.bla:9830/[0:0] send> Connection: Keep-Alive
http://bla.blablabla.bla:9830/[0:0] send> User-Agent:
389-Management-Console/1.1.5
http://bla.blablabla.bla:9830/[0:0] send> Accept-Language: en
http://bla.blablabla.bla:9830/[0:0] send> Authorization: Basic \
http://bla.blablabla.bla:9830/[0:0] send> YWRtaW46U1VSRm5ldDIwMTA= \
http://bla.blablabla.bla:9830/[0:0] send>
http://bla.blablabla.bla:9830/[0:0] send>
http://bla.blablabla.bla:9830/[0:0] recv> HTTP/1.1 401 Authorization
Required
http://bla.blablabla.bla:9830/[0:0] error> HttpException:
Response: HTTP/1.1 401 Authorization Required
Status: 401
URL:
http://bla.blablabla.bla:9830/admin-serv/authenticate
http://<our>.<testserver>.<suffix>:9830/[0:0] close> Closed
/var/log/dirsrv/admin-serv/error:
[Mon Nov 29 10:48:07 2010] [crit] openLDAPConnection(): util_ldap_init
failed for ldap://:389
[Mon Nov 29 10:48:07 2010] [warn] Unable to open initial LDAPConnection
to populate LocalAdmin tasks into cache.
[Mon Nov 29 10:48:08 2010] [notice] Apache/2.2.17 (Unix) configured --
resuming normal operations
[Mon Nov 29 10:48:08 2010] [crit] openLDAPConnection(): util_ldap_init
failed for ldap://:389
[Mon Nov 29 10:48:08 2010] [warn] Unable to open initial LDAPConnection
to populate LocalAdmin tasks into cache.
[Mon Nov 29 10:48:51 2010] [notice] [client xxx.xx.xxx.xx]
admserv_host_ip_check: Unauthorized host ip=xxx.xx.xxx.xx, connection
rejected
Kind regards,
Eric
Gerrard Geldenhuis wrote:
Hi Eric, As a start always use the fqdn of the host rather than
127.0.0.1 when connecting via the console. Secondly, 389-console has
a debug flag available that you can use while connecting that will
shed additional light on any other problems that may be causing
issues.
Regards
--
Eric Donkersloot
SURFnet
Radboudkwartier 273
3511 CK Utrecht
M +31 6 4115 4547
eric.donkersloot(a)surfnet.nl