Description: When troubleshooting the inability to process transactions, we may need to verify whether the line of communication from the Interface terminal and/or server to the UTG is open. One method of doing so is a Browser Test, which is used to validate that the UTG is able to receive communication over a specified port to the UTG's configured IP address. It should be noted that a Browser Test does require bringing up the UTG Stand Alone.To perform the browser test, please perform the steps outlined in the article below.
Verify the IP Address and Port Number that the Interface is using for communication as well as the Task Description -- this is the name of your configured API Interface, often the interface name.
Then, stop the UTG Service if it is running and start the UTG Stand Alone before opening up a Web Browser on the machine (i.e. Internet Explorer, Chrome or Firefox). In the Address Bar, type in HTTP://[ipaddress]:[portnumber] or HTTPS://[ipaddress]:[portnumber] if the merchant is using a SSL connection. The IP Address and Port Number are the values collected in Step 1. Note that we are not looking for any activity in the browser itself; a "Can't Display Webpage" or similar message is completely normal.
Leaving this window open, look in the UTG Stand Alone for an entry for [TaskDescription].1 (RPRO in above example) which will have a status of Ready or Available (what status displays is irrelevant) where [TaskDescription] is the value collected in Step 1. This will be located somewhere below the Global Status section, under the [TaskDescription] Waiting entry which will display at all times.
If the line exists, then communication to the UTG's IP Address over the Port Number listed is possible over the network. Troubleshooting should then be directed to configuration in the UTG, Interface and possibly Windows Firewall.
If the line does not exist, (and we see just TaskDescription Waiting) then the attempt to communicate is never reaching the UTG. This indicates a networking restriction, likely on the Port in question, and will need to be addressed by the merchant's IT.