[cisco-voip] AD plugin issue

[Walenta, Phil]

Well slight improvement, but still something wrong I think:
 
49: May 16 15:14:14.516 CDT %UserPreference-6-UNK:*********************
 DIRUSER CONNECTED TO ldap://s-ecb-ns1.cvtc.local:3268
**************************
50: May 16 15:14:14.532 CDT %UserPreference-6-UNK:The Paged Control is
available & will be used
51: May 16 15:14:14.532 CDT %UserPreference-6-UNK:Search Attribute
getting used is sAMAccountName
52: May 16 15:14:14.532 CDT %UserPreference-6-UNK:Exit DirUser<1>
53: May 16 15:14:14.626 CDT %UserPreference-6-UNK:Enter getDNForUserId
<1>
54: May 16 15:14:14.626 CDT %UserPreference-6-UNK:Enter getDNForUserId
<2>
55: May 16 15:14:14.641 CDT %UserPreference-6-UNK:Error getDNForUserId
<2>
56: May 16 15:14:14.641 CDT
%UserPreference-3-UNK:javax.naming.NamingException: [LDAP: error code 1
- 000020D6: SvcErr: DSID-031006C5, problem 5012 (DIR_ERROR), data 0
 ]; remaining name 'ou=Users,o=cisco.com'
 at com.sun.jndi.ldap.LdapCtx.mapErrorCode(Unknown Source)
 at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source)
 at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source)
 at com.sun.jndi.ldap.LdapCtx.searchAux(Unknown Source)
 at com.sun.jndi.ldap.LdapCtx.c_search(Unknown Source)
 at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(Unknown
Source)
 at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(Unknown
Source)
 at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(Unknown
Source)
 at javax.naming.directory.InitialDirContext.search(Unknown Source)
 at DirUser.DirUser.getDNForUserId(DirUser.java:12871)
 at DirUser.DirUser.getDNForUserId(DirUser.java:12946)
 at DirUser.DirUser.getUserHandleFromUserId(DirUser.java:12703)
 at com.cisco.ma.dirdata.GetBlobRequest.run(GetBlobRequest.java:33)
 at
com.cisco.ma.dirdata.Thread_pool$Pooled_thread.run(Thread_pool.java:108)
 
 

________________________________

From: Kevin Thorngren [mailto:kevint at cisco.com] 
Sent: Tuesday, May 17, 2005 3:05 PM
To: Walenta, Phil
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] AD plugin issue


Yes, rerun the plugin and point it to the Global Catalog server and use
port 3268 instead of 389. 
On May 17, 2005, at 3:59 PM, Walenta, Phil wrote: 


	So do I re-run my AD integration pointing it to 3268 then? 


	From: Kevin Thorngren [mailto:kevint at cisco.com] 
	Sent: Tuesday, May 17, 2005 2:55 PM 
	To: Walenta, Phil 
	Cc: cisco-voip at puck.nether.net 
	Subject: Re: [cisco-voip] AD plugin issue 

	Hi Phil, 


	It looks like the LDAP query is receiving a referral to
cvtc.local on port 389. This server seems to be refusing the connection:



	Caused by: javax.naming.CommunicationException: cvtc.local:389
[Root exception is java.net.ConnectException: Connection refused:
connect] 
	 at com.sun.jndi.ldap.LdapReferralContext.<init>(Unknown Source)

	You can collect a packet capture to get more detail of what is
happening. The referral seems to be pointing to a server that does not
have TCP port 389 open. One option is to point the CCM to a GC using
port 3268. The GC owns all objects and won't return referrals. Or you
will need to find out why the referred server is not responding
correctly. 


	HTH, 
	Kevin 


	On May 17, 2005, at 3:36 PM, Walenta, Phil wrote: 


	Has anyone had a problem with their AD plugin that looks like
this?  The user is there, I just don't know why it can't be accessed. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20050517/4264b0ac/attachment.html