I see somebody have same problem.
at this post
callback sample problem
and Matthew answer:
" What configuration information are you running with exactly? Can you post the contents of "config" please? My guess is that you didn't add the -h <ip> to one of the endpoints correctly, and since you are using a multi-homed system the OS picked the wrong endpoint again.
I just tested this by running the server with the default configuration, and adding -h <ip> in the Callback.Client.CallbackServer property in the client configuration and the same worked as expected. However, my machines don't have two ethernet cards"
So I edit my client config file. Add -h<ip> in the Callback.Client.CallbackServer property. Server use default config file. But server always direct callback to my pc's IP "192.168.0.x".
and failed.
Matthew, can you post you test server config file,and client config file?
Thanks.