0

There are 6 workstations and all but 1 can connect to SQL Server using the exact same connection string. So the SQL engine is obviously running and the issue is not centralized at server level (e.g. "Allow network connections to this server", "Maximum number of concurrent connections", "Named pipes"). Checked the firewall on the station and it's OFF at all levels. Even tried to add incoming and outgoing firewall rules for TCP 1433 and UDP 1434 with no effect. I tried to connect using the IP address of the server instead of its name in case there might be a name resolution issue between stations, but nope.

What else should I be checking on that workstation?

Thanks

Dale K
  • 25,246
  • 15
  • 42
  • 71
Mike
  • 79
  • 9
  • Can you ping? Tracert? Telnet to port 1433 or 1434? Test-Netconnection? Is it a named instance? – Aaron Bertrand Apr 07 '22 at 22:09
  • What's the exact error? Is TCP/IP enabled in the client protocols on the workstations? Reaching, but maybe a firewall rule on the SQL Server host machine explicitly blocking the workstation? – squillman Apr 07 '22 at 22:12
  • Please [Edit](https://stackoverflow.com/posts/71789463/edit) your question to include the full and complete error message - as text. The error message may contain important information pointing to many different causes, including older/incompatible ODBC drivers, improper configuration of TLS client protocols, etc.. Also include the output of `SELECT @@VERSION` from the target SQL Server. – AlwaysLearning Apr 07 '22 at 22:14
  • to add to @AlwaysLearning comment, please note if this is also On-Prem or Cloud SqlServer – J.S. Orris Apr 07 '22 at 22:19

0 Answers0