What happens to Windows Authentication if domain failure occurs?

[vinodi]

Hi,


I have a peculiar problem (or maybe not). I have SQL clients installed
on XP boxes. These XP boxes are a member of let us say "XYZ" domain.
SQL Server is installed on one of the boxes having Windows 2000 Server
in the same network. The installation has been done on local domain
account. Since SQl Server has been installed with Windows
authentication, what happens if the XYZ domain fails. Will it be
possible for all clients to access the database present on SQL Server
in the Win 2K box. I think I have made myself clear upto some extent.
Please throw light on how to accomplish the connectivity between SQL
clients and server in case of domain failure.


Regards,


Vinodi




~~The only place where SUCCESS comes before WORK is in the dictionary~~

 

[SQLBill]

When you set SQL Server for Windows Authentication and accounts to use that also, you are telling SQL Server to 'trust' Windows authentication of the login. To do that, both systems (Client and the server) must authenticate via the same system (usually a domain controller). Therefore, if the domain is down there's no way to authenticate. Also, if the domain is down the client's won't be able to reach the SQL Server anyways - the domain is down.

So, 1. when a domain is down, the users can't reach any other machine but their own. So they won't be able to access the SQL Server.

2. even if they could access it, they won't be able to authenticate.

Even switching to SQL Server authentication won't work if the domain is down. The client machines still won't be able to reach it.

-SQLBill