I Am getting the infamous error 26 connecting to named instance sql server from network share when trying to connect and the application is started from a network share. If started from a local hard drive, it works fine. I know it is related to my privileges on the network, as I am working as an external consultant, with limited privileges, and if somebody who is not external tries, he can connect fine both from local hard drive and network share using my computer, so .net trust is set up and is working properly.
To summarize:
If I start the application from a local hard drive, everything works fine.
If I start the application from the network share, connect gives the following error:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
and Ping gives "No such Host is known"
and DNS gives "No such Host is known"
I an internal employee starts the application from my machine, everything works fine.
We cannot see any differences in privileges for the internal user and my user. What kind of privileges could be causing this behaviour?
To summarize:
If I start the application from a local hard drive, everything works fine.
If I start the application from the network share, connect gives the following error:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
and Ping gives "No such Host is known"
and DNS gives "No such Host is known"
I an internal employee starts the application from my machine, everything works fine.
We cannot see any differences in privileges for the internal user and my user. What kind of privileges could be causing this behaviour?