Busy search fails when Active Directory name is not equal to iDomain

  • 3492324
  • 09-Mar-2007
  • 26-Apr-2012

Environment

Novell GroupWise 7
Novell GroupWise 6.5
Novell GroupWise Gateway - 7.1 Gateway for MS Exchange

Situation

Busy Search fails from GroupWise user to Exchange user
Logs show no errors but user sees not results returned
Biderectional busy search fails from GroupWise to Exchange

Resolution

The busy search for GroupWise users on Exchange users fails if the the primary Internet domain list in the SMTP address space does not match the Active Directory Name.
You can see the Active directory name in Active Directory Users and Computers Utility. The container is display in the left panel and is the parent container for the users directories. This Object name is the Active Directory Domain name.
In our current release of the Gateway the users need to have a primary SMTP space that matches this name for the busy seach to work. The LDAP queury will fail other wise and there for busy search will fail. If you change manually the SMTP address of the Exchange recipient from
iDomain name into AD domain name and repeat the busy search the busy search will return the correct results.
In most cases this is not set as your primary Internet domain on the SMTP address space for Exchange user and as a result Novell has corrected this code and will soon make it available.
This has been reported to development and will be available in a new build dated after 3-2-2007