How to Test PDM Connection with a Ping Test
It’s important to ensure SOLIDWORKS PDM clients have a strong network connection to the PDM server components to reduce time spent while working in PDM as well as prevent data loss over slow connections. One method our technical support experts use to test PDM connection, especially when troubleshooting performance behavior, is to check the network latency between the client and the server using a ping test.
The default ping test on Windows is 32 bytes, which means the system sends a packet size of 32 bytes between the source and the target device four times. The results for the four pings are displayed, including if packets were received, lost, and the minimum, maximum, and average round-trip time.
To improve the quality of the test to a size more comparable with PDM communications, you can run an extended/continuous ping test with an increased packet size of 1500 bytes. This guide details various command prompt options to increase ping test frequency and data packet size.
Note, a ping test is only testing the consistency of the connection between the source and target server. To test if a PDM client can connect to the various PDM server components in your environment, follow the instructions for running the SOLIDWORKS PDM Connectivity Test Tool.
Ping Test Latency Results
Before we get to the detailed instructions, it’s important to understand the desired PDM network connectivity speed and the effects of increased latency. Times are shown in milliseconds (ms)
<40 ms is normal in a local network environment.
<80 ms is workable for an internet connection, but problems can occur when accessing larger amounts of data. This value is high for a local network environment.
>80 ms performance issues will be noticeable, and failures will occur.
>120 ms performance degradation will be quite noticeable and the number of failures will increase significantly.
>200 ms connection issues are critical and access to data may not be possible at all.
Find the PDM Server Name
Before you can ping the PDM server, you will need to know the PDM database server name. Launch the SOLIDWORKS PDM Administration tool, log into the vault, and then right-click the vault name and select Properties to view the name. For the example images in this guide, server named MLC-RBraine was used.
Standard Ping Test
Launch a Windows Command Prompt by right clicking the Windows Start icon and selecting Run. Enter ‘cmd’ and press OK. Alternatively, search Windows for Command Prompt.
By default, the Command Prompt opens to the user folder of the logged in Windows user. You do not need to change the folder path. The ping can be run from any filepath.
Type the following text and press Enter to start the ping:
ping <your server’s name>
The ping results will be displayed after four packets of data are sent and received or attempted.
- Size of the data packet sent for each instance.
- Time for each packet to be sent and received (total round-trip time).
- Ping statistics/summary.
Extended Ping Test
Adding continuous option -t to the end of the ping text string will continuously ping the target until stopped by either pressing Ctrl+c (results are then displayed in the Command Prompt window) or closing the Command Prompt (this option ends the ping without displaying results). To test your network’s latency over time, it’s recommended to run the extended ping test for several minutes. This will help determine if data is being lost or delayed.
Type the following text and press Enter to start the ping:
ping <your server’s name> -t
Note the image below contains many more ping tests. This ping test was run for only a few seconds.
Extended Ping Test (specify packet size)
Adding option -l 1500 (lowercase L character) to the end of the ping text string will specify the data packet being tested to the desired size; 1500 is recommended for PDM.
Combining this with the extended ping option -t, the ping will continue running until stopped by either pressing Ctrl+c (results are then displayed in the Command Prompt window) or closing the Command Prompt (this option ends the ping without displaying results). To test your network’s latency over time, it’s recommended to run the extended ping test for several minutes. This will help determine if data is being lost or delayed.
Type the following text and press Enter to start the ping:
ping <your server’s name> -t -l 1500
Extended Ping Test (with log file that can be shared to tech support)
Adding a filepath and text file to the end of the ping text string will record the ping test and results in a text file within the specified location, which can then be shared with technical support. Note, using this text log file option will not display the ping test within the Command Prompt as it runs. The ping will run silently in the background until stopped. The Command Prompt screen will not change.
Combing this with the extended ping -t and specifying the packet size using option -l 1500 (lowercase L character), the ping will continue running until stopped by either pressing Ctrl+c or closing the Command Prompt; either method will add the results to the text file. To test your network’s latency over time, it’s recommended to run the extended ping test for several minutes. This will help determine if data is being lost or delayed.
Type the following text and press Enter to start the ping:
ping <your server’s name> -t -l 1500 >C:\temp\Pingtest.txt
Once you stop the ping test, navigate to the filepath specified and open the Pingtest.txt file to review the results or share it with MLC CAD Systems technical support for review.
Additional Resources
Technical Support
Get help from our team by Calling us at 800-364-1652 x 2. You can also get assistance by clicking the Technical Support button or the Email Our Experts button below.