System, Hardware and Network Requirements

Computer Requirements

The general requirements vary depending on the level of functionality that is needed:

• Cashier: A Windows-based PC or laptop is required in order to interact with the receipt printer, biometrics and EMV reader
• Back office or off-site: Any OS PC/laptop/tablet will work as long as it can install client certificates
  • Any browser besides Internet Explorer will work on Windows
  • Chrome and Firefox can install certificates on Mac and Linux
  • Only Safari works on iOS
• Mobile Valet: iOS only
• Loyalty Apps: Android and iOS

Note: The specs for the device do not matter as long as it is capable of browsing the Internet.

Network Requirements

PDF – netPark-NetworkInformationV2

PDF – netPark Pay – Flow and Network Diagram

Our data requirements are pretty small. For regular netPark use (anything excluding Damage Pictures and LPR), a standard 5Mbps Down, 1Mps Up should be sufficient. The better the latency, the more responsive the system will feel. If you are planning on taking automated damage images or doing LPR, a larger connection will be needed. In this case we would recommend 25Mbps Down, 10Mbps Up as a minimum for a 2 lanes in, 2 lanes out configuration. Higher bandwidth may be required if the are several self park devices running.

Firewall Configuration

netPark does not need any inbound access to your network. We only connect out to our cloud service. These are the requirements needed for all of the various connections.

Outbound Firewall Requirements

Outbound TCP 443 to “np1.netpark.us” – Required for all netPark use (POS or Self-Park)

• Continuous use
• Used by PCs, mobile devices, and the NIM to access the netPark system
• Multiple and variable IPs for load balancing and availability

Outbound TCP 8667 to “uniterm.netpark.us” – Required for all MONETRA EMV “chip and pin” terminals (POS or Self-Park)

• Continuous use
• Used by Ingenico EMV devices for credit card processing
• Multiple and variable IPs for load balancing and availability

Outbound TCP 443 to “tripos.vantiv.com” – Required for all NETPARK PAY EMV “chip and pin” cashier terminals

• Continuous use
• Used by Verifone and Ingenico EMV devices for credit card processing

Outbound TCP/UDP 9001 to “device.tripos.vantiv.com” – Required for all NETPARK PAY EMV “chip and pin” cashier terminals

• Continuous use
• Used by Verifone and Ingenico EMV devices for credit card processing

Outbound TCP 443 to “iptran1.dsipscs.com” (Required for all netPark Pay EMV unattended terminals)

• Continuous use
• Used by Ingenico EMV devices for credit card processing at self park devices

Outbound TCP 443 to “iptran2.dsipscs.com” (Required for all netPark Pay EMV unattended terminals)

• Continuous use
• Used by Ingenico EMV devices for credit card processing at self park devices

Outbound TCP 5080 to “trancloud.dsipscs.com” (Required for all netPark Pay EMV unattended terminals)

• Continuous use
• Used by Ingenico EMV devices for credit card processing at self park devices

Outbound TCP 443 to “prod.ssl53.com” (Required for all netPark Pay EMV unattended terminals)

• Continuous use
• Used by Ingenico EMV devices for credit card processing at self park devices

Outbound UDP 53 to “8.8.8.8/8.8.4.4” – DNS Servers for NIM (we’ll use alternatives if provided)

• Continuous use
• DNS Resolution
• Google’s public DNS servers

Outbound TCP 443 to “d2b9y0lpx8949m.cloudfront.net” – Used for retrieving netPark CDN images and files

• Continuous use
• Used for the Desktop Application and NIM
• Multiple and variable IPs for load balancing and availability

Outbound TCP/UDP 5938 to “*.teamviewer.com” and “*.dyngate.com” – Used for TeamViewer Remote Support

• Continuous or may be restricted by client until needed
• For TeamViewer remote PC support (see “TeamViewer Remote Support” below)
• Multiple and variable IPs for load balancing and availability

Outbound UDP 1194 to “nama.netpark.us” – Remote access to NIM for Self Park facilities

• Should be restricted by client until needed
• For remote NIM support
• Multiple and variable IPs for load balancing and availability

Outbound TCP 587 to “mail.netpark.us” – Used by NIMs to mail diagnostic logs

• Continuous or may be restricted by client until needed
• Automatic email of NIM diagnostic logs for technical support
• Multiple and variable IPs for load balancing and availability

Self Park Equipment Requirements

If your location is also having self-park equipment installed, below is a list of network information required for configuration of the netPark supplied self-park equipment. We will need the below information before we can ship out any equipment from netPark.

If you have any questions, please let your netPark Sales Representative know.

Network Information Requirements

Before netPark can ship any equipment to the location, we need to know the following details:

• Static IP Addresses
  • 1 Private, internal static IP – NIM
  • 1 Private, internal static IP per – self park device, damage/lpr camera and ADAM device
• Dynamic IP Addresses
  • 1 DHCP-Assigned, internal IP per – TranCloud EMV Terminal
  • DHCP-Assigned addresses can be MAC Address locked
• Subnet
• Gateway

TeamViewer (T.V.) Remote PC Support

We do not have full-time access to client networks or devices. When remote assistance is needed we have the user initialize the support session so they are in full control. This is the standard process:

1. First, the user contacts netPark support to request a support session
2. The user is then asked to activate the customized netPark support client*
   1. This is typically done through the Desktop Application
   2. If the Desktop Application is not available, users are typically directed to http://www.netparkhelp.com or https://www.netpark.us/support
3. Once the client is activated, assuming firewall permissions are enabled, T.V. will prompt the client to allow or deny session
4. If user grants access, the session is initialized
5. At any point during the session the user can terminate the connection by closing the application or restarting the computer
6. Once the session is terminated, the process must be repeated before a new session can be established

* This client does not get installed on the PC and is only active for the duration of the support session