General information
Forum:
Microsoft SQL Server
Title:
We got a new DC and now no connections work
Environment versions
SQL Server:
SQL Server 2000
We recently upgraded our domain controller to a new machine and replace the existing DC with the new machine. The new machine was renamed and the old machine was turned off today. Now none of my ODBC connections from our VFP app will connect, they all timeout from the program. When I go and configure the connection I recieve the following error message :
Microsoft OLE DB Provider for ODBC Drivers error '80040e4d'
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connect
Is there something in the SQL box or in sql server itself that needs to find the old DC? If so where and how do I change it? As is stands right now we turned on the old box and it seems to have fixed the issue but we want it fixed correctly and get rid of the old box. Any suggestions?
Thanks in advance
Kelly
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only