User Tools

Site Tools


faq:multilocation_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:multilocation_networking_best_practices [2017/07/24 10:09 (7 years ago)] – [Printing principles] swindfaq:multilocation_networking_best_practices [2022/03/11 09:48 (2 years ago)] (current) swind
Line 1: Line 1:
 ====== Networking Multiple Locations Best Practices ====== ====== Networking Multiple Locations Best Practices ======
 +
 +<note important>This document is also available as a FreshDesk Solution Article \\
 +</note>
 +
 Read the [[faq:windows_networking_best_practices|Networking Best Practices]] as a starting point.  Building a network infrastructure for multiple locations may be for several reasons.  You may have a second retail establishment, a warehouse, have remote administration requirements or just allowing sales people to dial in from a hotel room. Read the [[faq:windows_networking_best_practices|Networking Best Practices]] as a starting point.  Building a network infrastructure for multiple locations may be for several reasons.  You may have a second retail establishment, a warehouse, have remote administration requirements or just allowing sales people to dial in from a hotel room.
  
Line 22: Line 26:
   - Purchase hardware that is a currently supported Microsoft compatible server.   - Purchase hardware that is a currently supported Microsoft compatible server.
   - Microsoft Small Business (SBS) server **does NOT** allow user based terminal server sessions and can not be used for this purpose.  Purchase Standard or Enterprise server solutions.   - Microsoft Small Business (SBS) server **does NOT** allow user based terminal server sessions and can not be used for this purpose.  Purchase Standard or Enterprise server solutions.
-  - A VPN network is recommended but not required unless using integrated credit / debit card processing for PCI compliance. DO NOT USE VPN FOR DIRECT DRIVE MAPPING+  - A VPN network is recommended but not required unless using integrated credit / debit card processing for PCI compliance. <color #ed1c24>__DO NOT USE VPN FOR DIRECT DRIVE MAPPING__</color>
   - Use of strong passwords is strongly recommended   - Use of strong passwords is strongly recommended
  
Line 44: Line 48:
 <note tip><HTML><H2 align=center>A BETTER SOLUTION</H2></HTML> <note tip><HTML><H2 align=center>A BETTER SOLUTION</H2></HTML>
  
-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 with fixed (static)external IP Addresses. 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 more reliable, and easier to configure and maintain the connections than trying to use remote printing. This method would apply to both laser printers and thermal receipt printers. +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 with fixed (static) external IP Addresses. 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. Also the only driver involved would be the one on the server, so the Microsoft Easy Print Driver will not intercept the print job. This is more reliable, and easier to configure and maintain the connections than trying to use remote printing. This method would apply to both laser printers and thermal receipt printers. 
  
 </note> </note>
faq/multilocation_networking_best_practices.1500916186.txt.gz · Last modified: 2017/07/24 10:09 (7 years ago) by swind