3.2

Table Of Contents
Troubleshooting Client Connection Problems
227
6. Unlock the server.
Troubleshooting Client Connection Problems
This topic provides suggestions for settings to check if a client system is not connecting properly.
Network Configuration
Check the TCP/IP connection by typing
ping
<servername>
in the Command Prompt on
the client.
Server Settings
Check if there is a user account for the user. See “Managing Users, User Groups, and User
Rights” on page 123
.
Check if the password is expired. See
“Viewing and Setting Attributes” on page 127.
Check that the user has access to the database (a role other than No Access).
Make sure the user authorization provider includes the user account. See
“Setting User
Authentication Providers and Importing Users” on page 109
.
Client Settings
Reinstall Interplay Access. This client application hosts Interplay Access, Interplay
Administrator, and the connection package for any connection to Interplay.
Optimizing Interplay Performance
This topic provides some basic items to check if you are running into unexplained slowness
(either server or client side) with Interplay:
Make sure that the server meets the current specifications. See the Interplay ReadMe.
Make sure that the client is running on a system that meets specifications.
Run the client from the server machine.
If Interplay Access runs well on the server machine, it might indicate that the other clients
are communicating slowly with the server because of a network problem. Start the client on
the server machine and see if you have the same problems.
Check for other processes running on the server machine.
Most installations should run the Interplay Engine on a dedicated machine. If you are relying
on the server machine to perform other duties as well, you might have performance issues.
For example, some virus scanners can lock files on a server, and the Interplay Engine waits
until the file is unlocked before it can be moved, renamed, deleted, and so on.