NOTE: This article focuses on two tests that can be performed to help solve merchant Ethernet device communication issues efficiently.
In the event that a merchant reports issues with Ethernet connecting device communication, there are two types of tests that can be performed in their local area network (LAN): ping and telnet.
One of the many forms that a device and UTG can exchange communication for credit card processing is via Ethernet. Essentially, the device will be assigned an IP (must be set to static) and configured to speak through a registered port (default to 12000). Furthermore, this would consist of the device performing as a node in a merchant’s LAN.
What is the difference between the two? A ping test determines if the device is able to receive information and the telnet determines if it can send information.
An easier way of explaining this is the matter of two people establishing a phone conversation. If you are going to check to see if someone is available to speak, you would call them. A ping test serves as that purpose as the device will be alerted to receive information and confirm the receipt of the data. On the other hand, when a person needs to verify if their phone service is active, they may contact their phone carrier to see if they have the ability to make phone calls. From that standpoint, a telnet test serves as the purpose to check if the port is open; the port used by the UTG (sending communication given by the interface) and device (carrying card information) to communicate with one another for credit card processing.
Which test should be performed first? Ping! Yes - running a ping test will surely determine if the device is responsive. After all, a responsive device is a happy one. Well...it would make the merchant happy to know that the device is capable to perform the functions needed to run credit card transactions.
A ping test can be performed by opening a Command Prompt, See How do I access Windows Command Prompt or PowerShell?
- Once the window is open, type the command ping "IP OF TERMINAL" (sans quotes) EX: ping 192.168.1.100
- You will either see a timeout if unreachable, or you will see a Reply from the device.
- Each test returns four results. All results with either fail or pass.
- Please keep in mind that being able to ping an IP does not necessarily mean the device is unobstructed.
- It is possible that the port in use is blocked still on the network or that another machine could have the same IP.
It is best after getting a valid result to disconnect the device cable then ping again to confirm it fails to ensure we are speaking to just the device and not another point on their network.