Also if your forest is sizable, using honest LDAP in AD is quite
slow. When using standard LDAP port TCP 386, AD will traverse the
forest to get the real information instead of the cached information
at your local domain controller (DC). If your network has choke
points, this can take 10 minutes to return as has been my
experience. This locks up the address book which eventually blocks
on the retrieval thread execution.
The bad news is that using the Global Catalogue (GC) you are using
whatever managed to get replicated. AD is notorious for replication
errors usually in omissions.
Very Respectfully,
Wm. Cerniuk
Project Manager / Sr. Systems Architect
Veterans Affairs
877.529.5730 (toll free)
Time is Short, and the Water Rises
On Aug 21, 2007, at 1:47 PM, Timothy J. Miller wrote:
On Aug 21, 2007, at 12:15 PM, Robert Kerr wrote:
Has anyone in the Air Force had any luck with getting the Address
Book to
work on the network. I have tried many settings but have not been
able to
get it to connect and pull down the addresses.
If you have had luck let me know what you are using for the settings.
AD denies null binding on LDAP ports by default. You should be
able to use the global catalog port (3268) on a GC server instead.
-- Tim
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Fed-talk mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Fed-talk mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
