cannot generate SSPI context

Hi,
This only happens on a particular user's machine so far. the user is using
ms access, using odbc link to connect to SQL Server 2000 SP3a on W2k server.
With the MS Access running , suddenly the error happend when i ping the sql
server i can get its ip addr
i have checked the ms article on the SSPI but it does not seem to apply for
me in my case
appreciate any advise
tks & rdgs
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...ivity/200512/1
One thing to check is the SQL Client Network stack. This is configured in the
(SQL Server) Client Network Utility. What you will probably find is that the
working clients either have Named Pipes before TCP/IP, or left out TCP/IP.
While the problem client will have TCP/IP first, or left out Named Pipes.
At a guess, you are running the SQL Server with a Domain Account, but it
does not have the permission to register the SQL Server's SPN (Service
Principal Name). This means that it cannot use delegation, which probably
isn't a problem for you guys. But when someone tries to attach using TCP/IP,
it can't use Kerberos and throws the error.
Clients that connect Named Pipes just by-pass Kerberos and security account
delegation.
I may have gotten a couple of the details mixed up, I'm not 100% on this.
There is a good Trouble Shooting page in the SQL Support and in BOL, under
Administering SQL Server is a page called "Security Account Delegation" that
is worth a read.
Good luck
"maxzsim via droptable.com" wrote:

> Hi,
>
> This only happens on a particular user's machine so far. the user is using
> ms access, using odbc link to connect to SQL Server 2000 SP3a on W2k server.
> With the MS Access running , suddenly the error happend when i ping the sql
> server i can get its ip addr
> i have checked the ms article on the SSPI but it does not seem to apply for
> me in my case
> appreciate any advise
> tks & rdgs
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...ivity/200512/1
>