faq:windows_networking_best_practices
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
faq:windows_networking_best_practices [2016/03/01 09:03 (8 years ago)] – [Client/Server configurations] swind | faq:windows_networking_best_practices [2021/02/27 11:31 (3 years ago)] (current) – tanya | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Networking Best Practices ====== | ====== Networking Best Practices ====== | ||
- | A properly configured network will allow Windward Software products to function correctly and free from networking errors. | + | See [[https://support.windwardsoftware.com/ |
- | + | ||
- | + | ||
- | ===== Who should read this ===== | + | |
- | Your technical IT person that will be configuring or maintaining your network. | + | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | ===== Product overview ===== | + | |
- | - 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. | + | |
- | < | + | |
- | - Windward Software recommends that all client PC's at this time operate in 32 bit mode. The main reason for this is for device driver support. | + | |
- | - Pervasive.SQL will need to communicate over the network by the servers name. DNS should resolve properly on the internal network. | + | |
- | - A mapped drive letter is required to run Windward applications. | + | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | ===== Networking principles ===== | + | |
- | - A 100 MB network infrastructure is recommended, | + | |
- | - 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 == | + | |
- | + | ||
- | * [[http://technet.microsoft.com/en-ca/ | + | |
- | + | ||
- | ===== Workstation principles ===== | + | |
- | - A mapped drive letter to the server will need to be in place. | + | |
- | + | ||
- | ===== Printing principles ===== | + | |
- | - Network printing with printer queues is recommended. | + | |
- | - There are some known issues printing through terminal services. However, these are not Windward Software issues. They are Microsoft issues that were caused by the introduction of their Easy Print driver. | + | |
- | - 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' | + | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | ===== Peer to Peer configurations ===== | + | |
- | - [[http://wws5.com/ | + | |
- | - A standard TCP/IP based network infrastructure is required. | + | |
- | - [[http:// | + | |
- | + | ||
- | + | ||
- | ===== Client/ | + | |
- | - {{: | + | |
- | - A standard TCP/IP based network infrastructure is required with a server installed with a Microsoft Windows Server Family operating system. | + | |
- | * 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 | + | |
- | + | ||
- | 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. | + | |
- | + | ||
- | + | ||
- | ==== Server principles ==== | + | |
- | - 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 server to avoid the server changing its IP address during operation. | + | |
- | - DNS should resolve properly | + | |
- | - Keep server name simple, i.e. " | + | |
- | - If using a workgroup, user accounts used to sign into 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) | + | |
- | < | + | |
- | + | ||
- | <note tip> | + | |
- | + | ||
- | **Are you networking multiple locations? | + | |
- | + | ||
- | + | ||
- | | + |
faq/windows_networking_best_practices.1456851787.txt.gz · Last modified: 2016/03/01 09:03 (8 years ago) by swind