Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Chris Gervasini
Starting Member
2 Posts |
 Posted - 2009-05-14 : 17:34:28
|
| Here is our scenario. We have a visual.net application that was developed in house. This application will be published through Citrix and we will be assigning permissions to the views in the SQL database. It was determined that the SQL Server (data) for this application was so sensitive that it needed to be housed in a seperate domain. I created the new domain which consists of one server acting as the DC and SQL server. I created a two way trust for the domains and am able to add users from our existing domain as logins to the new SQL server. When we try to connect to the new sql server through SQL Server Management Studio, Express, ODBC, etc we continue to get the Cannot Generate SSPI Context Errors. I have searched and found suggestions for ways to try and resolve this issue but have had no luck. One of the posts said something about the domains belonging to the same forest. I am hesistant to do this for fear of messing with our domain. Does anyone have any clear ideas on this or other suggestions? |
|
|
Chris Gervasini
Starting Member
2 Posts |
Posted - 2009-05-18 : 09:56:06
|
| I discovered that this issue was being caused by DNS that I was running in the original domain. I created a host record in the DNS server for the new SQL server in the new domain and the SSPI errors were resolved. |
 |
|
|
|
|
|
SQL Server in Different Domain SSPI Context Error