User Tools

Site Tools


faq:windows_networking_best_practices

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
faq:windows_networking_best_practices [2007/03/29 12:06 (17 years ago)] bobfaq: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.  Use high quality network infrastructure components for switches, patch cables, etc will ensure the networks success. +See [[https://support.windwardsoftware.com/a/solutions/articles/66000475753]]
- +
-===== Who should read this ===== +
-Your technical IT person 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 and to a server if required. +
- +
-===== Product overview ===== +
-  - Windward Software products use the Pervasive.SQL database engine. +
-  - Pervasive.SQL will need to communicate over the network by the servers name. +
-  - A mapped drive letter is required to run Windward applications.  UNC (Universal Naming Convention) communication to the server is not supported. +
- +
-===== 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. +
-  - The TCP/IP protocol is required. +
-  - A properly configured DNS or other name resolution service should be in place.  (You should be able to PING your server by 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 system 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 both R/W (read and write) access. +
-  - Ensure 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. "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 W: mapped to a share on the server, generally named "WINDWARD" with full R/W permissions.+
faq/windows_networking_best_practices.1175195160.txt.gz · Last modified: 2007/03/29 12:06 (17 years ago) by bob