Connection Failed: SQL State: 'S1T00' / SQL Server Login Window

ISSUE:

• User tries to open RFMS and gets the Microsoft SQL Server Login window
• User clicks OK then gets the SQL Server Login window

The 'S1T00' error indicates the workstation cannot communicate with the SQL Server; the authenticated user (Windows user) is timing out on authentication and then is using the RFMSLogon account to connect.

1. Have the users right-click on their RFMS shortcut and select "Run as Admin." Does this allow them in without error? 
    

2. If "Run as Admin" does not resolve the error, have your local technician try pinging the server (by name) from the workstation and verify it's seeing the correct IP address.  If it is, as a test, try disabling the private and domain firewall on the server, and pc if necessary, then relaunch RFMS on the workstation. If the machines connect, turn the firewall back on and try to re-launch RFMS on the workstation. 
   Important: disabling the firewall is only a test, please make sure to re-enable the firewall when done testing.

   If, after reenabling the firewall, the connection is blocked again, your technician should review the firewall to figure out what ports SQL is trying to communicate through and open those. The default ports are TCP 1433, and UDP 1433 & 1434 but there may be other ports that are unique to your environment. Your technician may be able to use Netstat or another utility to assist with this. 
   
   Please note, historically speaking, the SQL ports were typically static but more current SQL installations appear to be installing them as dynamic. Do the following to check ports being used by SQLSRV.EXE.
    

   • Open the SQL Server Configuration Manager
   • Expand SQL Server Network Configuration (in the left side of the configuration manager)
   • Select Protocols for RFMS (or SQLExpress, or the name of the SQL instance if it is something different)
   • Select TCP/IP, right click and go to Properties
   • Go to IP Addresses tab, scroll down to the bottom to the small subsection called “IPAll”, and open the port listed under TCP Dynamic Ports in the firewall at the server and any point between the server and workstation, such as a domain controller.
     For help configuring it to use a fixed port, reference http://msdn.microsoft.com/en-us/library/ms177440.aspx
      
3. We also recommend trying to do an odbc connection to the server to see if it can find the correct Server with SQL instance by selecting SQL Server from list and selecting the drop down. If it pulls server name with SQL instance, select "next." Leave Windows NT Authentication checked and select "next." Does it give an error or take you to the next screen where you can do a drop down for databases? If an error or no databases, the user(s) are not authenticated to the SQL db.

Following is a link to a document with additional information for troubleshooting workstation connections.

• Connect Workstations