Windows authentication failure

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2005 Forums

SQL Server Administration (2005)

Windows authentication failure

Author

Topic

DLTaylor
Posting Yak Master

136 Posts

Posted - 2010-06-08 : 09:03:16

Im stuck so i thought I’d try the best sql forum…i will welcome any ideas!!!!!

I have a windows user account used to access multiple SQL servers and run SQL services e.g….DOMAIN\account.

It has worked for many years… until now.

When I log onto SERVER1 as DOMAIN\account I can connect to SERVER1 or SERVER2 and Run tasks from both.

When I log onto SERVER2 as DOMAIN\account i can only connect to SERVER2 but not SERVER1 i get the error message;
‘Login failed for user’’. It is not associated with a trusted connection. (Microsoft SQL Server, Error: 18452)

SERVER2 allows me to connect to all other server e.g. SERVER3 etc… as normal – but the issue seems to be isolated to SERVER2 connecting to SERVER1 and the authentication failing….

Any advice on how I can jolt it back into working?

(I have restarted services and re saved the DOMAIN\account privileges)

DLTaylor
Posting Yak Master

136 Posts

Posted - 2010-06-08 : 10:21:53

I have found another user with the same issue....but no answer..
Has anyone else experienced this?

MachineA:
Windows XP Pro.
SQL Server 2005, Standard Edition
Machine on Domain XXX
User XXX\User1 is added to Administrators group

MachineB:
Windows XP Pro.
SQL Server 2005, Developer Edition
Machine on Domain XXX
User XXX\User1 is added to Adminitrators group

User1 logs onto MachineA and uses SQL Managment Studio to connect to database engine on MachineA (Local SQL Server), everything works. Then tries to connect to database engine on MachineB everything works.

User1 logs onto MachineB and uses SQL Managment Studio to connect to database engine on MachineB (local SQL Server), everything works. Then tries to connect to database engine on MachineA (remote SQL Server) fails with error:
Login failed for user ''. The user is not associated with a trusted SQL Server connection. (Microsorft SQL Server, Error: 18452)

I have run the SQL Server Surface Area Configuration on both machines and tried to configure them exactly the same.

I have checked Name resolution on both machines, no issues found. I can connect to other resources (\\MachineA\C$ works from MachineB and \\MachineB\C$ works from MachineA).

Peter99
Constraint Violating Yak Guru

498 Posts

Posted - 2010-06-08 : 13:43:44

Check on machineA, whether it is configured to allow remote connection?

DLTaylor
Posting Yak Master

136 Posts

Posted - 2010-06-09 : 04:32:33

Thanks Peter99 - MachineA allows remote connetions.

for example if i log onto a further e.g. MachineC (same set-up as above) as user1 i can connect to MachineA and run all the tasks id 'expect' to be able to run as if i were on MachineB.

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources