I have a clustered SQL 2005 Server using named instances and dynamic ports 1433 and 1815. There is a client application which needs to connect to a SQL db, but struggles with the named instance required.
I.e. configuration string is SQL_SERVER \ SQL_Instance : 1433
This application has a problem, because if I put in SQL_SERVER \ SQL_Instance, it does not even try to connect via 1433. However, if I put in SQL_Server, I can see (via netstat), it tries to connect using 1433, but fails because the instance is missing. There is nothing in the app to adjust port.
I'd rather not make any changes to the server, as it's clustered, and other apps/clients currently connect without issue.
Anything I can do on the client to fool the app maybe? Perhaps an SQL agent which connects to the server properly, and the app then connects locally to the agent? Other ideas?
Last note, this client app actually is on a DMZ, so there is some port restrictions, NAT, and advanced network configuration to make for secure communication.