When line to primary Domain controller is dropped, some of the current logged on clients are dropped by SQL when they try to access the database. For some clients, the application still works just fine.
The clients are all set up and authenticated in the local Domain Controller. It is my thought that the authentication by the local domain controller should not be affected by dropping the network connection to the HQ Primary Domain Controller. Our VB/SQL application is set for Windows authentication and works fine in that mode. Until we drop the line to HQ.
One clue I had is that both the SQL Server and the Domain Controller (active directory) are on the same Server. We moved the SQL Server to another Server, not the one with the Active Directory on it. Again, while the network is up, everyone can connect, but when we bring down the network, some users could connect to the SQL Server database and others received an error:
Problem in mdlFindServer.FillTable: Trying to read UpdateHistory.
ex = System.Data.SQLClient.SqlException: Timeout expired. The timeout period dlapsed prior to completion of the operation or the server is not responding.
Any help will be appreciated. Please and Thank you.
Software/Hardware used: WIndows Server 2003, Visual Basic express, SQL Server Express, Dot Net 2.0
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!