Thanks for the info.  I have tried just about everything at this point.  I
am beginning to think that either the connectionName or password I have been
given is incorrect.  I am trying to track that down now.


Thanks again.

-----Original Message-----
From: Jeff Tulley [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 09, 2003 2:22 PM
To: [EMAIL PROTECTED]
Subject: Re: Tomcat and Active Directory


So maybe it is just my lack of understanding of Active Directory(working
for Novell, I'm prejudiced towards Novell eDirectory, of course), but
usually in my connectionURL, I put something of the form,
"ldap://myhost:636";  Changing that to "ldaps" usually doesn't work for
me, and the whole "/ou=migrated....." stuff at the end is not there.  Is
that unique to Active Directory, or is it just wrong to have it there
and that is what is causing your problems?

I've noticed that Tomcat sometimes tries to connect to :389 even though
:636 is in the connectionURL, when something is wrong in the
configuration.  Try a smaller connection url,
"ldap://nmr001dundom01:636";, and then put your user info into the other
fields -- userPattern, or userBase, etc.

Jeff Tulley  ([EMAIL PROTECTED])
(801)861-5322
Novell, Inc., The Leading Provider of Net Business Solutions
http://www.novell.com

>>> [EMAIL PROTECTED] 9/9/03 9:40:48 AM >>>
You won't get an intelligent response if you enter your LDAP URL into a
web
browser, but many email clients are LDAP-compatible (e.g. Outlook
Express -
add an LDAP link via the Tools\Accounts menu).  Also, you can try an
LDAP
browser, such as the one at http://www.iit.edu/~gawojar/ldap.  Another
suggestion which you can try right now is to change the "ldap" to
"ldaps" in
the URL - port 636 is the SSL port for LDAP.

----- Original Message ----- 
From: "Srofe, Douglas (c)" <[EMAIL PROTECTED]>
To: "'Tomcat Users List'" <[EMAIL PROTECTED]>
Sent: Tuesday, September 09, 2003 4:31 PM
Subject: RE: Tomcat and Active Directory


>
> Thanks for your response.  I have changed the url to the following:
>
> connectionURL="ldap://nmr001dundom01:636/ou=migrated
> users,ou=nmr,dc=enterprisenet,dc=org"
>
> Our admin said to use port 636.
>
> However, I still get the same error saying it can't connect to
> localhost:389.
>
> As a test, should I be able to enter that url in the browser and get
> something meaningful?
>
> Thanks again.
>
> -----Original Message-----
> From: Christopher Williams [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, September 09, 2003 10:55 AM
> To: Tomcat Users List
> Subject: Re: Tomcat and Active Directory
>
>
> There's just been a similar question answered.  The URL to your
Active
> Directory appears to be wrong - after all I'm guessing that Active
Directory
> is not running on your development system.  Change the URL to:
> ldap://server.name:389/ou=migrated users...
>
> and you might have some success.
>
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED] 
> For additional commands, e-mail: [EMAIL PROTECTED]

>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED] 
> For additional commands, e-mail: [EMAIL PROTECTED]

>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] 
For additional commands, e-mail: [EMAIL PROTECTED] 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to