Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Administrators

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 11-29-2005, 03:47 PM
Active Member
 
Posts: 26
Default Active Directory GAL help

I need some help getting the GAL setup for my active directory domain. The domain is a Windows 2003 native domain. I follow the setup wizard and enter the binddn of administrator however when I test my GAL settings I get the following Check.FAILURE error:

Quote:
javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: ad.lsky.ca:389 [Root exception is java.net.UnknownHostException: ad.lsky.ca]]
at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImp l(LdapNamingEnumeration.java:224)
at com.sun.jndi.ldap.LdapNamingEnumeration.hasMore(Ld apNamingEnumeration.java:171)
at com.zimbra.cs.account.ldap.LdapUtil.searchLdapGal( LdapUtil.java:774)
at com.zimbra.cs.account.ldap.Check.checkGalConfig(Ch eck.java:190)
at com.zimbra.cs.service.admin.CheckGalConfig.handle( CheckGalConfig.java:58)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:249)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:163)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:84)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:226)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:709)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:148)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:802)
at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:214)
at org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invok e(StandardEngineValve.java:107)
at org.apache.catalina.valves.AccessLogValve.invoke(A ccessLogValve.java:526)
at org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(H ttp11Processor.java:825)
at org.apache.coyote.http11.Http11Protocol$Http11Conn ectionHandler.processConnection(Http11Protocol.jav a:738)
at org.apache.tomcat.util.net.PoolTcpEndpoint.process Socket(PoolTcpEndpoint.java:526)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThr ead.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlR unnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.naming.CommunicationException: ad.lsky.ca:389 [Root exception is java.net.UnknownHostException: ad.lsky.ca]
at com.sun.jndi.ldap.LdapReferralContext.<init>(LdapR eferralContext.java:74)
at com.sun.jndi.ldap.LdapReferralException.getReferra lContext(LdapReferralException.java:132)
at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreRef errals(LdapNamingEnumeration.java:339)
at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImp l(LdapNamingEnumeration.java:208)
... 26 more
Caused by: java.net.UnknownHostException: ad.lsky.ca
at java.net.PlainSocketImpl.connect(PlainSocketImpl.j ava:177)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.j ava:364)
at java.net.Socket.connect(Socket.java:507)
at sun.reflect.GeneratedMethodAccessor32.invoke(Unkno wn Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sun.jndi.ldap.Connection.createSocket(Connecti on.java:333)
at com.sun.jndi.ldap.Connection.<init>(Connection.jav a:181)
at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.jav a:118)
at com.sun.jndi.ldap.LdapClientFactory.createPooledCo nnection(LdapClientFactory.java:44)
at com.sun.jndi.ldap.pool.Connections.<init>(Connecti ons.java:97)
at com.sun.jndi.ldap.pool.Pool.getPooledConnection(Po ol.java:114)
at com.sun.jndi.ldap.LdapPoolManager.getLdapClient(Ld apPoolManager.java:310)
at com.sun.jndi.ldap.LdapClient.getInstance(LdapClien t.java:1572)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:259 6)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:283)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapC txFactory.java:175)
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstanc e(LdapCtxFactory.java:134)
at com.sun.jndi.url.ldap.ldapURLContextFactory.
And yes, I've read the adminos pdf and still no luck.

Last edited by jmeier; 11-29-2005 at 03:58 PM..
Reply With Quote
  #2 (permalink)  
Old 11-29-2005, 04:04 PM
Zimbra Employee
 
Posts: 2,103
Default host unknown

Can the zimbra box resolve the hostname you gave it?
java.net.UnknownHostException: ad.lsky.ca]]
Reply With Quote
  #3 (permalink)  
Old 11-30-2005, 07:12 AM
Active Member
 
Posts: 26
Default

Quote:
Originally Posted by marcmac
Can the zimbra box resolve the hostname you gave it?
java.net.UnknownHostException: ad.lsky.ca]]
Yes. I am able to do an ldapsearch on it as well as a zmprov.
Reply With Quote
  #4 (permalink)  
Old 11-30-2005, 07:56 AM
Zimbra Employee
 
Posts: 2,103
Default name resolution

Sometimes, the ldap commands will not use DNS, where the system will - can you run:
host <hostname> on that hostname, and verify that it resolves in DNS?
Reply With Quote
  #5 (permalink)  
Old 11-30-2005, 10:59 AM
Active Member
 
Posts: 26
Default

Quote:
Originally Posted by marcmac
Sometimes, the ldap commands will not use DNS, where the system will - can you run:
host <hostname> on that hostname, and verify that it resolves in DNS?
Would this also affect the authentication portion of the setup as well? because that works perfectly. In resolv.conf i have the IP address of the domain controller hosting ad.lsky.ca as the main domain server and I have verified that it works by performing nslookups.

If this is a DNS issue what else can I check to make sure everything is setup properly?

As far as the GAL setup goes I enter in my AD servers (in this case two, a primary and a backup - 10.196.161.10 and 10.196.161.11), I enter the bind dn of administrator@ad.lsky.ca.
Reply With Quote
  #6 (permalink)  
Old 11-30-2005, 11:11 AM
Zimbra Employee
 
Posts: 4,792
Default

Quote:
Originally Posted by jmeier
If this is a DNS issue what else can I check to make sure everything is setup properly?
On the Zimbra box run:


host ad.lsky.ca
__________________
Bugzilla - Wiki - Downloads - Offline Client
Reply With Quote
  #7 (permalink)  
Old 11-30-2005, 12:29 PM
Active Member
 
Posts: 26
Default

Quote:
Originally Posted by KevinH
On the Zimbra box run:


host ad.lsky.ca
[root@zimbra ~]# host ad.lsky.ca
ad.lsky.ca has address 10.196.161.10
ad.lsky.ca has address 10.196.161.11
Reply With Quote
  #8 (permalink)  
Old 11-30-2005, 12:42 PM
Zimbra Employee
 
Posts: 2,103
Default 2 addresses?

Why is it returning 2 addresses?
Reply With Quote
  #9 (permalink)  
Old 11-30-2005, 01:05 PM
Active Member
 
Posts: 26
Default

Quote:
Originally Posted by marcmac
Why is it returning 2 addresses?
Because I have a primary and backup domain controller. The problem is fixed now. I rebooted my domain controller an I am now able to search the GAL.
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.