I have a laptop which is on my company's domain sometimes, and other times NOT on the domain (e.g if I am on the road).
The laptop has an off-the-shelf vendor application that I will call 'zzz'. When I launch zzz, it tries to open a local database using my windows credentials. That is, my id 'homsim' is a member of AD group 'domn\zzzusers'. 'domn\zzzusers' has dbo permissions on the local db, so I am alllowed to connect to the db instance and access the database.
Even though we're using Windows Authentication, I can connect to the local db even if I am working offline e.g. NOT on the domain. (Using something cached, perhaps?) By the way, my laptop does not have wireless, so I'm sure I'm offline.
The current version of 'zzz' has MSDE/SQL 2000 (8.0.760).
WHAT HAS CHANGED
Now I am upgrading my laptop with a new version of 'zzz'. That new version has SQL 2005 Express (9.0.4035). Now I can connect to the database if on the domain, but NOT if I am offline.
I get an error "Login failed for user ''. The user is not assocaited with a trusted SQL Server Connection". In the event viewer there is the following: "SSPI handshake failed with error code 0x80090311 while stablishing a connection with integrated security; the connection has been closed. [CLIENT: 127.0.0.1]"
How can I configure this app (or Windows permissions or SQL configuration) so that the Windows user can connect to the local database even if off the network? The requirement would be that the user must have authenticated previously while they WERE on the network. I realize I should call the vendor (and I have) but they don't have an answer.