November 1, 2016 at 11:32 am
Hello,
Have a windows app where we have an outside field that needs access. Right now, they vpn into a machine to access the app on the network (Windows Auth). Want to switch to straight vpn access. Have done everything for SQL Server (FW, Named Pipes, Remote turned on) and can access via ssms from the VPN without any issue.
The Windows App itself will not allow the connection and comes back with the Named Pipes: 40. Does anyone know of anything special that would be required maybe in the connection string for the app to be able to authenticate with SQL?
Any help would be appreciated.
November 2, 2016 at 7:43 pm
When you connected to your instance over the VPN with SSMS, did you ensure you are also using Named Pipes for communication, and not TCP/IP, so you're attempting the same thing the application is? Can the application be changed to use TCP/IP? Named Pipes communications aren't routable, which would explain the behavior you're seeing: app works fine on local network, can't connect through remote network.
Eddie Wuerch
MCM: SQL
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply