can't conect to db in SS2005

Hi,

I'm trying to create a local version of our website on my PC (XP Pro SP3, on Bootcamp). I saved a backup of the db from the production server, copied it over to my pc, and restored it locally.

It looks fine. I'm able to query it and play with it in MS SS Mgt Studio, but I can't connect to it through my user.

When I try to open a connection using a user and password I know to be correct, I get the "no trusted connections message.

I'm new to SS2005. My previous experience is with SS2000, if that makes much difference.

I've compared my setup to the production db and the only difference in terms of privileges is that local machine doesn't have a server role that the corresponding user has on the prod server, "public". It's not in my install. On the prod server, the user's a member of that group, as well.

Otherwise, it has the same permissions for dbs and users.

Any ideas?

Thanks.

LeprechaunAsked:
Who is Participating?
 
chapmandewConnect With a Mentor Commented:
make sure that you're an admin on your local machine and that your admin account is running the mssqlserver service.  Have you set your SQL instance up to allow windows and SQL connections?  If not, do so (right click on the server) and then set the sa password.  Login using the sa account.
0
 
LeprechaunAuthor Commented:
I checked and I don't see any privileges associated with "public", so I guess that's a red herring.
0
 
LeprechaunAuthor Commented:
Thanks Chapmandew. I'm pretty sure I set this earlier, but maybe not. When I just checked, the db was set to Windows Authentication only, so I toggled that and restarted the service.

That didn't solve the problem, though it changed the error from the "no trusted conections" one to "login failed for user 'sa'".

Experimenting aimlessly, I tried to changing the password to empty and tried. It worked!

So then I changed the pwd again, and it worked again. Now things appear to be working as they should.

Weird. Do passwords get corrupted?

Not sure whether your suggestion fixed it, but if nothing else your tip started the chain of events that led to the solution. Thanks.

0
 
chapmandewCommented:
Maybe you just typed in the password wrong???  Now that you're in, go and make sure your windows account is able to access the server.  

Sounds like you're good to go.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.