If the user is attempting to log into a system that has been previously connected to, the client will have 'remembered' the alternate ingress addresses associated with that system and use them, if necessary, to re-establish a connection. Under certain circumstances this can result in connecting to an address other than the one entered explicitly on the login form. When establishing an initial connection, the client will try each alternate site only once before 'giving up' and reporting an error.

Using the example from above, consider a scenario in which a user had logged out of, and is now logging back in to central.demo.com. On the login screen, they enter the server address: central.demo.com, but when they click the 'Login' button, their client, having remembered alternate ingress addresses, may choose a different ingress address to connect to.

Be aware that alternate ingress addresses are associated with the primary ('identity') address used to initially connect to the system. In the previous example, had the user re-entered a different server address on the login screen (say, east.demo.com) and that alternate site was unavailable, the client would not attempt to connect to west or central.