Key takeaways
- The exact server string must identify the broker's intended MetaTrader endpoint.
- A connected terminal for that account is the authoritative source.
- Verified registry entries and unverified candidates must be presented differently.
If MT5 reports that it cannot find a server, first copy the exact server name from a terminal already connected to that account. The connected terminal is authoritative; emails, portals and guessed sibling names are candidates until the broker or a successful connection verifies them.
Why the server name is so fragile
A MetaTrader server label identifies a specific broker endpoint and legal entity. Spaces, suffixes, platform version and account entity can matter, so a brand name alone is not enough. A plausible-looking label can still refer to the wrong platform or to no registered endpoint at all.
Method and limitation note: an idle login, timeout or server-not-found message is not proof of one cause. Directory availability, network reachability, platform version and the supplied name can produce similar symptoms.
The three reliable sources, in order
- A connected terminal for the same account. Copy the server value exactly from account details or the login selector.
- The broker's branded terminal server list.Confirm that the account's platform and legal entity match the selected entry.
- The broker portal or support team. Treat a welcome email as a candidate and ask for confirmation when it conflicts with the connected terminal.
Server-name checklist
- Confirm MT4 versus MT5.
- Copy spaces, punctuation and numeric suffixes without normalization.
- Confirm the broker entity attached to the account.
- Retest the exact string in the broker's own terminal before changing the password.
Symptoms of a wrong server name
- The selected label is absent from the broker terminal's server list.
- The login remains unresolved rather than returning a clear credential response.
- A sync service returns server unknown while the same account works under a different exact label.
These are troubleshooting clues, not a diagnosis. Preserve the original value and compare one change at a time so a network or credential problem is not mistaken for a naming problem.
How TradeStats sidesteps the problem
The TradeStats connection form reads broker metadata whose entries carry a verified flag. The picker marks verified entries as such; other discovered names remain unverified candidates until validated. In the current registry, Vantage International entries are candidates rather than verified entries, so the connected terminal should decide which value belongs to the account.
If no verified entry matches, use the exact connected-terminal value and continue with a unique investor password. Broker execution data becomes relevant only after the account actually synchronizes; the broker scoreboard is not a server-name directory.
Frequently asked questions
Why can a wrong MT5 server name be hard to diagnose?
An unknown directory entry can look like a timeout or an idle login rather than a password rejection. That symptom is not conclusive, so compare the string with a terminal already connected to the same account.
Where is the authoritative server name?
A connected terminal for that account is authoritative: copy the server shown in its account details or login information. A broker portal, email or another platform's server list can be a useful candidate but may use different formatting.
What if the broker email and connected terminal differ?
Use the exact value shown by the connected terminal and ask the broker to confirm the discrepancy. Emails and portals can contain platform suffixes, spacing differences, or details for a different account entity.