cannot connect from my client computer to sql server 2000
- hello, I have the sql server client tools (EM,query analyzer...) installed in my desktop. Everything was working fine until I decided to change my password today. I changed my password to all the servers including my domain controller. but i keep getting this error message when I try to connect to my EM from my desktop now... ...
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
I am part of the users group, administrators group and domain users. I have sql server 2000. I am not really sure what the problem is , It was working fine before i changed my password. I am using windows authentication to connect to my server. My sql server is set up for mixed authentication. I refreshed my active directory and restarted my sql server, made sure my sql server services and agent are running as well.
when i login directly to the server , everything is fine also, or if from my desktop i go to run as administrator and put the credentials for administrator then i am able to login to my em as well as query analyzer.. but the problem is when i use my local credentials eventhough i have the administrator rights to all my servers.Also, now when i try to run a form, etc from a database that has the backend in sql server i get the same error message... sql server error 18452.....login failed.... all i did was change my password in all the servers (and used the same password) I did not change any settings at all. help please.what else can i try?
Thanks in advance
-
If by local credentials you mean that you have logged into the computer and not the domain that would be your problem. you must be logged into the domain for the windows credentials to work.
-
yes i am logged in into my domain .
-
You mentioned that you can log in as the administrator. I assume you mean as 'sa' use SQL Server authentication. Since you are logging in successfully to your domain (of which your SQL Server is a member) with your new password, that part is probably okay. Can you access the server as 'sa' and verify that your domain user id is listed (under Security | Logins ) as a Windows user? What about query analyzer? Can you log into your server using QA and Windows authentication?
-
I am logging in a local/administrator, the sa is not available when i try to run as and open em or qa. now i went to my sql server and yes my account is under windows user.
-
also i have kerberos authentication...
-
Is the SQL Server service started with a domain user account?
I have had this issue if my service is started with the local system account.
Regards.
-
i try changing it to nt network account but i get the same error and also, i have some jobs that have to work with the local/administrator account so i had to put it back to this user.
-
anything else i could try?
-
If you are trying to log into a SQL Server from your workstation, and you receive the error "Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection." , then one of two things is causing the problem. (1) Your are not logged into the domain on your workstation or (2) The SQL Server is not a member of the domain you logged in to.
I assume you don't have any other connectivity or domain permission issues while accessing resources from your workstation.
It doesn't seem like a network protocol issue because the error you would likely receive would be "SQL Server does not exist".
If you run the Active Directory Users and Computers plugin, do you see both your user id and the SQL Server?
I'm not sure what you mean by "I am logging in a local/administrator, the sa is not available when i try to run as and open em or qa"
You mentioned earlier your SQL Server is setup with Mixed mode. Why can't you connect with QA using sa (after clicking the SQL Server authentication radio button and type the sa password)?
What happens when you physically logon to the SQL Server using your domain password?
Unless there are corrupted files somewhere, if both your domain user id and the SQL Server belong to the same domain, and your domain user id is assigned the sysadmin role (I think you alluded to that in an earlier post) in SQL Server, there aren't a whole lot of things that can cause your connection attempts to fail.
-
I am accessing all the drives of my workstation good and i have access to the network drives fine too. the problem is when i try to access a database with the backend sql server or i try to connect from my client tools to EM or QA.
to answer your questions:
If you run the Active Directory Users and Computers plugin, do you see both your user id and the SQL Server? Yes
I'm not sure what you mean by "I am logging in a local/administrator, the sa is not available when i try to run as and open em or qa" yes, and yes i could log in perfectly when I use this id.
You mentioned earlier your SQL Server is setup with Mixed mode. Why can't you connect with QA using sa (after clicking the SQL Server authentication radio button and type the sa password)? when i connect using sa, it connect fine through my desktop.
What happens when you physically logon to the SQL Server using your domain password? i could log in perfectly directly from the sql server.
Unless there are corrupted files somewhere, if both your domain user id and the SQL Server belong to the same domain, and your domain user id is assigned the sysadmin role (I think you alluded to that in an earlier post) --Yes. in SQL Server, there aren't a whole lot of things that can cause your connection attempts to fail.
is there any other options???? I can't get any of my work done, i already tried everything......
-
Are there other workstations that can connect to SQL Server? If so, can you logon to one of them using your domain userid and then try to connect using QA? If you can, then that would point to a configuration problem on your workstation. If not, then it's probably a userid-related problem. If no one can connect to SQL Server, you may have a DNS problem with server, which affects windows authenticated logins, but not standard SQL Server authentication.
You didn't say if this was a production server or not, which of course may affect the things you are able to try. (You may not be able to restart the server, etc.)
-
thanks so much for helping me, I tried using another workstation and login in with my windows user id and password and yes i am able to log in to QA and to EM with no problems., so it is definetely my workstation. Should i unistall completely my client and then reinstall it? is there anything i should try first?
again thank you.
-
Yes, that's what I would do next. Uninstall then reinstall. Also, make sure to run the appropriate service pack on your workstation after you reinstall to update the client tools to the same version as the server.
-
I did .... same error
Viewing 15 posts - 1 through 15 (of 18 total)
You must be logged in to reply to this topic. Login to reply