Answer
This has been traced to a DNS/name-resolution issue reaching the database host rather than a credentials problem — resolve the database host's actual IP address (for example, by having someone with working access ping the host), add a manual entry mapping that hostname to the resolved IP in the local machine's hosts file, then restart Developer Studio; this workaround has restored the connection in confirmed cases of this exact "too long" error.