| Application | PLAXIS 2D
PLAXIS 3D |
| Version | 3DFoundation
PLAXIS 2D |
| Date created | 30 May 2011 |
| Date modified | 05 October 2021 |
All dongle/hardware lock (HWL) based versions of PLAXIS 2D/3D are treated as "V8i SELECTseries 10" according to Bentley's Support Policy. This means that Bentley will discontinue support for hardware lock based versions of PLAXIS after December 31, 2021. This includes PLAXIS 2D 2019 and older, and PLAXIS 3D 2018 and older.
To see the benefits of the latest versions and how to get the latest version, please see PLAXIS CONNECT Edition: upgrade from Hardware lock to Flexible licensing
How to install Plaxis with a network CodeMeter dongle (grey USB key).
- Install Plaxis software on the client PC
- Install the latest CodeMeter drivers from the Plaxis website
- Install the same driver version on the server
- Insert the CodeMeter USB key in the server.
- On the server, open the CodeMeter WebAdmin, browse to Configuration and check the Run Network Server option
- Restart the CodeMeter Service on the server (Open the CodeMeter Control Center, go to the menu Process and choose "Restart CodeMeter Service".
- When using the IPv6 protocol (and not IPv4), always fill in the IP address of the Server in the Server Search list on the client pc. This can be done in the following tab-sheet of the local PC's WebAdmin ( http://localhost:22350/configuration/server_search_list.html ). This should be done on the client PC, not on the server.
- In most cases, it should work now.
Trouble shooting
- Check if the client pc can find the server: open the web browser and type: http://<IP-address server>:22350. Now you should be able to see the CodeMeter WebAdmin of the server. If not try to see if the server can be found at all by starting the command console and type 'ping <IP-address server>'
- Please note that the CodeMeter key uses port 22350 (default setting) for communication. Make sure that the firewall does not block the communication over this port. To check this, temporarily disable the firewall and check if the program starts. Please do not forget to turn on the firewall again.
- Sometimes the automatic search for the CodeMeter server takes too long, and will result in a timeout. In that case, please add the IP-address to the IP search list in the following tab-sheet of the local pc's WebAdmin (http://localhost:22350/configuration/server_search_list.html ) This is the client pc, not the server.
Make sure to use the correct IP address. If for instance only IPv6 protocol is available (e.g. when using Microsoft Direct Access), make sure to fill in the IPv6 server address.
Note: when using IPv6, you should always fill in the Server Search list - When the time out is still given, increase the UDP waiting time to increase the waiting time for a response from the server. To do so, go to the CodeMeter Webadmin and go to Configuration > Advanced > Extra (http://localhost:22350/configuration/extra.html) and increase the UDP Waiting time. Then you need to restart the CodeMeter service: open CodeMeter Control Center, and from the menu item Process, select to Restart the process.
- Licence updates should be done on the computer containing the CodeMeter network key.
Note: trouble shooting tips are updated for CodeMeter Version 6