Differences

This shows you the differences between two versions of the page.

--- faq:windows_networking_best_practices [2007/03/29 11:35 (17 years ago)] – kevin
+++ faq:windows_networking_best_practices [2021/02/27 11:31 (3 years ago)] (current) – tanya
@@ Line 1: / Line 1: @@
 ====== Networking Best Practices ======
-A properly configured network will allow Windward Software products to function correctly and free from networking errors.  Using quality networking components for switches, patch cables for your network infrastructure will ensure your networks success.
+See [[https://support.windwardsoftware.com/a/solutions/articles/66000475753]]
-===== Who should read this =====
-Your technical IT team that will be configuring or maintaining your network.  This may be the company that you are purchasing your hardware or the person that is going to get your workstations talking to each other.
-===== Networking principles =====
-  - A 100 MB network infrastructure is recommended using category 5e cabling.  (If building a 1000MB network you will require category 6 cables.)
-  - A 100 MB switch and NOT a hub is recommended.
-  - A TCP/IP protocol is required.
-  - A properly configured DNS or other name resolution should be in place.  (You should be able to PING your server by name.)
-===== Product overview =====
-  - Windward Software products use the Pervasive.SQL database engine to communicate over your network.
-  - Pervasive.SQL will need to be able to communicate to the database server whether it is in a peer to peer or client/server environment by the servers name.
-===== Peer to Peer configurations =====
-A standard TCP/IP based network infrastructure is required.
-===== Client/Server configurations =====
-A standard TCP/IP based network infrastructure is required with a server installed with a Microsoft Windows Server Family operating systems.  These operating systems include:
-  * Microsoft SBS (Small Business Server)
-  * Microsoft Standard Server
-  * Microsoft Advanced Server
-  * Microsoft Enterprise Server
-==== Server principles ====
-  - Ensure your network share to be used is set to R/W
-  - Ensure a static IP address is set on server.
-  - DNS should resolve properly
-  - Keep server name simple, i.e. "server" or "server2k3"
-  - If using a workgroup, user accounts used to sign into workstation should also exist on the server.
-  - If using a domain, ensure configured correctly with correct permissions.
-<note>No wireless database connections to the server. Wireless PC's are only to be used with Terminal Services.</note>
-==== Workstation principles ====
-  - A mapped drive letter to the server will need to be in place.  We recommend drive F.