Run the following checklist if your client application (like Wordfast Pro, Wordfast Classic, or Wordfast Anywhere) cannot connect to WFS.
SomePort usually means 47110, which is Wordfat Server’s default port. If the WFS administrator sets up another port, use that port number.
IPnumber is the server’s domain name or IP number. If client and server are in the same LAN, use the server’s machine name, or LAN IP (visible in WFS in the Setup/Network pane). If not working inside a LAN, use the server’s WAN IP. The server’s WAN IP can be obtained from the server’s workstation by pointing a browser at http://www.whatismyip.com or going to the Setup tab > Network. Note that is is preferable to use a domain name (or machine name from within a LAN).
If 1. works and 2. (LAN or WAN) does not work, you’re dealing with port issues, NAT issues, firewall issues, or generally speaking, architecture issues that are outside our hotline’s reach. If 1. does not work, see the troubleshooting guidelines below.
With Wordfast Classic (WFC):
Prerequisite: you must run a small utility named WfServerRelay.exe alongside WF Server. WF Classic (WFC) actually “talks” to WfServerRelay (WFR). WFR “locally” talks to Wordfast Server (WFS). The physical server should have a fixed IP, and the appropriate port open. WfServerRelay uses port 81 by default.
In WFC, the connection string is entered in the “Remote TM” pane under "Use Wordfast Server (WFS)".
(using a completely local setting with WfServerRelay + WFS +
WFC in the same computer as shown in the screenshots
(using a distant server; note that only WFR has the distant
IP; WFS is seen as “local” by
Here are two screenshots that illustrate Wordfast Classic (WFC) running with Wordfast Server (WFS) and Wordfast Relay (WFR) all on the same machine. WFS and/or WFR can be on other machines in which case their respective IP addresses must be updated.
For the above example to work:
The entire setup (WFC’s TM and setup and the TM used by WFS) is EN-US to FR-FR. A common cause of failure is that the local tool (WFC) and the distant server’s TM do not have identical language codes.
All software is on the same computer (WFC, WFS, and WFR). If the server and the relay are on other machines, simply update the IP numbers. If WFR (WfServerRelay) is local and WfServer (WFS) is distant, WFR=... should have 127.0.0.1 as IP (local IP), and WFS=... should have the distant IP address. If both WfServerRelay and WfServer are remote, the WFR=... IP should be the remote IP, and the WFS=... IP should then be 127.0.0.1 - because then WFR “talks” to a local WFS).
The Account at WFS is named EN2FR (any other name is OK), the password is EN2FR (any other password is OK), the “Server active” checkbox is checked in WFServer's "Activity" pane, the "Activity log" checkbox is checked, so that the server echoes the received commands as in the screenshot. In the TM section of WfServer, there must be no password (password field empty): the password is defined at the account level.
TM is set to “active” in WFS’ TM tab.
WFC is set up as per the screenshot.
The active TM in WFS contains a translation unit with "Hello World." as source.
The active TM in WFS is in "sync" (meaning, it has been reorganized once).
When opening a segment in WFC, you should see echoes of your activity in both WfServerRelay and WfServer, similar to what is seen in the screenshots. A “WFS100” match should be served on a green background by WF Classic.
With Wordfast Pro and Wordfast Anywhere:
correct connection string is entered in the URL field of the “Add
TM > WFServer” or “Edit TM” pane under
where MyLogin is an active WfServer account name.
Make sure the language codes of the TM on the server side and those of WFP’s current project are identical. Those language codes are visible as TM properties in the Sessions/TM pane (the TM must be in use), or when opening the actual TM text file with Notepad: read the TM’s very first line
With both clients:
A “real” Wordfast TM has been added to the “TM” pane.
An account has been created. The account sets MyLogin and MyPassword as provided in the connection examples above. The account has a positive number in the small “Nb” setting (the number of clients that are allowed to connect. Do not leave that setting empty).
The “Server Active” checkbox under the “Activity” tab is checked. We recommend checking the “Activity log” checkbox to monitor activity when setting up, and unchecking during regular activity.
The client’s and server’s firewalls allow communication through the chosen port (47110 by default).