kelso109
asked on
The target principal name is incorrect. Cannot generate SSPI context. (Microsoft SQL Server, Error: 0)
Hi,
I have added a new PC to the domain where the SQL server resides,
However, when I try to login to the sql server using windows authentication I get the following error:
Cannot connect to a2\a.
-------------------------- ----
ADDITIONAL INFORMATION:
The target principal name is incorrect. Cannot generate SSPI context. (Microsoft SQL Server, Error: 0)
Now,
1. I am able to connect from the same pc using SQL AUTH without any problems.
2. I have other PC's I added to the domain and I was able to login to the SQL server using windows auth without an issue.
3. on this PC I am unable to login using windows auth with ANY domain user, even with users that I confirm working from other PC's on the domain.
4. I tested ping , dns and such its all good.
How to proceed?
Thanks.
I have added a new PC to the domain where the SQL server resides,
However, when I try to login to the sql server using windows authentication I get the following error:
Cannot connect to a2\a.
--------------------------
ADDITIONAL INFORMATION:
The target principal name is incorrect. Cannot generate SSPI context. (Microsoft SQL Server, Error: 0)
Now,
1. I am able to connect from the same pc using SQL AUTH without any problems.
2. I have other PC's I added to the domain and I was able to login to the SQL server using windows auth without an issue.
3. on this PC I am unable to login using windows auth with ANY domain user, even with users that I confirm working from other PC's on the domain.
4. I tested ping , dns and such its all good.
How to proceed?
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks, I will give it a try.
It seems secure channel is broken, so disjoin and rejoin the PC from domain.
Tahir
Tahir
ASKER
di join and re join to the domain worked!
You mention that you can't connect with windows authentication... have you tried a SQL server login? if you can connect with a SQL login (not windows credentials), it would reinforce that the client isn't being trusted by the Domain.