|
I've looked over the internet and can't find a solution to my problem. I have a script that goes in the registry and creates the proper entries to connect to a SQL database using SQL Authentication. The issue I've run into is that some workstations in our environment are defaulted as Named Pipes instead of TCP/IP for the network library configuration for a connection.
This causes two scenarios..
configured TCP/IP before script - creates the new ODBC connection and runs perfectly with the SQL server.
configured Named pipes before script - creates the new ODBC connection fails.
I've gone through the registry of both machines and haven't found any settings that are altered when the Named Pipes is changed to TCP/IP for default ODBC connections that are created. Does anyone know where to change this value so I can add it to my script to force workstations pre-configured as Named Pipes to use TCP/IP for my new DSN?
| 
