Home All Groups Group Topic Archive Search About

SQL connection problem

Author
22 Nov 2006 10:43 PM
Robert Dufour
This is my connection string, the syntax is I think quite correct. The name
of the computer is my local machine, the database exists and I can connect
to it with the enterprise manager,
data source=WINXP1;initial catalog=SGIIMSTransNetPartner; Integrated
security=True

The error I get back Is cannot create SSPI context. I tried this connecting
to another server from this machine, same thing. This used to work fine
before, now all of a sudden , no joy.

Anyone have any ideas on how to fix this?

Thanks for any help,
Bob

Author
22 Nov 2006 10:59 PM
susiedba@hotmail.com
make a new text file; change the extension from TXT to UDL

double click on it; set all of the settings you want

change the extension from UDL back to TEXT; open it and you've got the
whole connection string already built for you

-Susie, DBA


Robert Dufour wrote:
Show quoteHide quote
> This is my connection string, the syntax is I think quite correct. The name
> of the computer is my local machine, the database exists and I can connect
> to it with the enterprise manager,
> data source=WINXP1;initial catalog=SGIIMSTransNetPartner; Integrated
> security=True
>
> The error I get back Is cannot create SSPI context. I tried this connecting
> to another server from this machine, same thing. This used to work fine
> before, now all of a sudden , no joy.
>
> Anyone have any ideas on how to fix this?
>
> Thanks for any help,
> Bob
Author
23 Nov 2006 4:11 PM
Robert Dufour
Susie. Its not a connection string problem. I did all that before it still
does not work. It looks like its a problem with network security settings
but I can't pit my finger on it.
Bob
<susie***@hotmail.com> wrote in message
Show quoteHide quote
news:1164236347.925540.66240@m7g2000cwm.googlegroups.com...
> make a new text file; change the extension from TXT to UDL
>
> double click on it; set all of the settings you want
>
> change the extension from UDL back to TEXT; open it and you've got the
> whole connection string already built for you
>
> -Susie, DBA
>
>
> Robert Dufour wrote:
>> This is my connection string, the syntax is I think quite correct. The
>> name
>> of the computer is my local machine, the database exists and I can
>> connect
>> to it with the enterprise manager,
>> data source=WINXP1;initial catalog=SGIIMSTransNetPartner; Integrated
>> security=True
>>
>> The error I get back Is cannot create SSPI context. I tried this
>> connecting
>> to another server from this machine, same thing. This used to work fine
>> before, now all of a sudden , no joy.
>>
>> Anyone have any ideas on how to fix this?
>>
>> Thanks for any help,
>> Bob
>
Author
27 Nov 2006 6:05 PM
susiedba@hotmail.com
well it's a connection string problem

or a firewall problem


Robert Dufour wrote:
Show quoteHide quote
> Susie. Its not a connection string problem. I did all that before it still
> does not work. It looks like its a problem with network security settings
> but I can't pit my finger on it.
> Bob
> <susie***@hotmail.com> wrote in message
> news:1164236347.925540.66240@m7g2000cwm.googlegroups.com...
> > make a new text file; change the extension from TXT to UDL
> >
> > double click on it; set all of the settings you want
> >
> > change the extension from UDL back to TEXT; open it and you've got the
> > whole connection string already built for you
> >
> > -Susie, DBA
> >
> >
> > Robert Dufour wrote:
> >> This is my connection string, the syntax is I think quite correct. The
> >> name
> >> of the computer is my local machine, the database exists and I can
> >> connect
> >> to it with the enterprise manager,
> >> data source=WINXP1;initial catalog=SGIIMSTransNetPartner; Integrated
> >> security=True
> >>
> >> The error I get back Is cannot create SSPI context. I tried this
> >> connecting
> >> to another server from this machine, same thing. This used to work fine
> >> before, now all of a sudden , no joy.
> >>
> >> Anyone have any ideas on how to fix this?
> >>
> >> Thanks for any help,
> >> Bob
> >
Author
23 Nov 2006 2:22 AM
Charlie Brown
Robert,
Are you developing on a laptop and moving from work to home often?  I g
et this error occasionally when my laptop loses its cached domain
credentials becuase I have been off the domain for a couple days.

Anyway, just throwing it out there.

Robert Dufour wrote:
Show quoteHide quote
> This is my connection string, the syntax is I think quite correct. The name
> of the computer is my local machine, the database exists and I can connect
> to it with the enterprise manager,
> data source=WINXP1;initial catalog=SGIIMSTransNetPartner; Integrated
> security=True
>
> The error I get back Is cannot create SSPI context. I tried this connecting
> to another server from this machine, same thing. This used to work fine
> before, now all of a sudden , no joy.
>
> Anyone have any ideas on how to fix this?
>
> Thanks for any help,
> Bob
Author
23 Nov 2006 4:12 PM
Robert Dufour
No I had to change the ip addresses of my network from range 192.168.1.xxx
to 192.168.0.xxx and the problem started after that. I have no Sysadd, I,m
it and I don't know what to do to fix this.
Bob
Show quoteHide quote
"Charlie Brown" <cbr***@duclaw.com> wrote in message
news:1164248549.975426.82650@k70g2000cwa.googlegroups.com...
> Robert,
> Are you developing on a laptop and moving from work to home often?  I g
> et this error occasionally when my laptop loses its cached domain
> credentials becuase I have been off the domain for a couple days.
>
> Anyway, just throwing it out there.
>
> Robert Dufour wrote:
>> This is my connection string, the syntax is I think quite correct. The
>> name
>> of the computer is my local machine, the database exists and I can
>> connect
>> to it with the enterprise manager,
>> data source=WINXP1;initial catalog=SGIIMSTransNetPartner; Integrated
>> security=True
>>
>> The error I get back Is cannot create SSPI context. I tried this
>> connecting
>> to another server from this machine, same thing. This used to work fine
>> before, now all of a sudden , no joy.
>>
>> Anyone have any ideas on how to fix this?
>>
>> Thanks for any help,
>> Bob
>
Author
23 Nov 2006 5:52 AM
Cor Ligthert [MVP]
Robert,

Just connect your sysad if you get this kind of troubles, he can even have
powered that server off.

Cor

Show quoteHide quote
"Robert Dufour" <bduf***@sgiims.com> schreef in bericht
news:%23Oth0eoDHHA.1748@TK2MSFTNGP02.phx.gbl...
> This is my connection string, the syntax is I think quite correct. The
> name of the computer is my local machine, the database exists and I can
> connect to it with the enterprise manager,
> data source=WINXP1;initial catalog=SGIIMSTransNetPartner; Integrated
> security=True
>
> The error I get back Is cannot create SSPI context. I tried this
> connecting to another server from this machine, same thing. This used to
> work fine before, now all of a sudden , no joy.
>
> Anyone have any ideas on how to fix this?
>
> Thanks for any help,
> Bob
>
>
Author
23 Nov 2006 4:15 PM
Robert Dufour
Hey corr, you guys think we're all like MS with a bunch of experts on staff
:-)
Here, I'm the sysadd, the server is on was never turned off. But I can't get
to it with integrated network security and I can't figure out what to do to
connect.
Bob

Show quoteHide quote
"Cor Ligthert [MVP]" <notmyfirstn***@planet.nl> wrote in message
news:e2QT%23MsDHHA.4256@TK2MSFTNGP04.phx.gbl...
> Robert,
>
> Just connect your sysad if you get this kind of troubles, he can even have
> powered that server off.
>
> Cor
>
> "Robert Dufour" <bduf***@sgiims.com> schreef in bericht
> news:%23Oth0eoDHHA.1748@TK2MSFTNGP02.phx.gbl...
>> This is my connection string, the syntax is I think quite correct. The
>> name of the computer is my local machine, the database exists and I can
>> connect to it with the enterprise manager,
>> data source=WINXP1;initial catalog=SGIIMSTransNetPartner; Integrated
>> security=True
>>
>> The error I get back Is cannot create SSPI context. I tried this
>> connecting to another server from this machine, same thing. This used to
>> work fine before, now all of a sudden , no joy.
>>
>> Anyone have any ideas on how to fix this?
>>
>> Thanks for any help,
>> Bob
>>
>>
>
>