No. Salt is not an authenticator. Salt is not a secure way to authenticate requests from the client.
A more complete answer is: You should back up, and do a requirements analysis and a risk analysis. Figure out what your security goals are, and what the threat model is. What resources are you protecting? What kinds of attacks might someone have an incentive to mount? Once you've been able to think that through, then you can start thinking about a particular mechanism.
At present, you do not seem to be able to give a clear description of what you are trying to accomplish. Therefore, the question is ill-posed and you are not likely to receive a good answer.
With such sparse information, the best advice I can give you is: use SSL (https). While I cannot be sure, due to the sparsity of the information give -- it sounds like you are probably reinventing the wheel, and probably poorly. Also, I recommend that you store state information on the server side, rather than storing it on the client and trusting the client to be honest about reporting the current state (after all, a malicious client can always lie -- a md5 hash does not prevent that).