working login no longer works mystery - sqlserver-server
This is a discussion on working login no longer works mystery - sqlserver-server ; I posted this earlier but I guess I wasn't clear. I have a working Domain Admin account named paul have been using it for over 5 years with no problems. Last night I changed the password with Exchange from home. ...
![]() |
| | LinkBack | Thread Tools | Display Modes |
|
#1
| |||
| |||
| I have a working Domain Admin account named paul have been using it for over 5 years with no problems. Last night I changed the password with Exchange from home. Then this morning when I got to work I couldn't login to the SQL Enterprise on a specific server. Other SQL servers were ok. Also if I could connect to the problematic server from a different computer without any problem. I also have a spare login paul2 that is also a domain admin. So on the computer that was giving me trouble I logged in and had no trouble connecting to the sql server. So the here are the results of different user and computers paul on hpadmin connect to lvac03sql doesn't work paul on hpchad to lvac03sql does work paul2 on hpadmin does work paul2 on hpchad does work What is on the PC for that specific user that would cause integrated security to fail. It has to be something in the registry. I have read tons of discussions on login failed for user ' they all deal with the account not being setup correctly from the start. Where as I know that Paul on HPADMIN worked yesterday. I will reboot the servers in the morning and hopefully that will fix the problem. I have already rebooted HPADMIN multiple times. I have also recreated the computer account and changed my password on the AD Server. other post is here http://groups.google.com/group/micro...93ca26d3c76ba9 sql error log although its not helpful. 2007-12-20 07:52:49.51 Logon Error: 17806, Severity: 20, State: 2. 2007-12-20 07:52:49.51 Logon SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 10.10.10.123] 2007-12-20 07:52:49.51 Logon Error: 18452, Severity: 14, State: 1. 2007-12-20 07:52:49.51 Logon Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 10.10.10.123] |
|
#2
| |||
| |||
|
Hi Paul have you checked for aliases on the client? You may also want to check which protocols are being used. I assume that you have logged out and back into hpadmin? John "barrettpaulj@gmail.com" wrote: > I posted this earlier but I guess I wasn't clear. > > I have a working Domain Admin account named paul have been using it > for over 5 years with no problems. Last night I changed the password > with Exchange from home. > > Then this morning when I got to work I couldn't login to the SQL > Enterprise on a specific server. Other SQL servers were ok. Also if I > could connect to the problematic server from a different computer > without any problem. > > I also have a spare login paul2 that is also a domain admin. So on the > computer that was giving me trouble I logged in and had no trouble > connecting to the sql server. > > So the here are the results of different user and computers > paul on hpadmin connect to lvac03sql doesn't work > paul on hpchad to lvac03sql does work > paul2 on hpadmin does work > paul2 on hpchad does work > > What is on the PC for that specific user that would cause integrated > security to fail. It has to be something in the registry. > > I have read tons of discussions on login failed for user ' > they all deal with the account not being setup correctly from the > start. Where as I know that Paul on HPADMIN worked yesterday. > > I will reboot the servers in the morning and hopefully that will fix > the problem. I have already rebooted HPADMIN multiple times. I have > also recreated the computer account and changed my password on the AD > Server. > > other post is here > http://groups.google.com/group/micro...93ca26d3c76ba9 > > sql error log although its not helpful. > 2007-12-20 07:52:49.51 Logon Error: 17806, Severity: 20, State: > 2. > 2007-12-20 07:52:49.51 Logon SSPI handshake failed with error > code 0x8009030c while establishing a connection with integrated > security; the connection has been closed. [CLIENT: 10.10.10.123] > 2007-12-20 07:52:49.51 Logon Error: 18452, Severity: 14, State: > 1. > 2007-12-20 07:52:49.51 Logon Login failed for user ''. The user > is not associated with a trusted SQL Server connection. [CLIENT: > 10.10.10.123] > > |
|
#3
| |||
| |||
|
I ended up do a safe start and renaming the profile of paul and then restarted and recreated the user profile. That has fixed the problem except now I have to transfer all the info from the old profile to the new one. I still wish I new what in the user profile prevented the trusted sql login. |
|
#4
| |||
| |||
|
The problem is that you need to remove the cached password for this server. Recreating your profile is one way to do this, but not the easiest. To remove the cached password, follow these steps: 1)Select Start\Settings\Control Panel\User Accounts 2) Highlight the user and select the "Advanced" tab. 3) Click "Manage Passwords" 4) Highlight the server and remove it. |
![]() |
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
| |
All times are GMT -4. The time now is 08:07 AM.




Linear Mode