The easiest way to confirm a firewall is not blocking the connection is to log on the file/database server as an administrator and turn off any firewall you have running, such as Windows Firewall and/or any other third-party firewall. If the workstation(s) can connect to the server once all firewalls are disabled, then applying an exclusion to these ports will yield successful results. If disabling all firewall on the server does not resolve the issue, try disabling the firewall at the workstations to confirm if the workstation is allowing outbound communication. If all firewalls are disabled on the server and workstation and the issue persists, the root cause is not the firewall and setting exclusions will not resolve your communication issue. Note: If all firewalls are turned off, you can use the netstat -an command to determine whether Pervasive is actually running and ready to accept communication requests from workstations on the noted ports. - Click the Windows start menu, Search all programs and files, and type: cmd
- Press the Enter key.
- At the command prompt, type: netstat -an
- Press Enter. This should show the ports in a LISTENING state. Pervasive is listening on the ports for workstations to connect.
In order for workstations to access Pervasive data on the server, netstate -an must show the correct ports and firewalls must not be blocking the connection attempt. [BCB:156:Chat 300 CRE US:ECB] |