Cannot generate SSPI context. State ID: HY000

kriki

I know there are other posts about this, and I tried it all out.

I have Navision 5.00 on a SQL2005 standard edition on an XP (my portable).

If I try to connect to the SQL DB with Windows login (with nettype default,Named Pipes,TCP/IP Sockets,Multiprotocol) I get this error.
The strange thing is : if I connect with MS SQL Server Management Studio, I can connect to it without problems.
I already restarted the PC, but no use.

For the moment I am NOT on MY domain network but on another network.
When I was writing this post, I got some idea : I disconnected the cable and tried to logon and it succeeded!

Now I would like to logon when I am connected to another network. Does someone know how to do that?

colin_leversuch-roberts

off the top of my head it sounds as if you're authenticating, or trying to, to the AD. MS will always connect as it works with the local context - I assume the sql server is running as local system? I don't run SQL on XP so I don't know if it's an XP issue. Maybe run a profiler trace to see what's being called?

kriki

It is a local system.

I also thought about the fact that Navision is trying to find the domain to authenticate (because it works if I remove the network cable).

Now I thought to try to block some network traffic through Zonealarm for Navision 5.00 and I found 2 versions (IT and W1) with different Zonealarm blocks. So I checked and saw I used IT and not W1 as I thought. So I tried with W1 and it worked but I found it strange because seeing the blocks in Zonealarm I expected it would not work with W1. So I tried with IT and it also works! :shock: ](*,) :bug: ](*,) ](*,) ](*,)

So, I suppose some component (probably ODBC to get Navision connect to SQL) needs some time before it knows the portable is NOT connected to its domain.

ravikantc

I also got the same error...............and tried following method:

Go to advanced tab and select Net Type: "Named Pipes" and i am able to login................

I don't know what was the problem :-# :-k

kriki

I already forgot I created this topic.

I already tried the "Named Pipes" and the "Default" (first thing I did actually), but it doesn't help.

But a month or 2 ago, I thought of another way and this seems to work.
I use TCP/IP BUT I do NOT use the name of my portable, but I use 127.0.0.1 as the servername and this seems to work without problems.

ara3n

You can also VPN into your network and then connect.

kriki

ara3n wrote:

You can also VPN into your network and then connect.

yes, but I don't always have internet.

ara3n

kriki wrote:

ara3n wrote:

You can also VPN into your network and then connect.

yes, but I don't always have internet.

I thought if the computer is disconnected it works?

kriki

ara3n wrote:

kriki wrote:

ara3n wrote:

You can also VPN into your network and then connect.

yes, but I don't always have internet.

I thought if the computer is disconnected it works?

Yes, but after a while.
Now that I use 127.0.0.1 and TCP it always works.

gvolkov

I understand you SOLVED this case when running the db on your local machine. I am running SQL 2005 and NAV 5.0 And one of my users experiencing this error. The interesting thing is that when his workstation is freshly started, NAV opens just fine. Then for about 10-15 miuntes it works fine. After that however, if its closed, it cant be reopened resulting in same SSPI error you mention in this thread. Anyways, i tried to make sure the time on the db server is syncronized with the workstation, but that didnt help. Any ideas????

kriki

gvolkov wrote:

I understand you SOLVED this case when running the db on your local machine.

Correct.

I can only use the name when I am in my domain-network. So it could be that they lose connection to the domain controller or the domain name server?
The strange thing for me was that NAV lost the connection and got that error, but the SQL server management studio worked fine.

jlandeen

I've recently gotten this error in a reconfigured environment and I noticed that when I use the IP address of the SQL server instead of the name of the sql server I get this error.

Seems weird that when I connect with the SQL Server by name everything works but if I try connecting by IP address I get an error.

bbrown

If you ping the server by name, does it respond with the same IP you are using?

serdarulutas

Happens to our users when they forgot about resetting their Windows password. They still have access to OS but the NAV access is rejected. One they reset their windows password, they regain access.