OK, I am not sure where to look for this...
I have a process I created that by using a vbs file and a batch file, I can have a coworker batch create about 20 DSNs on various users' computers.
I did this the first time and it worked fine for me, but not on any users' machines.
The users' machines all created the connecting with Named Pipes rather than TCP/IP. As far as I can see, there is not a value in the registry key to set that. I did a test run using the SQL server IP rather than the FQDN and it seemed to work in my test. Now it seems that it is not reliably setting the connection protocol to TCP/IP.
Any suggestions?
I have a process I created that by using a vbs file and a batch file, I can have a coworker batch create about 20 DSNs on various users' computers.
I did this the first time and it worked fine for me, but not on any users' machines.
The users' machines all created the connecting with Named Pipes rather than TCP/IP. As far as I can see, there is not a value in the registry key to set that. I did a test run using the SQL server IP rather than the FQDN and it seemed to work in my test. Now it seems that it is not reliably setting the connection protocol to TCP/IP.
Any suggestions?
