>>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
>
>Some suggestions:
>1. On the server open SQL Configuration Manager, right mouse click on the Protocols for MSSQLSERVER (or whatever is the name) and make sure that TCP/IP is enabled.
>2. Then Right Mouse click on TCP/IP and make sure that IPALL 1433 is Active.
>
>HTH.
Hi Dmitry,
yes I've checked the TCP/IP settings.
1433 is the port specified in all TCP/IP settings and TCP/IP is enabled in every configuratino section. In IPALL the ip is 1433 with a dynamic of 53001, I have added both to the firewall on both a client and the server.
~M