I think this makes sense. When you first boot the computer, you haven't
logged in, so there is no user context for Windows Authentication. That is,
if Windows doesn't know who you are because you haven't logged in, then how
is SQL Server going to trust the connection. But SQL Server Authentication
works because you provide a user context.
You should be able to run your script as a login script, because then SQL
Server can use the context of the Windows user that is logging in. Of course
that may be too late for retrieving the info you need. If so, it looks like
your two options are SQL Server Authentication, or provided some sort of
sanitized info to an anonymous login.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
[quoted text, click to view] "GEL" <gel@dummy.gov> wrote in message
news:HYednWfjwvRYlUXbnZ2dnUVZ8vqdnZ2d@giganews.com...
> Howdy!
>
> I'm writing a little script that should run at bootime.
> The script should connect to SQL Express and retrieve some values
> from a view.
>
> Running and testing this script as administrator works without
> problems.
>
> Running this script at boottime results in a refused connection to
> sql server. The eventlog of the server shows event id 18456 (error
> during logon of user nt-authoroty\anonymous-logon).
>
> I allowed the domain group "domain computers" to select from that
> certain view, but no luck.
>
> I bypassed the problem by using an sql account instead of windows
> authentification.
> But I don't like that.
>
> How can I allow all my domain computers to access that view using
> windows authentication?
>
> TIA
> Gert
>
>
> --
> --------------------------------- --- -- -
> Posted with NewsLeecher v3.8 Final
> Web @
http://www.newsleecher.com/?usenet > ------------------- ----- ---- -- -
>
