what did I do now - can't log on to default instance

Question

what did I do now - can't log on to default instance

mikekay

SSC Enthusiast

Points: 135
More actions
March 3, 2009 at 2:33 pm

#218846

Greetings. My studies continue and the more I learn the more trouble I'm getting into....;-)
I can no longer log on to default instance using Windows Authentication. I can log on using SQL Server Auth.
What I did is enable tcp/ip in configuration manager.
I am currently looking at configuration manager, highlighted SQL Server (MSSQLSERVER), right click, properties. I selected This Account, browsed the name, typed in the password, and restarted the service. I have also made sure that the user has permissions to c:\program files\microsoft SQL server directory. I changed the default port, and checked to make sure the port is open on the computer. It is.
I then log off, back on to the proper account, try to log on and get this:
logon failed Error 18456.
Any help appreciated.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

MANU-J. SSC-Dedicated Points: 31126 More actions · Answer 1

To determine the true reason for the failure, look in the server's error log where a corresponding entry will be written.

MJ

mikekay SSC Enthusiast Points: 135 More actions · Answer 2

The problem was caused by my trying to change the port connection, from the default to a different port number. This should have worked and I'm not sure why it did not.

The error logs for this problem were not very helpful - it just told me the connection was refused.

Back to the studies to find out why I cannot change the tcp/ip port.

Thanks for your help.

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 3

mikekay (3/4/2009)
The problem was caused by my trying to change the port connection, from the default to a different port number. This should have worked and I'm not sure why it did not.
The error logs for this problem were not very helpful - it just told me the connection was refused.
Back to the studies to find out why I cannot change the tcp/ip port.
Thanks for your help.

If you change the port that SQL Server uses, I believe you then have to explicitly include the prot number in your connection to the server. Either that, or have the SQL Bowser Service running, but for the default instance, it expects it to be on 1433.