I have a Standard Ed SQL Server 2005 default instance version 9.00.4053.00 (SP3) running on Standard Edition Windows NT 5.2 (Build 3790: Service Pack 2).
Remote Connections enabled
No Windows Firewall - this is inside our network
SQL Server is running on a NON-Standard port
Alias for SQL Server is created, TCP indicated, port number defined
Connections work fine from both TCP, Named Pipes, and LPC.
I can Telnet to the SQL port and use a UDP port test shows I can remotely connect to SQL Browser 1434.
My Problem is as follows:
I would very much like all connections to use TCP/IP protocol. However, when connections are made with the SQL Browser, or even my Alias (if I turn off SQL Browser) they get made with Named Pipes protocol.
I would like to use TCPIPKEEPALIVE settings inside of an application and on the TCP stack due to a problem application not cleaning up connections. However, I cannot take advantage of this if my SQL Browser or Alias connections won't use TCP/IP protocol.
Please advise me on how to force the browser to use this protocol.
View Complete Post