The connection dialog and where its three values come from — Namibia

Measured order execution — Standard

How orders actually filled when real market orders were placed on Exness’s MT5 feed — fill time, slippage and rejects by order size:

Small sample (a few round-trips per size); indicative. The same pricing engine feeds every platform the broker offers.

MetaTrader 4 (MT4) at Exness

• The connection dialog is the first screen, and none of its three fields is invented by the person at the keyboard — each of them has an issuer.
• The server field is a name chosen from a list that arrives with the build; it is searched by broker name rather than typed as an address.
• The account number and its password are issued together, and always by whichever side created the account.
• A practice account created from inside the terminal is issued its number and password by that dialog itself, on the spot.
• A live account number has no source inside the terminal: it comes into existence during registration on the broker side.
• The dialog can be cancelled — the program stays open and the three values can be entered later from its File menu.
• Entering three valid values is what turns an installed program into a connected one; until then the window is a program without a counterparty.

Three fields, three issuers

The connection dialog looks like a form and behaves like a lookup. The server is picked from a list, not invented; the number identifies an account that already exists somewhere; the password authorises that number. Nothing in it is a preference, which is why guessing at the fields never works and reading them as questions about origin always does.

Seen that way, the dialog is a useful map of the access boundary. It shows, in three lines, exactly which part of the arrangement lives on the machine and which part lives somewhere the machine has to be told about.

What the terminal can issue by itself

The same dialog contains a route that produces its own credentials. Choosing to create a practice account there makes the terminal request one from the server it has selected, and the number and password come back into the fields without a registration having happened anywhere. That is the whole of what the second door can do on its own.

It is worth noticing what this does and does not prove. It proves the program runs, the list of servers is present and the machine can reach one of them. It says nothing about any account belonging to a person, because no person was named at any point.

What has no source inside the terminal

A live account number is not a value the program can generate, request or recover. It is created on the broker side when a profile is registered, and from the terminal's point of view it simply arrives as text to be typed in. The same is true of the password issued with it.

This is the practical reason the two halves of the job — fetching the program and obtaining an account — can be done in either order, but neither one can produce the other. An installed terminal with no number and a number with no terminal are both half-finished states, and each is completed by the other side.

Reading the connection dialog field by field

1. Server: open the list and search by broker name. If the expected name is missing, the list is the problem, not the account.
2. Login: this is a number, not an email address. It identifies an account object rather than a person.
3. Password: the one issued together with that number, at the moment the account was created.
4. If no number exists yet, use the dialog's own route to create a practice account and let it fill both fields.
5. If a live number is expected, it comes from the registration on the broker side and cannot be produced here.

The dialog can be closed and reopened from the File menu at any time; cancelling it does not undo the installation.

Where each of the three values comes from

Two of the three can be produced locally. A live login number is the one value with no local source.

Related Exness pages