March 31, 2005 at 12:34 am
Hi There,
Can any one please help to solve the following problem ?
I have 3 different SQL 2k instances on my machine. My machine is connected to our DOMAIN network.
While installing these instances, i have used my Domain Account and passwords for starting the services.
I can access and use all the instances without any problem.
But if we try to access or connect (SQL Server Authentication) the above said instances by any other user/machine on the network, the instance names are not listing in the SERVER list and also cant connect to the instances.
It gives the following message:
Server Msg : 17.
"SQL Server does not exist or access denied."
Thanks in advance
Subhash
March 31, 2005 at 2:03 am
OK, so you used your domain account to start the services; this probably means that you are a local administrator on your system so no problems there.
Have you granted SQL access to the windows group/login in the security section, if it's still at the default settings then you'll be allowed in courtesy of membership of the builtin admins bit but no-one else will (except domain admins).
You can get a network admin to create a windows group and all the users you want to use your system into it, then create a new login for that group in enterprise manager and set the database access and permissions as you see fit.
Let me know if this helps
March 31, 2005 at 9:19 am
Please, first make sure that what Mike said is done.
I would say it does not look as permission problem from the error message. The error mesasaage looks like that instance could not be found and I always have this message with firewall problems, no matter who started the SQL services. It was only 2 cases where access was actually denied.
You do know that instances listen on different ports. Use Server Network Utility to check ports. Are you logging in from the same machine where the server is installed? did your users tried to use it from other computers? Instance should be accesses as MachineName\InstanceName
Additionally if users and you and the server are in different domains please, let them use fully qualified domain name like MyServer.Domain.MyCompany.com or whatever is on your DNS server for this machine.
Test both TCP/IP and Named Pipes for connection. Make sure network protocols are enabled in SQL Server. You may be using Shared Memory (LPC) when accessing from the same computer. Check in the Current activity Window Processes view what protocol is used when you are connected.
Any of what I listed usually produces your error message.
Replace your Domain account for SQL Startup with something else. Your account will lock out as soon as you change your domain password.
Yelena
Regards,Yelena Varsha
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply