Re: SSPI handshake failed with error code 0x8009030c
- From: Sue Hoegemeier <Sue_H@xxxxxxxxxxxxx>
- Date: Mon, 27 Feb 2006 20:28:03 -0700
So if you are connecting to a network share using domain
credentials for the server, that doesn't always work....if
that's what you are doing. With XP Home, you are going to
work around security issues but not really have a sound
solution.
Maybe it still works somehow in SQL Server 2005 but to look
at what specific login has the login failure - if you see
user null as the failure, that's a different issue than
seeing the mapped drive credentials which is different from
an error where it's the guest account.
-Sue
On Fri, 24 Feb 2006 01:50:30 -0800, Andris
<Andris@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
The error 0x8009030c is SEC_E_LOGON_DENIED. I would guessYes other computers who is on domain can connect.
you enabled remote connections?
I thought that was a
different error. Is the PC and the server in the sameNo, server is on domain, but computer not.
domain?
You can check the default trace around the time of
the login failure to find what login is actually failing. IsProgram uses widows logon. But before i run the program i connect to server
that windows account setup as a login in SQL Server?
network share as domain\user.
.
- References:
- Re: SSPI handshake failed with error code 0x8009030c
- From: Sue Hoegemeier
- Re: SSPI handshake failed with error code 0x8009030c
- Prev by Date: Re: SQL 2005 - Encryption of a distributed application database
- Next by Date: Re: Adding permissions to an AD user on a remote database
- Previous by thread: Re: SSPI handshake failed with error code 0x8009030c
- Next by thread: Re: SQL 2000 drops connection, DDOS attack?
- Index(es):
Relevant Pages
|