Network Configuration – Best Practices
The world has changed in many ways and computing devices are becoming more mobile and data is rapidly moving into widely distributed environments. It is clear and increasingly necessary that industries evolve to provide solutions utilizing private and public communications methods in a safe and secure way. This ranges from large scale complex computer networks down to the simplest of IoT devices. Somewhere in the middle of all this, lies Physical Access Control Systems (PACS) and Video Surveillance such as those offered by Amano McGann.
Before we begin, it is our recommendation that you consult a network engineer or other professional when configuring your network, especially in cases involving access communications outside your local area network. In general, network configuration lies outside the scope of the access control software and must be configured properly to allow our system to function.
Our products and systems do not have any problem communicating over LAN, WAN and VPN networks where routing is done properly. Wherever possible, avoid the use of NAT rules, port forwarding, public IP addresses, and the like and instead connect our system components within the same LAN. If you must connect in any a scenario other than one on a LAN, you may experience difficulty with installation and day to day communications, especially when using public IP Addresses.
If you choose to utilize a public IP addresses (anything other than RFC1918 addresses), NAT rules, port forwarding, public IP addresses, etc. please be aware that we will NOT be able to support or troubleshoot communications issues you experience.
Routers, managed switches, and other complex networking components must be set up by network professionals. If you must implement complex networking configurations, please realize that you may be utilizing a bit of a trial and error to setup and communicate with various components in the system.
Network Requirements Specification
Communications
- 100Mbps Ethernet Network Interface (between Hardware and Server/Clients)
- LAN, VPN and most properly configured WANs are supported.
- Static IP addresses are strongly recommended for all system components including the server(s).
NOTE: While technically possible, hardware connected via the Internet using NAT Translation, port forwarding, public IP (non RFC1918 addresses) is not supported. Please use a Local LAN whenever possible.
Remote Client Connection
When using a remote client computer, you must be able to communicate with the server via IP address or DNS name on the assigned TCP Port (defaults listed below).
Network Ports
Both TCP and UDP protocols are utilized and require the following ports be open for the listed components.
Related Docs:
Address Allocation for Private Internets – https://tools.ietf.org/html/rfc1918
Need further assistance?
