Don't have any specific suggestions for fixing it. The error you are getting is precisely correct. If you go to the Windows account, you will in fact find that it has been locked out due to repeated login failures. I've encountered this one before within a single domain. The fix was entirely on the Windows side, but I do not remember how it was fixed. It seemed that the replication engine made several attempts to login which failed for some reason causing the security mechanisms in Windows to kick in and lock out the account. You do need to make sure that the account which replication is running under, generally the SQL Agent account, has access to the machines in both domains.
For More Information
- Dozens more answers to tough SQL Server questions from Michael Hotek are available here.
- The Best Microsoft SQL Server Web Links: tips, tutorials, scripts, and more.
- Have a SQL Server tip to offer your fellow DBAs and developers? The best tips submitted will receive a cool prize. Submit your tip today!
- Ask your technical SQL Server questions -- or help out your peers by answering them -- in our live discussion forums.
- Ask the Experts yourself: Our SQL, database design, SQL Server, DB2, object-oriented and data warehousing gurus are waiting to answer your toughest questions.
Dig Deeper on Microsoft SQL Server Installation
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.