It must be that your client that you use generates some random resource id every time you login. If you set it to a permanent value and then try to login with the same resource id from the other computer (or the same) it should kick the older session (if this is the policy conflict option). There is no way to make one username to login only from one location if resources are different. This is how jabber/xmpp operates.
↧