Difference between revisions of "Networking"

From Rts
Jump to: navigation, search
m
Line 1: Line 1:
'''Best Practices'''
+
====Best Practices====
  
 
Assign a static IP address to each machine running RTS software.  Ensure that the addresses are outside the DHCP range for your network.  If this is not done, a router failure or DHCP problem will cause machines to fail when connecting to the server.
 
Assign a static IP address to each machine running RTS software.  Ensure that the addresses are outside the DHCP range for your network.  If this is not done, a router failure or DHCP problem will cause machines to fail when connecting to the server.
Line 9: Line 9:
 
Do not connect a protected WIFI network to the RTS network with a password given to all employees.
 
Do not connect a protected WIFI network to the RTS network with a password given to all employees.
  
'''Internet Ticketing'''
+
====Internet Ticketing====
  
 
A static public IP is not required for your Internet connection unless using MovieTickets.com.  You should forward TCP ports 2235, 80, and 443 to your RTS server.  If you do not forward 80 and 443 certain corporate customer computers will not be able to purchase internet tickets.
 
A static public IP is not required for your Internet connection unless using MovieTickets.com.  You should forward TCP ports 2235, 80, and 443 to your RTS server.  If you do not forward 80 and 443 certain corporate customer computers will not be able to purchase internet tickets.
Line 15: Line 15:
 
Port 2237 is no longer required to be forwarded and should be removed from your forwarding rules.
 
Port 2237 is no longer required to be forwarded and should be removed from your forwarding rules.
  
'''Digital Signs - Chromecasts'''
+
====Digital Signs - Chromecasts====
  
 
If using Chromecasts for digital signage, Google requires a DHCP server.  The DHCP server should assign addresses in the point of sale network range.  Chromecasts must have internet access.
 
If using Chromecasts for digital signage, Google requires a DHCP server.  The DHCP server should assign addresses in the point of sale network range.  Chromecasts must have internet access.

Revision as of 23:29, 1 January 2018

Best Practices

Assign a static IP address to each machine running RTS software. Ensure that the addresses are outside the DHCP range for your network. If this is not done, a router failure or DHCP problem will cause machines to fail when connecting to the server.

Enable a DHCP server for the point of sale network.

Do not connect an Open WIFI network to the point of sale network.

Do not connect a protected WIFI network to the RTS network with a password given to all employees.

Internet Ticketing

A static public IP is not required for your Internet connection unless using MovieTickets.com. You should forward TCP ports 2235, 80, and 443 to your RTS server. If you do not forward 80 and 443 certain corporate customer computers will not be able to purchase internet tickets.

Port 2237 is no longer required to be forwarded and should be removed from your forwarding rules.

Digital Signs - Chromecasts

If using Chromecasts for digital signage, Google requires a DHCP server. The DHCP server should assign addresses in the point of sale network range. Chromecasts must have internet access.