Client connection ignore maximum number of TCP connections

[Keis]

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.

[cedar]

I think your client connect with UDP mode.
UDP mode is better efficient than TCP.

If you want to use TCP I absolutely, please try to append '/tcp' to destination host name to be sure using TCP connection.

[Keis]

i'm confused, where should i put '/tcp' in the profile properties?
after the destination server host name like this?
www.hostname.com /tcp

[cedar]

Yes.
In VPN client account setting, set destination server host name like as 'vpn123456789.softether.net/tcp'. (blank is not needed between hostname and option.)