![]() ![]() ![]() Netutil issues a DNS PTR query for _retailnext._tcp.local. The default IP is 35.239.184.87.ĭetails of the discovery methods used by Network Utility are provided below for reference. Xovis: netutil connects to TCP port 443 on the specified remote manager IP.īrickstream: netutil connects to TCP port 2375 on the specified remote manager IP. This test ensures that the sensors will be able to connect to and communicate with their respective remote management application.Īurora: This test is not performed for Auroras as they use the RetailNext Cloud for remote management. Xovis/Brickstream: netutil connects to TCP port 443 on each of the cloud endpoint IPs listed under the "Stereo Sensors" section in the Network Requirements document. This test ensures that the sensors will be able to connect to and communicate with the RetailNext cloud endpoints.Īurora: netutil connects to TCP port 8278 on each of the cloud endpoint IPs listed under the "Aurora" section in the Network Requirements document. Xovis/Brickstream: netutil queries the specified NTP server for time information and also performs some additional validation on the NTP server response. This test ensures that the sensors will be able to properly synchronize time using the configured NTP server.Īurora: This test is not performed for Auroras as they use the RetailNext Cloud for time synchronization and hence do not require an NTP server. It then confirms that the IP in the returned A record matches the cloud Xovis/Brickstream endpoint IP 35.244.170.41. ![]() Xovis/Brickstream: netutil queries the DNS server for A records for .net. It then confirms that the IP in the returned A record matches the cloud Aurora endpoint IP 104.154.145.235. This test ensures that the sensors will be able to resolve the cloud endpoint to an IP using the DNS server supplied by the local DHCP server (or the user, if using Static IP).Īurora: netutil queries the DNS server for A records for .net. You do not, however, need to run netutil as root as it will automatically try to acquire root access using sudo, and if that fails, then su. On Mac and Linux PCs, netutil requires root access to run the DHCP test as port 68 is a "privileged" port on Unix-like systems. If a response is received, netutil confirms that it contains a DNS server IP. It then waits a few seconds for a matching DHCPOFFER response back from a DHCP server. Netutil binds to UDP port 68 on your PC and broadcasts a DHCPDISCOVER request to UDP port 67 on the broadcast IP address ( 255.255.255.255). This test ensures that a sensor set to DHCP will be able to obtain an IP address as well as the DNS server's IP via the local DHCP server. The test is skipped if you select the Static IP option. If you are ready to run the tests, hit ENTER.ĭetails of the network tests run by Network Utility are provided below for reference. If you need to make any changes to comply, hit Ctrl+C or close the window to exit the tool, then make the necessary changes and re-run the tool. Network Utility will now display some instructions before initiating the tests. Specify the exact same Remote Manager here that is used by the sensors in the store. If you specified either Xovis or Brickstream as the sensor type, you will be prompted to enter the Remote Manager IP address. Specify Remote Manager (for Xovis or Brickstream only) Specify the exact same NTP server here that is used by the sensors in the store. If you specified either Xovis or Brickstream as the sensor type, you will be prompted to enter the NTP server information (hostname or IP address). Specify NTP server (for Xovis or Brickstream only) This step is skipped if you specified a DHCP network type, as this information is provided by the DHCP server. Specify the exact same DNS server here that is used by the sensors in the store. ![]() If you specified static IP as the network type, you will be prompted to enter the DNS server IP address. ![]()
0 Comments
Leave a Reply. |