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 revision Previous revision
Next revision
Previous revision
faq:windows_networking_best_practices [2017/03/01 10:37]
swind
faq:windows_networking_best_practices [2020/06/30 14:24] (current)
kevin [Additional Information]
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. ​ Using high quality network infrastructure components for switches, patch cables, etc will ensure the networks ​success.+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 ===== ===== 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 from or the person that is going to get your workstations talking to each other and to a server if required. +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.
- +
  
  
Line 13: Line 11:
 ===== Product overview ===== ===== Product overview =====
   - Windward Software products use the Pervasive.SQL database engine.   - 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. +  - 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. 
-<​note>​NOTE: ​ At the time of writing this article there were still OPOS device drivers that did not have 64 bit support available. An example of this was a Metrologic scale or pole display.</​note>​ +<​note>​NOTE: ​ At the time of writing this article there were still OPOS device drivers that did not have 64-bit support available. An example of this was a Metrologic scale or pole display.</​note>​ 
-    - Pervasive.SQL will need to communicate over the network by the servers ​name. DNS should resolve properly on the internal network.+    - 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.   - 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%%)   - UNC (Universal Naming Convention) communication to the server is not supported. (ie: %%NET USE W: \\server\share%%)
Line 47: Line 45:
   - Network printing with printer queues is recommended.   - 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. ​   http://​thinprint.com and http://​www.terminalworks.com/​ have solutions to address these issues.   - 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. ​   http://​thinprint.com and http://​www.terminalworks.com/​ have solutions to address these issues.
-  - 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. ​ +  - Ideallyif 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. ​
- +
- +
  
  
Line 81: Line 76:
 ==== Server principles ==== ==== Server principles ====
   - Ensure your network share to be used is set to both R/W (read and write) access.   - 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.+  - Ensure a static IP address is set on the server to avoid the server changing its IP address during operation.
   - DNS should resolve properly   - DNS should resolve properly
   - Keep server name simple, i.e. "​server"​ or "​server2k3"​   - 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 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)   - 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>​No wireless database connections to the server. ​ Wireless workstations are ONLY to be connected using Microsoft terminal services or remote desktop. Please see the following article on wireless networks: http://​wiki.wws5.com/​doku.php?​id=faq:​wireless_networks </​note>​ <​note>​No wireless database connections to the server. ​ Wireless workstations are ONLY to be connected using Microsoft terminal services or remote desktop. Please see the following article on wireless networks: http://​wiki.wws5.com/​doku.php?​id=faq:​wireless_networks </​note>​
Line 90: Line 85:
 <note tip>​Additional Microsoft server licensing may be required depending on your requirements. ​ For more information on CAL (Client Access Licensing) [[https://​www.microsoft.com/​en-us/​Licensing/​product-licensing/​client-access-license.aspx]].</​note>​ <note tip>​Additional Microsoft server licensing may be required depending on your requirements. ​ For more information on CAL (Client Access Licensing) [[https://​www.microsoft.com/​en-us/​Licensing/​product-licensing/​client-access-license.aspx]].</​note>​
  
-**Are you networking multiple locations?​** ​ Read the [[faq:​multilocation_networking_best_practices|Networking ​multiple locations ​Best Practices]]. +==== Additional Information ==== 
- +  [[faq:​multilocation_networking_best_practices|Networking ​Multiple Locations ​Best Practices]]. 
- +  * [[:​faq:​network_troubleshooting|Network Troubleshooting]] 
-  ​+  ​* [[:​faq:​backup|Backing up your Windward Software information]]
faq/windows_networking_best_practices.1488393459.txt.gz · Last modified: 2017/03/01 10:37 by swind