Samuel

OK, that worked! Actually I didn't use the IP address; what I did was to replace the term in the Managed Connection: "ServerName\MSSqlInstanceName" (in this case ISW-OW-01\ORDERWISE") with just "ServerName" (so "ISW-OW-01").

I know I've seen this before (same customer, different system) and that was how I fixed it, but memory had dimmed in the intervening couple of years. What gave me the clue was looking back at that PowerShell stuff, in which I had only specified ServerName, with no mention of InstanceName.

But... problem solved, at last! I really need to write all this crud down on a cheat-sheet so it doesn't trip me up again. In this case "ServerName\InstanceName" worked in development (which is obviously with just my dev machine) and on the server where I deploy the program, but not on the remote workstations, while just "ServerName" works everywhere. Why? Beats the heck out of me.

Mike