I'm having a trouble with my SQL server 2000. I use Windows 2000 advance server SP4 and SQL Server 2000 sp4.
Sometimes i recieved "Cannot ganerate SSPI context" when i open enterprise manager and trying to connect to (local) instance of SQL Server.
If i restart the OS, it works just fine, but after a while it will happend again (the error).

Some website said that it's because of the domain.

Right now i use DNS from my ISP to connect to the server:
202.155.84.188
202.155.84.189
And i use IP:
192.168.7.12
subnet mask:
255.255.255.0
And default gateway:
192.168.7.1
I use the gateway to connect to the internet.

So my Sql server computer is connected to a gateway, and other computer that using the sql also connected to the gateway.

I don't know what wrong with my SQL server.

Can anybody help me?

Thx,
rabbi

abtakerNew Member

25 Jan 2007 08:09 PM

Hai,...

I never use the SSMS,....

I already allow mixed authentication. And when the error occured, i always open the EM from the computer which i installed the SQL server 2000 (which generate the error).
Becuase of these error, all my scheduled jobs (backup, etc) can not run.

I really2 don't know what's wrong with it. At first it's okay, but after a few minutes it's error again.

So it's like that i can't connect to the sql server registration (local) it self.

But recently, i tried something and i got one step further on this issue.
By the time i cannot connect / open the Enterprise Manager from local (i open the EM from
the server itself), all of the client CAN / able access the database from remote.

And if i change the setting in the Client Network Utility, the error message that
i got also change.
If i use TCP/IP, the error is "Cannot generate SSPI context."
If i use the Named Pipes, the error is about cannot Connect()).

I know that EM is considered as client application by the SQL Server (so it must connect
using client setting), but what happen to Shared Memory? Because i access the EM from the
server itself not from remote.