A properly configured network will allow Windward Software products to function correctly and free from network errors. Using high-quality network infrastructure components for switches, patch cables, etc will ensure the success of the network.
Who should read this
Your technical IT person will be configuring or maintaining your network. This may be the company that you are purchasing your hardware from or the person that is going to get your workstations talking to each other and to a server if required.
- Windward Software products use the Pervasive.SQL database engine.
- Starting with version 10, Pervasive has a 64-bit engine for 64-bit Operating Systems. Windward Software does support the 64-bit engine on the file server and workstation.
- Pervasive.SQL will need to communicate over the network by the server's name. DNS should resolve properly on the internal network.
- A mapped drive letter is required to run Windward applications.
- UNC (Universal Naming Convention) communication to the server is not supported. (ie: NET USE W: \\server\share)
- A 100 MB network infrastructure is recommended, as a minimum, using category 5e cabling. (If building a 1000MB network you will require category 6 cables.) For more information on this see: https://www.tomsguide.com/reference/ethernet-cables-explained
- A 100 MB switch or better is recommended. The use of network hubs (old technology) are not recommended or supported.
- A DSN driven network using the TCP/IP protocol.
- Wireless networking is NOT supported unless it is used for Remote Desktop connectivity. There are NO other exceptions.
Please consult your computer and network technician to ensure you have these devices configured.
Some Useful articles on Securing your Physical Location
- A mapped drive letter to the server will need to be in place. We recommend drive W: mapped to a share on the server, generally named “WINDWARD” with full Read and Write permissions. Read and write permissions will need to be configured for all users and administrators on each workstation computer that will be accessing the “WINDWARD” share. Please consult with your computer tech for making these permissions changes if you need assistance.
- Network printing with printer queues is recommended.
- Ideally, if you are planning to run System Five over terminal services, plan on purchasing networkable printers that have built-in network cards, and configure your remote locations to connect using a VPN. In this manner, all printers look like they are on the same network, and the remote computers will print to them as though they exist on the server's local network. This is much more reliable and easier to configure and maintain connections than trying to use remote printing. This would apply to both laser printers and thermal receipt printers.
Peer to Peer configurations
- A standard TCP/IP based network infrastructure is required.
Terminal Services configurations
- A standard TCP/IP based network infrastructure is required with a server installed with a Microsoft Windows Server Family operating system. These operating systems include:
- Windows Server 2008 R2 (64-bit Only) Enterprise, Standard, and Foundation
- Windows Server 2008 Enterprise, Datacenter, and Standard
- Windows Small Business Server 2008 (64-bit Only) Premium and Standard
- Windows Small Business Server 2011 Premium and Standard
- Windows Server 2012 R2
- Windows Server 2012 Foundation, Essential, Standard, Datacenter
- Windows Server 2016 Essential, Standard, Datacenter
- All operating systems listed above are based on running the most current version of Actian's Pervasive Client and Server engines.
- All previous Windows Server operating systems are no longer supported by Microsoft, nor are they supported by (Actian (formerly Pervasive), so they should not be used for new installations of System Five.
- Microsoft Active Directory (AD) is not required but will still function suitably.
- Ensure your network share to be used is set to both R/W (read and write) access.
- Ensure a static IP address is set on the server to avoid the server changing its IP address during operation.
- DNS should resolve properly
- Keep server name simple, i.e. “server” or “server2k3”
- If using a workgroup, user accounts used to sign into the workstation should also exist on the server.
- If using a domain, ensure it is configured correctly, with correct user permissions. (A Windows Domain is not required but normally a good idea for network administration)