myITforum.com Community Forum myITforum.com Community Forum

Home  Forums  Blogs  Live Support chat  Search Articles  Wiki  FAQ  Email Lists  Register  Login  My Profile  Inbox  Address Book  My Subscription  My Forums 

Photo Gallery  Member List  Search  Calendars  FAQ  Ticket List  Log Out

All Forums RSS Feed Subscription:


  


ADAM issue

 
View related threads: (in this forum | in all forums)

Logged in as: Guest
  Printable Version
All Forums >> [Management Products] >> Active Directory and Group Policy >> ADAM issue Page: [1]
Login
Message << Older Topic   Newer Topic >>
ADAM issue - 6/5/2008 7:27:10 PM   
phenry194

 

Posts: 187
Score: 0
Joined: 3/30/2007
Status: offline
I'm working out of my league here, so please bear with me.  We are setting up encryption software and have a server to act as a host to the clients with the encryption installed.  Part of the requirement for the server is to have ADAM sp2 installed.  There is an adam client account that is a domain account, but it also acts as a service account that acts as a communicator between the client and adam on the server.  This allows adam to collect registered user accounts on the client so it can assist in password changes and the like.  Unfortunately, the application manager doesn't see these registered user accounts, only the machine accounts.  The vendor asked us to edit a client host file and put the ip address for a DC (initially the DC the application server authenticated to) and the name of the domain.  With that set up in the host file, it worked great and we could see the registered user accounts.  Then we tried an IP address for a different DC just for the heck of it to replace the other ip address.  We got the same results.  So it looks like for some reason, the client can't resolve to a DC, even though it authenticates against one every morning, without the host file telling it where one is.  If it can't resolve, then ADAM can't get the user GUID from AD and can't enter the information into the application manager.  We don't want to have to edit all the host files on the clients as that is really kind of a herky way to handle this, and the vendor says it is a network configuration problem, so they can't help.  They say they see this in multi-domain environments, but we are on our own domain.  We think that there might be a conflict with the fqdn vs. the common name of our domain with ADAM, but I'm pretty sure we used the fqdn when setting up adam.  Is there any way we can check those settings in adam?  I know very little about adam, so I don't know where to look with the possible exception of adsiedit for adam, but then what do I check there?  anybody have any ideas on what steps I can take on this one or what may be causing the problem?  Thanks.  : )
Post #: 1
Page:   [1]
All Forums >> [Management Products] >> Active Directory and Group Policy >> ADAM issue Page: [1]
Jump to:





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts



  
Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.703