|
Home > Archive > MS SQL Server > June 2005 > SQL Server Startup Authentication Question
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
SQL Server Startup Authentication Question
|
|
|
| We are running SQL Server 2000 (SP4) on laptops. Each is configured as
a client to the main database on our Company's server. Each client has
a replicated database locally for used when they are not online.
When we start the client SQL Server agent on our network domain it
detects the server database and connects to it via the network. When
we start the client without a network, the agent authenticates locally
and is started with the local database.
Here is our issue, and is there a registery setting to get around it:
When we start our client with a network connection, but not on the
company domain, SQL server refuses to start. We want it to fail over
to local authentication as if there were no network connection. Our
work-around is to disable the connection, stop/start the agent,
re-enable the connection.
Any ideas are appreciated.
| |
|
| How your SQl Server realise the your network or no work status?
-
Thanks
Ravi
"Mark" wrote:
> We are running SQL Server 2000 (SP4) on laptops. Each is configured as
> a client to the main database on our Company's server. Each client has
> a replicated database locally for used when they are not online.
>
> When we start the client SQL Server agent on our network domain it
> detects the server database and connects to it via the network. When
> we start the client without a network, the agent authenticates locally
> and is started with the local database.
>
> Here is our issue, and is there a registery setting to get around it:
>
> When we start our client with a network connection, but not on the
> company domain, SQL server refuses to start. We want it to fail over
> to local authentication as if there were no network connection. Our
> work-around is to disable the connection, stop/start the agent,
> re-enable the connection.
>
> Any ideas are appreciated.
>
>
| |
|
| Not quite sure what you are asking. If it detects a network
connection, but that connection is not in our Company domain (for
instance a personal home network with no VPN connection to our
Company), SQL server will start but fail on the authentication.
We want it to then try to authenticate locally as if there were no
network connection present.
|
|
|
|
|