We've been witnessing a strange and annoying problem when using java-jml with SIP Communicator lately and we're not sure what might be causing it. Many users have reported that they cannot log on the MSN network on Windows XP machines behind a NAT.
When looking more closely into the issue, we discovered that the stack can't even establish a TCP connection with the login server. It keeps sending the initial "syn" and it never gets an ack. This only happens on windows machines located behind a NAT and my guess is that the syn packet doesn't really reach the NAT (but that's only a guess for now).
Has anyone ever had this problem?
I thought that it could be some firewall blocking issue but a simple (java) program that opens a tcp socket to the same address and on the same remote and local ports, doesn't have the problem. I am wondering whether this could be caused by cindy.jar.
Any ideas?
Thanks
Emil
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello all,
We've been witnessing a strange and annoying problem when using java-jml with SIP Communicator lately and we're not sure what might be causing it. Many users have reported that they cannot log on the MSN network on Windows XP machines behind a NAT.
When looking more closely into the issue, we discovered that the stack can't even establish a TCP connection with the login server. It keeps sending the initial "syn" and it never gets an ack. This only happens on windows machines located behind a NAT and my guess is that the syn packet doesn't really reach the NAT (but that's only a guess for now).
Has anyone ever had this problem?
I thought that it could be some firewall blocking issue but a simple (java) program that opens a tcp socket to the same address and on the same remote and local ports, doesn't have the problem. I am wondering whether this could be caused by cindy.jar.
Any ideas?
Thanks
Emil