|
|
| (4 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | [[Category:Installation]][[Category:Pervasive]] | + | #REDIRECT [[Installation Environment and Network Requirements]] |
| − | Agency Systems is a network dependant application. In a typical setup the programs and data are located on a dedicated server or master workstation. This means that
| |
| − | your network is an important piece for the performance and sustainability to run Agency Systems. Below are some key items and requirements for Agency Systems to run properly.
| |
| − |
| |
| − | ==== Verify that all workstations on the network are on the proper Workgroup or Domain ====
| |
| − |
| |
| − | Each Windows computer belongs either to a workgroup or a domain. Home networks and other small LANs utilize workgroups, whereas larger business networks operate with domains. Choosing proper workgroup and/or domain names is essential to avoiding technical problems in networking Windows computers. Ensure your workgroups and/or domains are named appropriately according to the following rules.
| |
| − |
| |
| − | Ensure each workgroup and domain name is no longer than 15 characters.
| |
| − |
| |
| − | Ensure no workgroup or domain name contains spaces. Windows ME and earlier versions of Windows do not support workgroups or domains with spaces in their name.
| |
| − |
| |
| − | Whenever possible, ensure all computers on the LAN use the same workgroup/domain name. Using common workgroups/domains makes it easier to browse the network and avoids some security complications when sharing files. Note that the default workgroup name in Windows XP is "MSHOME" but in older versions of Windows is "WORKGROUP".
| |
| − |
| |
| − | Ensure the name of the workgroup/domain is different from the name of any computer on that network.
| |
| − | Avoid special characters in workgroup and domain names. Whenever possible, do not use any of the characters when naming Windows workgroups and domains: / \ * , . " @
| |
| − |
| |
| − | ==== Verify that all workstations have a valid computer name ====
| |
| − |
| |
| − | When setting up a peer-to-peer Windows network, each computer name must be configured properly. Computers having names that violate Windows guidelines may, for various technical reasons, fail to network with their peers on the LAN. Ensure your computers are named appropriately according to the following rules:
| |
| − |
| |
| − | No two computers can possess the same computer name. Ensure all computer names are unique.
| |
| − |
| |
| − | Ensure each computer name is no longer than 15 characters.
| |
| − |
| |
| − | Ensure no computer name contains spaces. Windows ME and earlier versions of Windows do not recognize computers having space characters in their name.
| |
| − |
| |
| − | Avoid special characters in computer names. Whenever possible, do not use any of these characters when naming Windows computers: / \ * , . " @
| |
| − |
| |
| − | Avoid using lower-case letters in a computer name whenever possible. On Windows Vista, the case of letters (upper or lower) is ignored. Older versions of Microsoft Windows, however, treat computer names as case sensitive. Entering computer names in all upper case is recommended to avoid possible name conflicts that would prevent Windows computers from identifying each other.
| |
| − |
| |
| − | ==== Make sure that you can ping the server by name ====
| |
| − |
| |
| − | A ping test determines whether your computer can communicate with another computer over the network. Then, if network communication is established, ping tests also determine the connection latency (technical term for delay) between the two computers.
| |
| − |
| |
| − | You can use a ping test to troubleshoot connectivity problems with your home network. Ping tests are also commonly used to measure the delay ("lag") with online gaming services or other Internet servers.
| |
| − |
| |
| − | Microsoft Windows contains a built-in ping utility for running ping tests through the command prompt.
| |
| − |
| |
| − | ==== Configure your Firewall / Anti-Virus Software ====
| |
| − |
| |
| − | Add the following Pervasive PSQL components to your firewall access list:
| |
| − |
| |
| − | For Pervasive PSQL Server, ntdbsmgr.exe.
| |
| − | For Pervasive PSQL Workgroup, w3dbsmgr.exe.
| |
| − | For the entire Empire directory wither from the server and the mapped drive.
| |
| − |
| |
| − | If you want to opens ports, Pervasive PSQL communicates via the following:
| |
| − |
| |
| − | 3351 for the transactional interface, 1583 for the relational interface, and 139 for named pipes.
| |
| − |
| |
| − | Note that opening a port opens it for all access, not just for Pervasive PSQL.
| |
