Test Shift4 UTG Connection with Telnet
If everything seems to be configured correctly (IP address, Port, Firewall Router, UTG and Execu/Tech software) but you're still getting a Winsock error, then the UTG is either not running, not working properly, running on a different port than specified, or something is blocking the connection.
Verify that the Shift4 UTG service or "Stand alone" is running. If it isn't, your connection attempts will fail.
Changing the port number in the UTG service will require the assistance of Shift4. Contact Shift4 Support.
If the connection is failing with Telnet, Execu/Tech will not be able to assist in resolving the problem. Please contact a qualified network technician to assist you.

|
If you've tried everything and still can't get it to work, it may be that ports are still being blocked outside of the known firewalls. Try changing the port on which the
UTG is listening. Instructions are at the bottom of this page.
|
The Error
When attempting to process a credit card from within Execu/Tech software, you might see this error if there is a communication failure between our software and Shift4's UTG software.
Winsock error 10060 The attempt to connect timed out
Press <Ok> to retry.

|
Telnet Test
You can test this connection by using Telnet.
- You may need to install Telnet. You can do this from an elevated command prompt with this command:
dism /online /Enable-Feature /FeatureName:TelnetClient
To test the connection, open a Command Prompt and type:
telnet 192.168.1.10 17476
|
- Replace 192.168.1.10 with the IP address of the computer where the UTG was installed.
- 17476 is the default port number, but if your UTG uses a different port, replace it.
|
Successful Connection
If the connection is successful, you'll see a blank window with only a cursor. This is because the UTG doesn't respond with anything upon connection.
|
Failed Connection
If the connection failed, you may see something like this.
If you see anything other than a successful connection, it is the responsibility of your network technician and Shift4 to resolve the problem.
Until Windows can communicate with the UTG, Execu/Tech will not be able to communicate with the UTG.

|
|