I have set up an AD/AM server on our network to provide address book
information for remote users. It works great for users that are
connected to our campus network, but if you attempt to authenticate
using the Windows Address Book from a computer that is not joined to
the domain (or joined to a different domain) the authentication fails.
There was some discussion on this in the Active Directory group he

http://groups.google.com/group/micro...a2b10d86?hl=en

Let's say our domain is CAMPUS, and I have a user account named aaron
(CAMPUS\aaron). If I'm logged in to my workstation here on campus and
use Windows Address Book (WAB) to access the directory using my
CAMPUS\aaron username/password, it works fine. But, if I go home and
log in to my local home network with a domain of HOME, and then
configure WAB on that machine to authenticate using the same
CAMPUS\aaron username/password, WAB will instead use my HOME domain
username and password in it's authentication INSTEAD of the username
and password that I have told it to use.... I know this from looking
at a packet dump of the traffic.

Anyone know what might cause this or what I can do to correct it?