>>>>Hi all,
>>>>
>>>>I've cmoe across a weird situation that I can't get around. A customer has an SQL instance on a server and we want to start using it. Standard enough so far and I wrote a small prg that connect to the SQL server and inserts a row. On the Server it works no problem, with both windows authentication and SQL authentication in the connection string.
>>>>The problem is that on the network if I try to run this simple program it fails. The program does not make a connection to the server. I have tried opening ports on the server and the client pc but no difference. I have also tried turning off the AV but no difference. I've gotten it to the point where I can telnet to the server on port 1433 but still the connection fails. Initially the telnet was failing as well but I changed the dynamic port in the SQL configuration.
>>>>On a different client PC i installed sql server 2008 and then was able to use my program to insert into the SQL database on the server, but I can't go installing SQL on every client PC.
>>>>Server is Win server 2008R2 and SQL server 2008. There were 3 instances of SQL running, 2 have now been uninstalled as they are no longer used.
>>>>Any idea on what to try next or any tool to use? I've googled and confirmed all the regular settings are correct.
>>>>
>>>>~M
>>>
>>>I'll bet you it's the firewall. I had the same issue when I set it up on our network. I even made a blog post about my experience:
>>>
>>>http://mattslay.com/opening-up-sql-server-to-allow-remote-connections/
>>>
>>Thanks Matt,
>>I've tried opening 1433 and udp 1434 on the server and client, telnet works but not sql connection.
>>~M
>
>
>Check these settings in Sql Server Configuration Manager:
>
>http://content.screencast.com/users/MattSlay/folders/Snagit/media/84dbcab5-aa7e-4867-a6e5-6cef7040e40a/11.05.2015-11.35.png
>
Thanks Matt,
yes they are all set as shown on screen.
~M