cannot connect from my client computer to sql server 2000
-
Hmmmm. Without being able to look at the workstation hands-on, it's tough to debug unusual problems. Maybe something else is going on. Did you change any other settings other than your password? For example, if you are running Windows XP, did you turn on the Windows firewall?
Maybe the problem is not with the SQL Server components, but with a network setting.
You could run the Client Network Utility and make sure that it's configured similarly to the workstation from which you can connect successfully.
Also, have you read this? http://support.microsoft.com/kb/827422
I'm sorry, but I'm running out of ideas at this point.
Mike
-
Hello Jessica,
Something similar happened to me not long ago.
Since I could connect using a SQL Login but could not use Windows authentication, I thought that it was an Active Directory problem; possibly a conflict with my workstation.
I opened Client Network Utility and created an Alias for the server where SQL Server is installed. Instead of using TCP/IP as the protocol, I selected Named Pipes. I closed Client Network Utility and tried to connect through Query Analyzer again. This time it worked.
I went back to Client Network Utility and deleted the Alias, and the connection was again succesful.
I haven't had a problem since then.
I hope that helps.
-
hi thanks but i tried and i get the error message:
Unable to connect to server win2k3-02
Server: Msg17, Level 6, State1
[Microsoft][odbc sq server driver][namepipes]sql server does not exist or access denied.
-
Here is another solution: http://www.derkeiler.com/Newsgroups/microsoft.public.inetserver.iis.security/2004-06/0579.html
I haven't tried it yet. I will post an update after I do.
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply