Please check as follows on the server:
Windows Firewall
Go to the server that hosts the Access EasyPay database/ service and search for SQL Central 17.
Double-click SQL Anywhere 17 and click the Services tab.
Right-click the service that is running there and click Properties.
Click the Configuration tab and check the port number assigned e.g. serverport=2638
Go to the client pc, search for Windows Firewall,, and click Advance Settings.
Click In Bound Rules and check if there are any rules related to Access EasyPay. If there isn't, click New Rule.
Select Port and click Next.
Select TCP and select Specific Local Port.
Enter the port number you checked earlier in step 4.
Click Next and select Allow the Connection.
Enable the rule to all (domain, public, private).
Click Next, enter EasyPay, and click Finish.
Repeat the same steps for Out Bound Rule.
Using a unique ODBC in the client's pc
Go to the client's pc.
Go to EPE Control and click ODBC Setup.
Check the client's existing connection by selecting Configure an Existing DSN
Click Next do a print screen and exit the screen.
Click ODBC Setup, and select Create a DSN Connecting to a Server Database.
Enter a unique DSN Name and the rest enter the exact setting you got from step 4.
Click Next and check if connection is successful.
If the connection is successful, you can use this database to log in in the future. The previous database name has clashes with other PC/servers in the same network.