Any SQL Experts in the House?

[GregE240]

Got a wee problem I can't get my head around.

We've got a SQL server in an NT4 resource domain. Users connect to databases on it from NT4 account domains. Lets call them domain A and Domain B. Users from A can access the box fine, but users from B cannot. If I strip out the domain prefix from users in Domain B, it works a treat?

Note the SQL server is using NT authentication.

Any ideas would be really helpful because I'm scratching my head here big time....

Thanks,
Greg

[anonymous-user]

Trust relationships between the NT domains?

[Don]

LexSport said:

Trust relationships between the NT domains?

Got to be.

Do you have to use NT Authentication on the SQL Server? Lots of problems go away if you use a username/password....

[GregE240]

Thanks chaps.

Yes, there is a trust between the domains, but this must be working fine as users have their home drives on other servers in the same domain as the SQL server, and they are connecting fine.

If there was a problem with the trust I suspect they wouldn't get their O drives mapped.

The only thing I can think of is to remove the SQL server from the domain and re-add it, just to be sure?

[Don]

GregE240 said:

Thanks chaps. The only thing I can think of is to remove the SQL server from the domain and re-add it, just to be sure?

Its worth a shot, Greg. Is this pukka SQL Server or MSDE? MSDE can be a pain in the posterior and require unpleasant registry editing to get it to authenticate using username/password combinations and the NT Authentication thing seems to cause all sorts of grief.

Just in case the setting is

HKEY_LOCAL_MACHINE\Software\Microsoft\MSSqlServer\MSSqlServer\LoginMode = 0x2




>> Edited by Don on Tuesday 29th June 09:08

[GregE240]

Don said:

Its worth a shot, Greg. Is this pukka SQL Server or MSDE? MSDE can be a pain in the posterior and require unpleasant registry editing to get it to authenticate using username/password combinations and the NT Authentication thing seems to cause all sorts of grief. Just in case the setting is HKEY_LOCAL_MACHINESoftwareMicrosoftMSSqlServerMSSqlServerLoginMode = 0x2 >> Edited by Don on Tuesday 29th June 09:08

MSDE????? Don mate, this is a high street bank running a major business critical app my friend!!

Anyway, good news; I've sorted it. Within the same part of the registry is a key called "DefaultDomain". Bizarrely this was set to the domain that the users were failing from, and not the resource domain it should be in. Why? I've no idea. Anyhoo, I stopped SQL, changed it and restarted it, and it now works a treat.

Beer or wine next time I see you Don - thanks a million.

Greg

[sybaseian]

GregE240 said:

MSDE????? Don mate, this is a high street bank running a major business critical app my friend!! Greg

Are they mad?
Which bank? I can see me getting some extra money soon.....

[Don]

GregE240 said:

Beer or wine next time I see you Don - thanks a million. Greg

Cheers. Glad my random ramblings set you off in a direction that fixed it!