<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=204145919-17052005>So do I re-run my AD integration pointing it to 3268
then?</SPAN></FONT></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Kevin Thorngren [mailto:kevint@cisco.com]
<BR><B>Sent:</B> Tuesday, May 17, 2005 2:55 PM<BR><B>To:</B> Walenta,
Phil<BR><B>Cc:</B> cisco-voip@puck.nether.net<BR><B>Subject:</B> Re:
[cisco-voip] AD plugin issue<BR></FONT><BR></DIV>
<DIV></DIV><!-- Converted from text/enriched format -->
<DIV>Hi Phil, </DIV><BR>
<DIV>It looks like the LDAP query is receiving a referral to cvtc.local on port
389. This server seems to be refusing the connection: </DIV><BR>
<DIV>Caused by: javax.naming.CommunicationException: cvtc.local:389 [Root
exception is java.net.ConnectException: Connection refused: connect] </DIV>
<DIV> at com.sun.jndi.ldap.LdapReferralContext.<init>(Unknown Source)
</DIV>
<DIV> </DIV>
<DIV>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. </DIV><BR>
<DIV>HTH, </DIV>
<DIV>Kevin </DIV><BR>
<DIV>On May 17, 2005, at 3:36 PM, Walenta, Phil wrote: </DIV><BR>
<BLOCKQUOTE>
<DIV><FONT face=Arial><SMALL>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.</SMALL></FONT> </DIV></BLOCKQUOTE></BODY></HTML>