====== No Terminals Available for selection ======


===== Information / Common Issues =====
There are a few reasons that terminals might not show in the list.
  * The most obvious is that they are in use
  * The terminal is hung in Pervasive
  * Insufficient permissions to access that network resource
  * Firewall software blocking the connection


===== No Terminals Available for selection #1 =====



==== Problem ====
Customer could not open System Five from 1 client terminal. The original issue was a [[faq:pvsw-errors:status_116|Status 116 error on Master.btr]]

==== Troubleshooting steps ====
  - Looked at security, but the station had only had windows updates done recently and been connected to the internet
  - Looked at network configuration and made sure the Server Pinged correctly.
  - Setup a host file entry for the server ip address
  - Tested connection to pervasive with the Pervasive System Analyzer. I found that TCP/IP was not working, but netbios was.
  - Turned off the firewall on the server. 

==== Cause ====
  * The error was caused by the firewall on the server having been configured to block TCP/IP traffic from the client PC



==== Resolution ====
We turned off the Firewall and everything worked.
  - Ordered List Item
  - Enable NetBios over TCP/IP
  - Remove any bad hosts file entrys in c:\windows\system32\drivers\etc\hosts
  - Set TCP/IP timeouts to avoid the two hour delay (see article...)
  - Ensure that Name Resolution (DNS) is working properly by pinging Pervasive server by DNS name and correct IP is returned
  - Ensure System has R/W access to data files