Connecting remotely through VPN

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Greetings,

One of my customers has an SBS2003 SP2 box running SQL Express 2005. It is
set for mixed mode authentication and I have a SQL account setup (not SA) for
connecting via SQL authentication.

When I connect to the LAN locally (inside the building) I can connect just
fine to this instance using SQL authentication. I do not go through Windows
authentication when I am there, but DHCP provides me with an IP address. I
log onto resources (drive mapping, etc.) as needed.

When I am at my own office and connect through the VPN, everything works
just like it does when I am at the client site except that I cannot connect
to the SQL server.

The SQL Browser service is running, TCP/IP and named pipes are enabled and
when I ping the server name, it returns the correct IP address. Remote
connections are enabled. Following is the error message I receive when
attempting to connect via VPN.

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) (.Net SqlClient Data Provider).

I am using SQL Server Management studio on a Windows Vista machine. I have
tried both TCP/IP and named pipes configuration on my client and both give me
the aforementioned error.

Thank you for your assistance.

Dale Hoffman
.

Relevant Pages

  • Re: crash on virtual dimensions
    ... SQL authentication doesn't work for SQL Server to anywhere. ... It is basically a way for access developers to start writing all of their ...
    (microsoft.public.sqlserver.olap)
  • Re: Cannot connect a remote sql server
    ... Try disabling the firewall on the client. ... I would also make sure the SQL Browser service is running and that the login credentials you're using have rights to the default database. ... I've also written a long chapter on connecting that has helped a lot of people establish and maintain connections. ... I don't know if this matter but the server I'm trying to connect to is SQL Server 2000. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
  • RE: Website Administration has errors
    ... The application is configured to use SQL Server ... permission issue when the webadmin site page try connecting to the target ... since the web admin site will use the ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • SQL Express Remote Connections
    ... TCP/IP is enabled (because i can get there from the local subnet) and if i go to the properties of the connection and go to IP Addresses they are all active but only the primary host ip is enabled. ... 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. ...
    (microsoft.public.sqlserver.setup)