Status reports, error messages, and other commentary are displayed in the text box near the bottom of the window.  Most error messages will include a brief explanation and suggestions for correcting the problem.  Errors encountered while listing a remote directory will also be displayed beneath the Remote Browser.

ExpeDat Client Interface

Some types of errors occurring during a file transfer will trigger Automatic Retry, which may allow for recovery during unattended operation.

Common errors are described below as well as in the Troubleshooting chapter.  A complete list of MTP/IP errors can be found in DEI Technical Note 0013.

No Application at Given Port
ExpeDat Desktop is able to reach the machine you specified, but no server is running there.  Check that you entered the correct server name and port, and that servedat is running on that machine.

No Response, ICMP Prohibited, or Network Down
ExpeDat Desktop is unable to reach the server.  Check that you are connected to the network, that you entered the correct server name and port number, that servedat is running on that machine, and that any firewalls have been configured to allow ExpeDat through.

Operation Timed Out
The transaction has been canceled because there has been no contact with the server for a long time.  If this occurs at the start of the transaction, it may indicate a network connectivity problem, that the ExpeDat server is not running, or that you entered the wrong address or port number.  If this occurs after a transaction has started, it indicates a loss of network connectivity, such as your Internet connection or the server going down.  This can also happen if there is a dynamic firewall which is configured to block high-volume UDP traffic.  See DEI Technical Note 0002 for firewall configuration instructions.

Invalid Pathname
The server did not recognize the Remote Path.  If you typed the remote path in manually, check that it is correct.  This error may also occur if the server and port you specified is not running an ExpeDat application.

Bad Credentials, Username, or Password
If the server requires authentication, make sure that the username and password you have entered are correct.

Request Denied
You do not have permission or access rights to perform the requested transaction.  If the server requires a username and password, that username may lack sufficient access privileges on the server.

Object Busy: Try again later
The file you are attempting to access is being used by another transaction or application.  If it is being uploaded by another ExpeDat transaction, you may receive an estimate of when it is expected to complete.

Server Capacity Exceeded: Try again later
The server may be beyond its configured capacity.  Try your transaction again later.  If the problem persists, contact the server administrator.

If you receive a different error whose cause is not self-explanatory, contact your system administrator or refer to the Troubleshooting chapter.