FAQs
What can cause a CardAccess 3000 Workstation not to connect to a CardAccess 3000 host?
Refer to the Continental document library for the appropriate troubleshooting guide. There are many reasons why this would occur. Below are a few of them:
1) Verify on XP Pro and Server 2003, the firewall is disabled in Services. In Windows 7, Windows 8.1, Server 2008 R2 and Server 2012 R2, verify the firewall is started and INBOUND and OUTBOUND ports are all set to "ALLOW".
2) On Windows 7, Windows 8.1 Pro, Server 2008 R2 and Server 2012 R2, verify the UAC settings are lowered all the way down to "Never Notify". The UAC settings can be found in Control Panel>User Accounts.
3) Verify the "CardAccess Utility" on the CardAccess 3000 workstation contains the IP address of the CardAccess 3000 host and the Station ID is set to Workstation. The Port is a fixed value of 9000.
4) You must be able to ping from the CardAccess 3000 workstation to the CardAccess 3000 host by IP address and hostname. If you are unable to ping by hostname, you must make a manual entry in the hosts file.
5) Verify on the host and the workstation, Named Pipes and TCPIP are enabled. This can be found on the Start menu under SQL server 2008 R2>Configuration Tools>SQL server Configuration Manager >SQL Native Client configurations>protocols.
Note: This can also be verified by using the command prompt and type :
CLICONFG.EXE
Verify Named Pipes and TCPIP is in the box on the right. If not, move them over to the right.
6) If the full version of SQL server has been installed on the host computer, verify it is licensed correctly.