There are a number of possible ways this could simply be misconfigured. If you are confident you have satisfied all the set up requirements do read on; otherwise you might need to divulge a few more details about your account, credentials, login_mode settings and mappings.

There have been a number of recent corrections made to integrated logins. Some of those are available in the latest patch for 12.0.1; identified as EBF 25390: 12.0.1 SP95 Build 4314. You might want to test with that to see if that addresses your issue. Another fix is still pending but, so far, I haven't identified if you have that issue or not.

Information about your specific 12.0.1 build may be important.

So more accurately this is a cross domain implentation. If this is being managed for you using Active Directory Service then that should be transpared (I beleive); so maybe you just need to set the "integrated server name" option to fix this.

If you are not using Active Directory(ADS) read on . . . hopefully it will help some . . .

So you could be using a Pre-ADS implementation and may be hitting a fundamental barrier here.

* * * From my limited understanding of Windows security ...* * * My understanding is, currently,

• we only support one 'domain' at a time; which can be either a single NT Domain or Active Directory [see the "integrated server name" option]
• and that both the client and the server must see the same profile [see "Network aspects of integrated logins"

I believe only Active Directory can be used to achieve.

Hopefully someone who has a better answer or work around will correct me on this ...