Brian K. Jones wrote:
Hi, Brian;sorry. I forgot to mention that I had already tried that, to no avail. "390" appears in a bunch of other places too, judging by the grep -r output. Changing adm.conf and restarting everything results in the same message as before -- "can't connect to DS on <old port num>". brian. Did you have a chance to try these steps? It's on our release notes... http://www.redhat.com/docs/manuals/dir-server/release-notes/ds71relnotes.html Changing the Directory Server port number on the Configuration Directory Server will lock you out of the console after the Directory Server is restarted When changing the port number, when you press Save, you will get a dialog explaining what is about to happen. If you choose to proceed with the change, and you restart the Directory Server, you will notice that the console does not work anymore. To make it work again, you will need to change the port number in the files serverroot/shared/config/ldap.conf and serverroot/shared/config/dbswitch.conf. You must do this on all systems that have a Directory Server being managed by the console. If the Configuration Directory Server is also your User/Group Directory Server, you must also update the User Directory entry in the Global Preferences. (154554) Thanks, --noriko On Tuesday 21 June 2005 12:01 pm, Mike Jackson wrote: |
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature