Connection string problem with sql 2000

[Bob]

I had code to use connection strings using integrated windows security and
that's been working OK for years, Now in my testing environment ( a W2k
server and 4 computers on a small LAN all with fixed IP's) I had to change
my IP address ranges from 192.168.1.xxx to 192.168.0.xxx. That should not
affect any connections since my network worked fine after that as before. I
can ping between all I can see the folders that I want as I want to. However
when trying to connect with my standard connection stsrings using SSPI, that
no longer works. I get an error back saying can not create SSPI context.
I ran tests creating ODBC connections and found that if I try to connect
using the computer name and integrated security, the connection can't
complete but if I use the computer name a user name and password, then the
connection works fine. My suspicion is that I must do something on the SQL
server, but I can't figure out what. I run the server in the localhost
system account so the SSPI context is created each time the SQL server
starts and destroyed when it stops. I did some reading up on this but did
not find anything that solves my problem.
Has anyone else run up against this problem before.
Any help would be appreciated.
Bob

[Robert Dufour]

Weirdest thing.
After I started using my Vs2005 I was having problems with the application
and the IDE hanging. The app just stopped responding while I was typing
code.
I decided to do a repair on the install of both Vs2003 on this machine and
of Vs2005. After completing these two repairs I can now test my odbc
connections using the integrated security to the server OK.
Now how the h... can VS2005 prevent ODBC data sources from obtaining a
connection to SQL server when its not even opened on the machine.

At least I can start working again.

Maybe some day MS will get stuff to work reliably, not reliably unreliable.

Regards to all,
Bob

"Bob" <bd*****@sgiims.comwrote in message
news:O9**************@TK2MSFTNGP04.phx.gbl...

>I had code to use connection strings using integrated windows security and
that's been working OK for years, Now in my testing environment ( a W2k
server and 4 computers on a small LAN all with fixed IP's) I had to change
my IP address ranges from 192.168.1.xxx to 192.168.0.xxx. That should not
affect any connections since my network worked fine after that as before.
I
can ping between all I can see the folders that I want as I want to.
However
when trying to connect with my standard connection stsrings using SSPI,
that
no longer works. I get an error back saying can not create SSPI context.
I ran tests creating ODBC connections and found that if I try to connect
using the computer name and integrated security, the connection can't
complete but if I use the computer name a user name and password, then the
connection works fine. My suspicion is that I must do something on the SQL
server, but I can't figure out what. I run the server in the localhost
system account so the SSPI context is created each time the SQL server
starts and destroyed when it stops. I did some reading up on this but did
not find anything that solves my problem.
Has anyone else run up against this problem before.
Any help would be appreciated.
Bob