Why new users must log in through .salesforce.com instead of test.salesforce.com?
Has anyone recognized this problem earlier where a user has to login through their specific instance's node (cs1,cs2, ...), rather than through test.salesforce.com?
Is it just because these users are so new it hasn't propagated yet? What is the reason behind that?
This issue has been faced by many users but unfortunately, it is still unfixed and struggling to understand why need to log in through .salesforce.com instead of test.salesforce.com.
Summary
After a sandbox has been activated, it may take up to 5 hours for login attempts via the test.salesforce.com login portal to be successful.
This is due to a delay in the replication of the user from the new sandbox environment to the redirection pointer on the test login server.
In some scenarios, the replication delay seems to also occur when creating new users in a sandbox environment.
Repro
After your sandbox has been refreshed, attempt to log into the environment from Test.salesforce.com. After several hours, the login attempts will be successful once the replication has completed.
Workaround
The current workaround is to log into the application directly from the server in which this sandbox environment is hosted. This will bypass the test login server completely.
To login directly to the server, access the login page for the server itself.
For example, if you organization resides on the cs5 environment you would log in via https://cs5.salesforce.com.
If you are using My Domains and not sure which server you should be accessing, please define the domain for the environment into the field on this page.