Question or Problem: Lost of connectivity on Terminal(s) in the network.
Equipment or Software affected: Terminals in the network
Solution:
UDP lets you send network packets. If a UDP packet you send gets dropped, you never find out about it and nobody will help you retry. It is important that the ordyx terminals are well connected, and the firewall settings are adjusted properly.
When attempting to troubleshoot a UDP issue it is important to note that all steps below should be performed on all terminals in the network. Due to the nature of UDP communication issues, any terminal on the network could be the cause.
The most common causes of UDP issues on a network are the firewall being enabled or the exemption not being correctly added to windows defender. In order for the UDP connectivity issue to be resolved, it is important to disable the windows firewall and add an exemption for
C:\restoware to Windows Defender.
If both of the settings are correct from the previous step and the UDP is still unresolved, the next thing to look into is the physical network. Check that all terminals are properly plugged into the LAN. If a terminal is on another network the UDP will never resolve. In addition a device called a Sonicwall will cause connectivity issues and should be removed from the network if present.
If the UDP issue still persists the next step is to look for a DNS Suffix issued from the Router on the network. This process is explained in the Article Disabling DNS Suffix located in the Knowledge Base.
We need to test whether UDP messages are coming in. If they are not, we need to test whether UDP in general is working. In order to do so, download the UDPmulticasttesttool.zip in each TS. Open the zip file in order to install the "MulticastTestTool.Net Lite" application.
Test Ordyx UDP:
Start the application and enter 230.0.0.1 as the multicast address and 4426 as the port. Check the "Listen to inbound traffic" and press the Start button. You should see the count of incoming packets received increase. If it does not, press the Stop button and check both "Listen to inbound traffic" and "Generate outbound traffic", press Start, let the counters increment to about 20, press Stop, uncheck "Generate outbound traffic", press Start button.
Test UDP:
Exit the application in both terminals and restart it in order to use the default settings. Select "Generate ..." and "Listen ..." in one terminal while selecting only "Listen" on the other terminal. Press the Start button of the app on both terminals and see if the UDP generated by the one terminal is heard on both.
Related Articles
Network Troubleshooting
How to Troubleshoot a network by steps: Tonic is not responsible for the customer's network, however Tonic support will help the customer troubleshoot their network. When we receive a call from a store that stated they have communication/connectivity ...
Network Troubleshooting (Public)
Network troubleshooting steps: You as an Ordyx customer are responsible for your network, however Ordyx support will help you troubleshoot. Follow the steps below to troubleshoot a network: 1. Unplug the Ethernet cable, and plug it back in. 2. Make ...
Terminals
Terminals This section brings up a list of all of the terminals and Apple devices that are provisioned. It can be filtered by area with the dropdown menu. The customers can see the list, number, ID, Area, the CD count and which CD it is and the ...
Ordyx Network Configuration
Ordyx Network configuration In order for terminals to communicate effectively, the proper network setup has to be implemented. All network devices (computers, printers, handhelds, etc…) must be on the same network. This is essential for the sharing ...
Network Printer Troubleshoot
Steps to Troubleshoot a Network printer: Follow the steps below to troubleshoot a Network Printer. Do keep in mind Tonic is not responsible for the customer printer, however Tonic Support will help the customer troubleshoot their network printer. 1. ...