Solved this one myself, but it does not make much sense.
On the client computer, I opened Client Network Utility and in the Alias >
Edit tab changed the name of the 'Server Alias' to something different from
the 'Server Name'. Now, I can at least connect using SQL Authetication.
Next hurdle is Windows authentication.
Mike Thomas
"Mike Thomas" wrote in message
>I have been using Windows XP SP 2 and SQL Server 2000 Developer's edition
>on one computer and it has worked fine. For testing, I've installed Query
>Analyzer on a 2nd, workgroup computer. I know the network itself is
>working. Files and printers are shared and working.
>
> The problem is that ODBC and Query Analyzer on computer 2 cannot connect
> to the SQL Server on computer 1.
>
> The message returned is "SQL Server does not exist or access denied".
>
> I suspect SQL Server is not hearing the connection request.
>
> The user name I am using (Windows authentication) is MST, and this name
> has a login ( COMP!\MST). When I try to login from computer2, I suppose
> the login is COMP2\MST ? At any rate, I cannot add this login to SQL
> server.
>
> Using SQL authentication, I can log in on computer 1 via Query Analyzer
> with a different user name and password, but I receive the message above
> when I try to log in via QA from computer 2.
>
> Can anyone point me in the right direction to solving this?
>
> Thanks
> Mike Thomas
>
FAQ
Search
Profile
Private Messages
Log in
