Hmmm. Okay then, given that's the case I still cannot understand why I cannot edit my session entries from the other domain. My data sources are all set the same (AD integrated) and reference the exact same SQL database. I can edit anything while using the RDM client to access the database from anywhere in domain A but NOT from domain B. I can access any session entry from either domain A or B with no issues - I cannot edit from B however. As given previously I need to be able to force the client to look to another domain for AD verification, as it seems that the client will only look to the current domain for this - which is standard AD behaviour. It is strange however that I seem to be able to authenticate to domain A fine upon accessing the database from domain B, but not when trying to edit an entry? It cannot be SQL edit permissions, since I have those permissions and have no trouble using the same account from domain A to both access and edit. Just seems odd that for accessing the DB it works but not when trying to edit, which makes me think the RDM client is taking a different approach to authenticate when trying to edit a session.
↧