This is by design. During a startup sequence, specially in MW setup, the upcoming DSA 'pings' all related remote hosts where it's peer MW DSAs reside to check availability of those servers/hosts.
NOTE: Keep in mind, the check it not made for availability of remote DSAs but rather for the machines/hosts themselves.
Changes are during some sort of maintenance process, you might have:
** Shutdown one or more of those remote hosts OR
** Put this problem host as part of troubleshooting process behind a firewall OR
** Took it off the network etc.
As those are out side of your current MW network, the existing DSAs on the network will still work while this one fail to start if for any reason you are required to RESTART this isolated set of DSAs.
Remove the reference of those working host/DSAs from this isolated DSAs which you are trying to restart. Doing so, the DSA that is coming line, will not ping the remote host and this local DAS should start successfully.