If you want to force an HTTPS connection, you most probably need 443. If you want to force (Secure) TCP, it is probably 2705, unless the server admin reconfigured it.
When writing this article, my assumption was that memoq always uses HTTPS connection when HTTPS is possible. So I further assumed that whenever HTTPS is not used, it must be because HTTPS in prevented by a firewall or similar.
However, I've since found with that these assumptions are wrong. Sometimes, memoQ defaults to Secure TCP even if HTTPS is "allowed" and could be used. I have no idea what the logic is, so far.
There is a file that contains the last used protocol (connection type) for each server the memoq client has recently contacted:
This file needs to be edited in a hex editor and the protocol can be changed. Then when your restart memoQ, if HTTPS is possible, HTTPS will be used. In the file, the protocol is right after each server name. The value 01 means Secure TCP, and 03 means HTTPS.
I'll continue to investigate this.
And yes, there is a typo in the file name, "prococol." This is the name of the file, the typo is not mine but the developer's.
I've noticed I missed to include some important points, one about changing the connection type, and another about the scope of the issue. So I've edited this post. Those who have read it in email will not get an update.
1. First of all, it is the administrator of the memoQ TMS server who decides which types of connections are even allowed. So if they turned off HTTPS (in the memoQ TMS deployment tool), then users can’t ever connect via HTTPS.
2. Note that opening a project is just one example where network speed matters, and maybe not even the best one: checking out a project, exporting large files or TMs, and many other daily operations can be affected.
Another detail I've recently learned from the folks at memoQ support (or, rather, relearned after forgetting about it):
In memoQ's "Server URL" fields, you can enter the port number. Just put a colon after the server name, and then enter the number, like:
my.server.address.com:443
If you want to force an HTTPS connection, you most probably need 443. If you want to force (Secure) TCP, it is probably 2705, unless the server admin reconfigured it.
There's a new development. The plot thickens.
When writing this article, my assumption was that memoq always uses HTTPS connection when HTTPS is possible. So I further assumed that whenever HTTPS is not used, it must be because HTTPS in prevented by a firewall or similar.
However, I've since found with that these assumptions are wrong. Sometimes, memoQ defaults to Secure TCP even if HTTPS is "allowed" and could be used. I have no idea what the logic is, so far.
There is a file that contains the last used protocol (connection type) for each server the memoq client has recently contacted:
c:\Users\YOUR USERNAME\AppData\Roaming\MemoQ\PrococolCache.bin
This file needs to be edited in a hex editor and the protocol can be changed. Then when your restart memoQ, if HTTPS is possible, HTTPS will be used. In the file, the protocol is right after each server name. The value 01 means Secure TCP, and 03 means HTTPS.
I'll continue to investigate this.
And yes, there is a typo in the file name, "prococol." This is the name of the file, the typo is not mine but the developer's.
I've noticed I missed to include some important points, one about changing the connection type, and another about the scope of the issue. So I've edited this post. Those who have read it in email will not get an update.
1. First of all, it is the administrator of the memoQ TMS server who decides which types of connections are even allowed. So if they turned off HTTPS (in the memoQ TMS deployment tool), then users can’t ever connect via HTTPS.
2. Note that opening a project is just one example where network speed matters, and maybe not even the best one: checking out a project, exporting large files or TMs, and many other daily operations can be affected.