Cannot generate SSPI Context - HOW TO TURN OF KERBEROS ON CLIENT

Hi
God damn I have gotta lot of mess due to the "Cannot generate SSPI Context",
clipping my connection to the SQL server (connection OK in 40 - 60 minutes
then "poff" SSPI Context fails.
My environment is as follows.
- Domain recently converted to AD (SQL server also in AD)
- MS SQL 7.0 on Windows 2000 server
- WinXP sp 2 on (most) clients
- Access 2003 on (most) clients
I develop and publish an Access application which run against several db's
on the SQL server. Seems like I'm the only one having the "Cannot generate
SSPI Context" trouble yet. As I learn from different articles on the net,
it's most likely due to some Kerberos security stuff.
How can I turn that thing off, and access our SQL server on the lowest level
of security (with trusted connection). We have firewalls all over the place
protecting us from the outside, and none of our employees have brains to
access the SQL server and do any damage to it through a data connection.
Please anyone!!!
Mr. SmithCheck your time synch and DNS resolution. SSPI context issues can arise
from either of those not working correctly.
Geoff N. Hiten
Microsoft SQL Server MVP
"Mr. Smith" <nospam@.blindfolded.gone> wrote in message
news:OSH1P8iSFHA.1236@.TK2MSFTNGP14.phx.gbl...
> Hi
> God damn I have gotta lot of mess due to the "Cannot generate SSPI
> Context", clipping my connection to the SQL server (connection OK in 40 -
> 60 minutes then "poff" SSPI Context fails.
>
> My environment is as follows.
> - Domain recently converted to AD (SQL server also in AD)
> - MS SQL 7.0 on Windows 2000 server
> - WinXP sp 2 on (most) clients
> - Access 2003 on (most) clients
>
> I develop and publish an Access application which run against several db's
> on the SQL server. Seems like I'm the only one having the "Cannot generate
> SSPI Context" trouble yet. As I learn from different articles on the net,
> it's most likely due to some Kerberos security stuff.
>
> How can I turn that thing off, and access our SQL server on the lowest
> level of security (with trusted connection). We have firewalls all over
> the place protecting us from the outside, and none of our employees have
> brains to access the SQL server and do any damage to it through a data
> connection.
>
> Please anyone!!!
>
> Mr. Smith
>