SQL Not Responding

First make sure that the technician at the location has the internet plugged into the WAN of the Fortinet and LAN on the Fortinet is plugged into the computer. This will create 2 static IP addresses the Fortinet IP address will be 172.16.100.1 and the computer IP address will be 172.16.100.2. If the technician has the internet plugged directly into the computer it will pull it's own IP address which will likely be 192.168.1.X. This will be the wrong IP. To check to make sure the static IP's are set, do the following. 1. Control Panel 2. Network 3. Change Adapter 4. Ethernet right click 5. Properties 6. Choose TCP/IPv4 right click 7. Properties 8. If the internet is plugged in WAN on Fortinet and LAN is plugged into Computer use the following addresses if nothing appears in the address box. IP: 172.16.100.1 Subnet Mask: 255.255.0.0 Gateway: 172.16.100.2 DNS: 8.8.8.8 Alternate DNS: 8.8.4.4 If there is a different IP address and there is no technician available at the site do the following. 1. On kiosk open the (D:) 2. M3 Kiosk 3. Kiosk2.exe (config) open in notepad. 4. Find Kiosk2setting -- value should read should read 172.16.100.2, but enter whichever IP address they have created such as 192.168.10. X this will bypass the Fortinet and will bring up the SQL 5. Close and it will save the setting. If technician is at the site, make sure they attach internet to WAN on Fortinet and LAN from Fortinet is plugged into the computer.

SQL not responding due to wrong IP address
First make sure that the technician at the location has the internet plugged into the WAN of the Fortinet and LAN on the Fortinet is plugged into the comput...
Wed, 3 Apr, 2019 at 4:20 PM