Client connection ignore maximum number of TCP connections
Posted: Thu Apr 04, 2013 2:43 am
Problems as subject, both client and server build number 9045.
what's happened:
I have a profile setup to make 32 TCP connections, when i try to connection at the first time, it works.
But after a disconnection and attempted to connect to the same server again, the client manager ignore the number of TCP connections setting, remains to maximum numbers of only 2 at anytime.
I also notice the VoIP/QOS function is also disabled by unknown reason when the connection settings being ignored.
I have to remove the profile completely and import it again to make it work with 32 TCP connections, and then it ignore the settings again after the first attempt.
I think it's a bug, somethings wrong after build 9035, since i don't have this problem before when i was on the build number of 9035.
what's happened:
I have a profile setup to make 32 TCP connections, when i try to connection at the first time, it works.
But after a disconnection and attempted to connect to the same server again, the client manager ignore the number of TCP connections setting, remains to maximum numbers of only 2 at anytime.
I also notice the VoIP/QOS function is also disabled by unknown reason when the connection settings being ignored.
I have to remove the profile completely and import it again to make it work with 32 TCP connections, and then it ignore the settings again after the first attempt.
I think it's a bug, somethings wrong after build 9035, since i don't have this problem before when i was on the build number of 9035.