David Bird (2/4/2010)
I've experienced the timeout error when SQL Server is down or I VPN from home using a different domain. Some containers fail from being unable to obtain a lock.
Try using the full domain server name in the SSIS Server table
I am not using VPN, I am directly connected to our network. I verified all servers are online. Most of the servers failing to connect are test servers and I know they are not utilized much, so I don't think locking is an issue. As one of my troubleshooting steps, I already have fully qualified the server name with the domain.
Verify the login being used by SSIS has the needed permission. You can start a profile on the remote servers to see what login is being used on both successful and unsuccessful connections.
All connection managers are setup to use Windows authentication. I am logging into SSIS using my windows ID and running (debugging) from there. My id is SYSADMIN on all servers in the ServerList table.
Review the error log for the SQL Server having connection failures. Make sure the capture Login Failure setting is enabled on the server.
I have reviewed the logs and there are no entries of failed login attempts or any errors for that matter. They are all set to capture failed login attempts only.
I thought maybe it's a firewall issue, but then I would have issues trying to connect to the servers from Management Studio as well. I am at a loss.