[cisco-voip] AD plugin issue

[Kevin Thorngren]

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 --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 2147 bytes
Desc: not available
Url : https://puck.nether.net/pipermail/cisco-voip/attachments/20050517/da9ea091/attachment.bin