none
Problems with SQL Server access thru a proxy, but only within a .NET Web Application. RRS feed

  • Question


  • Accessing my SQL Server in a proxy enviorment, I get the following error:

    "An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"


    If i access a local database (on the same computer) with my .NET Web Application, I have no problems.

    Going thru SQL Server Management Studio, I'm able to to access the remote SQL Server thru our ISA proxy with no problem, using the same SQL login.

    What is SQL Server Management Studio doing that I'm not doing in my .NET Web Application?

    I tried the following in the Web.Config file too and without the <defaultProxy> as well.

    <system.net>
        <defaultProxy>
          <proxy usesystemdefault="True" proxyaddress="http://proxyserver:8080" bypassonlocal="True"/>
          <bypasslist>
            <add address="remotesql_name"/>
            <add address="remotesql_ip"/>
            <add address="alias_sqlname"/>
          </bypasslist>
        </defaultProxy>
      </system.net>

    Anyone have any clues?

    Thursday, November 8, 2007 10:27 PM