Client Connection Problem.

Hi Everyone,
I have a problem while executing my application on the network. I don't know
why this error "cannot generate SSPI context". I have been developing client
server application in VC++.NET with SQL Server 2000. I installed my SQL
Server on Windows Server 2003 machine and configured as Domain Controller ex.
soficomdrc.com. The client machine have client utility of SQL Server. How to
solve this problem? Can someone explain to me? why?
My connection string like this:
static String* SQL_CONNECTION_STRING =
S"Server=GSDC01;Database=Soficom;Integrated Security=SSPI";
Thanks in Advance
Jose
There is a lengthy troubleshooting article in the knowledge
base that lists all the steps you need to follow on trying
to track down the issue. Refer to:
How to troubleshoot the "Cannot generate SSPI context" error
message
http://support.microsoft.com/?id=811889
-Sue
On Wed, 5 Oct 2005 08:26:06 -0700, JoseTA
<JoseTA@.discussions.microsoft.com> wrote:

>Hi Everyone,
>I have a problem while executing my application on the network. I don't know
>why this error "cannot generate SSPI context". I have been developing client
>server application in VC++.NET with SQL Server 2000. I installed my SQL
>Server on Windows Server 2003 machine and configured as Domain Controller ex.
>soficomdrc.com. The client machine have client utility of SQL Server. How to
>solve this problem? Can someone explain to me? why?
>
>My connection string like this:
>static String* SQL_CONNECTION_STRING =
>S"Server=GSDC01;Database=Soficom;Integrated Security=SSPI";
>Thanks in Advance
>Jose
|||That I already read. I coudn't understand fully. That's why I cam to forum.
Jose
"Sue Hoegemeier" wrote:

> There is a lengthy troubleshooting article in the knowledge
> base that lists all the steps you need to follow on trying
> to track down the issue. Refer to:
> How to troubleshoot the "Cannot generate SSPI context" error
> message
> http://support.microsoft.com/?id=811889
> -Sue
> On Wed, 5 Oct 2005 08:26:06 -0700, JoseTA
> <JoseTA@.discussions.microsoft.com> wrote:
>
>
|||Is the client machine on the domain? Are you trying to connect with a local
user or a domain user?
MeanOldDBA
derrickleggett@.hotmail.com
http://weblogs.sqlteam.com/derrickl
When life gives you a lemon, fire the DBA.
"JoseTA" wrote:
[vbcol=seagreen]
> That I already read. I coudn't understand fully. That's why I cam to forum.
> Jose
> "Sue Hoegemeier" wrote:
|||Yes I am connecting the client machine by domain user. I can access my SQL
Server by Enterprise Manager.
Jose
"MeanOldDBA" wrote:
[vbcol=seagreen]
> Is the client machine on the domain? Are you trying to connect with a local
> user or a domain user?
>
> --
> MeanOldDBA
> derrickleggett@.hotmail.com
> http://weblogs.sqlteam.com/derrickl
> When life gives you a lemon, fire the DBA.
>
> "JoseTA" wrote:
|||Trying to solve that over the newsgroups isn't an easy task
as there is a lot that goes on with connectivity errors. But
some things to start with...when you can connect using
Enterprise Manager, is that across the network?
Are you trying this (Enterprise Manager and your
application) from different PCs?
Are you trying this with different accounts being that you
are using Windows Authentication?
Go to a PC where your app won't connect and try to ping the
server by server name. If that doesn't work, try to ping the
server by IP. If that doesn't work, you have network issue.
Next, try to connect with your app by logging into the PC
that's running your app using a windows login you know has
connected to SQL Server before. One that has the client
utilities are installed. If your app can't connect, then
trying connecting on this same PC still using Windows
Authentication with Query Analyzer. If that does work, its
something specific to how your app is connecting or the
connection string. Sometime you can connect with named pipes
but not TCP/IP protocol and get this error. In that case,
you can try modifying your connection string to use named
pipes and see if you can connect and get around the error.
If that doesn't work, try creating an alias using the client
network utility on the client that can't connect.
And that's just a few of the things you can start checking
and modifying (one at a time and test after each step) to
see if you can get things going.
-Sue
On Fri, 7 Oct 2005 01:55:08 -0700, JoseTA
<JoseTA@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Yes I am connecting the client machine by domain user. I can access my SQL
>Server by Enterprise Manager.
>Jose
>"MeanOldDBA" wrote: