Hello. My name is Inigo Montoya. You killed my father. Prepare to die.
Balu Sadhasivam wrote:Patrick,
Instead of "localhost" , try with IP "127.0.0.1". Or make sure if you have "127.0.0.1 localhost" entry in hosts file.
Hello. My name is Inigo Montoya. You killed my father. Prepare to die.
Paul Sturrock wrote:You won't see SQL Server listening on 1433 via netstat, I think it reports the port as machinename:ms-sql-s or machinename:ms-sql-m. Do you have anti virus software running? Does it block connections?
You are trying to use integrated authentication, if you swap to SQL Server authentication can you connect?
Hello. My name is Inigo Montoya. You killed my father. Prepare to die.
Patrick Brooks wrote:
I didn't see AVG blocking, but I did not disable it; guess I should. I haven't tried with SQL Server authentication, because I'm having problems with it. When I create a new account which uses SQL Server auth, I can't log in as the account I just created. Strange.
Balu Sadhasivam wrote:
Patrick,
Check out if this thread could help you
Hello. My name is Inigo Montoya. You killed my father. Prepare to die.
Paul Sturrock wrote:
Have you enabled your server to accept both kinds authentication? I think out the box its Windows integrated only.
Hello. My name is Inigo Montoya. You killed my father. Prepare to die.
Hello. My name is Inigo Montoya. You killed my father. Prepare to die.
Hello. My name is Inigo Montoya. You killed my father. Prepare to die.
Did you see how Paul cut 87% off of his electric heat bill with 82 watts of micro heaters? |