Troubleshooting
The MTP Utilities may report diagnostic messages if an unusual or aberrant condition occurs. If the software does not appear to be working as expected, please re-read the documentation, then check the list below for suggestions. You may also find useful tips amongst the DEI Tech Notes. If you are unable to resolve the problem, contact DEI technical support at +1 617-500-0002 ext. 2 (US Central Time), or submit a technical support request.
If you have purchased MTP software through one of our international sales partners, please contact them for support.
When reporting trouble, describe the circumstances as fully as possible. Include the exact text of any messages and the revision codes of the applications. The GUI version can be found by clicking the "About" button. Version codes in the CLI versions are displayed by adding "–v" to the command line. Information about your networking environment, such as link type and speed, operating systems, and types of files being transferred is also very helpful.
Following are some circumstances and diagnostic messages which you may encounter when using MTP Utilities:
Tests fail with "Local Network: No Application at Given Port"
This most likely means that a server is not currently running on the machine indicated by the server address or port. Check that you have entered the correct address and port into the client. If the server is running on a private network that is different from the client's network, you must make sure that the server's router has Network Address Translation (NAT) correctly configured. Also check that the client is using the public address of the router, not the private address of the server.
Tests fail with "Local Network: No Response"
This indicates a connectivity problem. Verify that you are using the correct server address and port number. Check the network connectivity between the two systems and make sure that an MTP server is running on the remote system.
If there is a firewall or NAT device in the path, make sure that it is configured to pass through the UDP port number of the server. For lserve and MTPtestGUI, the default server ports are UDP 8082 and TCP 8082. See DEI Tech Note 0002 for detailed instructions on configuring firewalls.
If the server you are contacting hosts multiple IP addresses, try using its default address (usually the first one listed by "ifconfig -a" or "ipconfig /all"). Note that MTP servers can be configured to run on any port, so check with the server administrator to verify that you are using the correct port number.
MTP0: bind: Address already in use
Another application is already using the UDP port. Check whether you have another lserve, mtptest, or MTPtestGUI application running.
bind: Address already in use
Either another application is already using the TCP port, or it has been less than 60 seconds since you quit lserve, mtptest, or MTPtestGUI. Under some circumstances, TCP/IP prevents its ports from being re-used for some time after the application using them has quit. This is an inherent limitation of TCP/IP. If no other MTP Utility is running, wait 60 seconds then try again.
Data transfer doesn't seem any faster
MTP/IP maximizes utilization of your network path, but it cannot go any faster than the slowest component of your data path. On congested, broadband, wide-area network paths, MTP will almost always be faster because TCP is very inefficient in those environments. But on slow, little-used, or local-area networks, TCP may be able to max-out your connection. Also note that third-party hardware which performs compression or bandwidth management may be affecting the performance of both protocols.
Data transfer is very slow, much slower than TCP
Many factors can affect network performance. If MTP/IP is transferring data more slowly than FTP or other TCP based applications, it is usually due to the configuration of one or more network devices.
Note that MTP/IP is not supported with devices designed only for TCP/IP. This includes SSL VPNs and all network emulators.
Check whether any of the routers or other devices in your network have been configured to restrict UDP data flow. See Tech Note 0002 for advice on configuring firewalls. If you are using a VPN, check that it fully supports UDP datagrams. SSL VPNs do not fully support UDP and are not compatible with MTP/IP. It may be helpful to temporarily disable firewalls or bypass other devices to isolate the problem.
For more suggestions on diagnosing performance and connectivity problems, see DEI Tech Note 0009, or submit a detailed technical support request.
"The license period for this software has expired"
You are using a trial or temporary license version and the time limit has expired. You must download an updated version from either the DEI website or your customer download site. See Tech Note 0012 for tips on updating your software, particularly if you are getting this error after installing purchased software.
The license code is not accepted or not remembered
Licensed (non expiring) versions of the software require that you enter a license code the first time you run the software on new hardware. If a computer has multiple network interfaces, such as ethernet and WiFi, a license code will have to be entered separately for each interface. You must enter the specific license code that matches the software and hardware you are using. For more information about license codes, see the Setup chapter. For more license code error messages and their possible meanings, see Tech Note 0027.
"Unable to resolve host"
The Domain Name or IP address could not be understood. Verify that you are using the correct name and that your system is online.
"Server Busy"
This message indicates that the server or peer you are contacting is already in use or at maximum capacity and you should try again later.
"MTP0" "DOC0" or "SEQ0" messages are appearing
These messages are produced if MTP encounters very unusual conditions or errors. If you are unable to resolve the issue based on the message output and the problem persists, please contact technical support for assistance.