How To Remotely Connect To SQL Express Using SQL Authentification Across A LAN.
Sep 19, 2007
I hope helps some folks. I hope the links come through okay.
Keywords: Help, Network, KB910437, SQL Express, Network, TCP/IP, User,
SQL Server Express Networking
After a long period of trial and error I finally figured out how to connect to SQL Server Express 2005 using SQL Authentication across an XP network. It required several rather involved several steps to do this. I wrote this document just in case I forgot what I did so that I could repair or re-create my network login(s).
I will try to summarize the steps and include some HELP links to the web pages or my local €œSQL Books On Line€? pages that pointed me in the correct directions. The final piece to my puzzle was found here on the MSDN forums. Some links are better than others, while others may appear not to apply, so always check for links at the bottom of pages. Some were the best I could find after the fact, and not my original pages. Others were actually better, and may seem to be redundant. It€™s a work in progress.
I left out many routine or obvious steps like telling you when to click OK. If you need to be told when, you have no business even considering trying this. Good Luck!
PREREQUISITES:
1. You must have an instance of SQL Express installed and running.
2. You must have the SQL Browser service running.
3. You must have SQL Management Studio Express, SMSE, installed on your Server and to be able to log in as an administrator using Windows Authentification. Be familiar with Object Explorer under SMSE.
4. You must have SQL Server Surface Area Configuration properly installed.
5. You must have a functioning LAN, such as a Windows Workgroup.
6. You need a second computer on your LAN running SMSE Tools for testing.
7. You need a strong knowledge of how to use Control Panel.
8. You need to have KB910437 properly installed despite what this might say, although a neat diagnostic command is documented to verify your install.
SUMMARY:
You must enable SQL Networking
You must configure SQL TCP/IP for the server instance.
You must configure the server instance to use UDP Port 1433.
You must enable a UDP port in your Windows Firewall for that server instance.
Test the ability to remote log in using Windows Authentification using SMSE.
You must create a Windows User account for SQL.
You must create a SQL User login Auditing for that Windows User account.
You must grant Permissions to do things for that SQL login.
Now you can try to Log In across a network.
DETAILS:
SQL Networking must be setup by using the SQL Configuration Manager, SCM.
The default installation leaves networking disabled.
Select and use the TCP/IP protocol.
Re-Start the SQL Server service.
Using the SQL Server Surface Area Configuration Manager you must enable TCP/IP.
Select €œServices and Connections€?.
Choose your server instance and then select €œRemote Connections€?.
Choose €œLocal and Remote€?, then €œUsing TCP/IP Only€?.
Re-Start the SQL Server service.
The server needs a means to talk to the outside world. Use SCM.
Setup your IP address by right clicking on the TCP/IP protocol
Choose €œProperties€?.
On the €œProtocol€? tab leave the default settings, (Yes, 30000, Yes, No).
Select the €œIP Address€? tab.
Configure €œIP1€?, (Yes, Yes, enter your IP address, 0, blank).
Configure €œIP All. Leave the default alone.
Enter €œ1433€? on the second line.
Re-Start the SQL Server service.
The server needs to unlock the door to the outside world.
Open Control Panel and select Windows Firewall.
Click the €œExceptions€? tab and click on €œAdd Port€¦€?.
For €œName€?, enter the name of the server instance.
For €œPort Number€?, the same port as Step 3, 1433.
Test to see if Windows log in works before enabling SQL Authentification.
Using the SMSE, select the €œConnect€? icon in Object Explorer.
Accept all defaults and see if it works.
The server needs Windows user accounts setup.
Set up a generic user account for SQL remote users.
I suggest setting up an account for administrators to use.
I suggest setting up an account for general users to use.
SQL needs to add Windows users to SQL Logins.
Convert a windows user login to a SQL login manually or automatically.
The user needs to be assigned tasks that he is permitted to perform.
Grant the user limited access, or just enough.
Assign generic logins to groups, and then assign permissions to the groups.
Use the pre-defined groups. By assigning users to groups.
Test to see if SQL Authentification works locally, then remotely.
Using the SMSE, select the €œConnect€? icon in Object Explorer.
I have SQL Express April CTP (from VS Beta 2) installed on machineA, but I cannot connect to it from machineB using the command "sqlcmd -S machineAsqlexpress -E". This command works just fine from machineA.
I'm using a Windows XP Home laptop to connect to a network of one of my customers. The administrator of the customer has given me a username and password for a VPN connection. I've got the VPN connection working and I can ping the SQL Express server.
This server is using Windows Authentication. For the users of my VB application we have added a group to the Active Directory and added this group as a user to the SQL Express Server. This works and the users can access the database from within the application. The SQL Express Server allows remote connections and the browser service is also running.
I would like to use the SQL management Studio Express on my laptop to access the remote SQL Express server and manage the database files. To do this I first connect to the remote LAN using VPN and add the address of the SQL EXpress server in the field 'Server name' of the 'Connect to server' screen. The authentication field is set to Windows Authentication. However the username is greyed out and states the login for the SQL Express server on my laptop: laptopusername. How can I correct this?
I don't know whether the username of the VPN connection is in the Active Directory. Should this be the case and should this user also be added to the login/user of the SQL Express server? And how do I get the Management Studio to connect to the remote server? Could XP Home be the bottleneck as it cannot logon to a domain?
im using sql server 2005 express for my vb.net projects but i can't connect to it using SQL Server Management Studio Express or through my vb.net code. I got a error message: An error has occourred while estabishing 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. I already enabled remote connections as suggested by this site http://www.programmingado.net/a-395/SQL-Server-2005-Express-and-remote-connection.aspx. Made sure that SQL Server and SQL Browser services are running. But I still cant connect.
I've just bought a Virtual Private Server Account because I want to host a number of different ASP.NET sites, each backed by their own SQL database. I've downloaded SQLEXPRE.EXE and SQLServer2005_SSMEE-x64.msi to the server and installed the database engine and Management Studio Express on the VPS. My problem is that I cannot access the SQLEXPRESS on my server from my local machine. The Management Studio Express cannot get logged in. I've used "Surface Area Configuration Manager" to allow "Local and remote connections" using TCP/IP only. I've used SQL Server Configuration Manager" to enable the TCP/IP protocol. After making these changes I've stopped and started the SQL server - and even rebooted the machine. I've created a login "Remote User" for this access. I've added sqlservr.exe as an exception to the firewall. What else do I need to do? Is there a simpleton's guide to completing this task?
I have read all of the posts regarding this subject as well as 3"Dummies" guides and I keep having the same problems. I have a verysimple multi-user application that has to hit a database. Wecuerrently have this system deployed and it is working fine on adomain based network. We are scaling back and the network we will beusing is now a workgroup not a domain.It should be simple. I have XP boxes (clients) trying to hit the SQLServer Express database on a Windows Server 2003 machine. It is aclosed network so security is not an issue. I am trying to make thisthing wide open. All I want is for the user to be logged in on hisclient machine, run the application, and access/update the databasewithout having to re-authenticate to the SQL server. I want windowsto handle all of the authentication between the XP machines and theServer 2003 machine.Any suggestions would be greatly appreciated.
Hi all, I'm having a little trouble connecting to a SQLExpress instance on a remote domain using SQL Server Management Studio Express.I've read that by default the program is set up locally only, so have edited the Surface Area Configuration. It only gives me the option to edit 'Services and Connections' on the localhost, but have edited the Remote Connections to use TCP/IP and Named Pipes. In the Management Studio, I enter the server name, and login credentials. On the Connection Properties tab I changed the network protocol to TCP/IP though everytime I attempt to connect I get the following error message: Any help would be greatly appreciated. Rich
Problem: I upgraded a SQL Server Express instance to SQL Server Enterprise, but I'm unable to connect to the SQL server from any remote machine. Only local connections work -- and I've verified that Remote Connections are allowed in the SQL Surface Confg. utility.
Scenario: Server1 has an SQL Enterprise edition installed as a default installation. SharePoint Server 2007 was installed later, and during that install a SQL Express edition instance was installed which is part of the standard SharePoint install. That Express instance contains all the SharePoint content databases.
So Server1 has SQL instances: Server1 <default install running Enterprise> Server1OFFICESERVER <previously running SQL Express, now upgraded to Enterprise>
After upgrading Server1OFFICESERVER to Enterprise, everything seemed to work fine (i.e. SharePoint works fine). However when I try to connect remotely to Server1OFFICESERVER I can't. I've verified through the SQL Surface configuration tool that remote connections are allowed. I've rebooted the server as well. I've tried connecting remotely using various PCs and various applications (e.g. SQL Server Mgmt Studio, Visual Studio, etc.).
If I have SQL 2005 Standard installed on a server and I log on locally to that server. Can I connect to other machines through Management Studio-->Object Explorer that have SQLCE installed and manage the CE DB?
I think you can only connect to either local .sdf files or ones located on a device attached by USB to the local machine, but I have had some difficulty finding a definitive statement on that.
Hi I just installed MSDE over my Windows 2003 box and facing an small problem. I installed it with SQL security mode and also set a password for user "sa". Everything looks just fine using "osql" as it uses local address. But I can't connect to my server from another computer using VS.NET Server Explorer. It seems as MSDE is set to reject connections from outside by default. My question is how to enable it so I can connect using my "sa" account. Appreciate your help in advance.
I just reinstalled SQL Server and after reattaching my databases, I can't connect remotely. If I use "localhost" in my connection string it works fine, but I can't register my remote Enterprise Manager this way.
I'm trying to connect to my instance of SQL server 2000 remotely. I know how to do this with SQL server 2005. but since i do not have SQL server 2000 installed on my local machine.. (xp box) I would love to know how i can connect to my remote server?
Is this at all possible without SQL Server 2000 installed ? i have tried to download the personal edition / developer but I couldnt find it
If anyone knows where i can find the developer edition or if there is a trick to get SQL server 2005 to work with my SQL 2000 server it would be greatly appreciated. thanks
I have both the develper and sql express installed on my laptop computer. I also have Sql Express installed on my desktop computer( Did have develper installed but removed thinking the problem was in the install). I can connect via Management console from my Desktop to laptop with out any problems. I see databases etc. I can not connect from my laptop to desktop. I get a login error. From what I can tell, the servers are configed the same on both machines. I checked Firewall settings on both machines, even turned them both off with no results. Every time I try to connect from laptop I get Log in error, and I get "Failure Audit" eror under component services.
I am at a loss as to what is wrong. I am migrating my Database apps to Sql from Access and need to access remotely and locally, as well as do Replication. Any ideas?
I appologise that incarnations of this topic have been posted several times on this forum, however I cannot find a scenario that is the same as my own so I've resorted to starting a new thread.
I can successfully create and connect remotely to an HTTP EndPoint on my Windows 2003 machine using Integrated security, the administrator username and password via my static IP address.
I have read that Windows XP SP2 supports HTTP EndPoints, and it would be much more convenient for me to be able to create EndPoints in XP, and connect remotely.
I have created the endpoint like so...
CREATE ENDPOINT sql_tvr10 STATE = STARTED AS HTTP( PATH = '/sql/tvr10', AUTHENTICATION = (INTEGRATED), PORTS = (CLEAR))
In visual studio I can retrive a list of services running at http://localhost/sql/tvr10?WSDL absolutely fine. However, in Visual Studio on the remote machine, I cannot connect to http://194.106.11.11/sql/tvr10?WSDL - it prompts me for a username and password, however I cannot select the username - it is set to "Athlon64Guest" (Athlon64 is my server computer name). I have no passwords on any of my windows accounts (except administrator), and I have no database passwords set.
Could someone please tell me how I should go about accessing the HTTP EndPoint?
Just so it is clear, I am running a small LAN with no domain, just a workgroup. I need the client application to be able to connect via http regardless of which network it is on. I am using VS2005 and SQL Server 2005 Dev Ed.
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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
------------------------------ What's blocking my remote connection to SQL 2005 on Windows 2003? I am using Vista Ulttima and the above message comes up after I clicked connect. However I have no problem to connect to same database from same location using XP. Can someone help?
I had a big problem on connecting sqlserver remotely from other machines on the network .....
From any computer in the network i wanna to register the instance of the sqlserver from the enterprise manager ..... the server instance doesn't appear within the available sqlserver list (the servername which equal to my machine is the only one that appear) ..... when i manualy write the servernamealias manually and i choose the connection type and then i write sqlserver username and password and then finish he give a message to me that access denied or sql server doesn't exist ... !!
by the way from the local machine i registered the local instance of sqlserver successfully and successfully i access the Databases .....
To be noted:
I previously uninstalled this alias and i then i reinstalled it again with the same name and i attached the previously exists Databes.
in the same time i installed on the same machine sqlserver 2005 connectivity clients not the server itself.
I am trying to remotely connect to a SQL 2005 Instance on a cluster. I see the following error:
No retry on exception System.Data.SqlClient.SqlException: 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)
I have enabled TCP/IP , Named Pipes on the node. I have turned off IPSec on the clients as well. I am using the following connection string : "Integrated Security=SSPI;server=servernameinstancename;Pooling=false;database=TrialDB"
WSUS is installed on my windows 2003 server. During the install, parameter DISABLENETWORKPROTOCOLS was not specified, and so no remote connection was possible.
I used SVRNETCN.exe to enable TCP/IP remote connection on port 1433. However it seems not to work.
FROM THE SERVER :
osql -E -S MYSERVERWSUS works fine but
osql -E -S 127.0.0.1WSUS doesn't work, i get the famous error
I have to deal with a private network of laptops which are all equiped with preinstalled "Windows XP home"
I've installed SQLExpress on one of these, but I cannot connect on it from the rest of the laptops. (I've successfuly done this with "Windows XP profesional" though, and local connections work fine as well).
I've already setup the SQLExpress to accept conections throuigh TCP/IP but I can not think of something else. (Security comes to mind, but I do not know how to resolve it on "Windows XP Home").
All, My ISP does not allow me to remotely connect to my hosted SQL Server DB--how can I use SQLDataSource and other data bound controls in development? Here are my specs: IDE: Visual Web Developer Express 2005 Database: MS SQL Server ASP Version: ASP.NET 2.0 The SQL Server is hosted centrally at the ISP; basically I have been given the connection string parameters. My question is this: Do I use two web.config files (one for when I develop locally and one for when I deploy remotely)? If so, how? Will the SQLDataSource control find the connection string defined in web.config on the remote server? I don't want to have to write all of the database code and it would be a big loss of one of the major benefits of using ASP.NET 2.0 if I do. Any help will be greatly appreciated, Leslie
Someone please help me before I loose all of my hair :mad: !!!
I have two machines, a Windows Server 2003 machine running an SQL Server Standard Edition database instance and client tools (Enterprize Manager etc.), and a workstation PC running Windows XP SP2 which has just the SQL Server client tools (not an actual DB instance).
I'm trying to use the Enterprize Manager client tool on my WinXP machine to remotely connect to the server instance on the server PC (via 'New SQL Server Registration' option). Everytime I do this I get the following error message:
Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server Connection.
Now I've tried using different usernames and passwords. I have login details for my SQL Server set to use Windows Login rather then SQL Server login, so I tried remotely connecting with the username and password for the server PC, tried 'sa' with server password, even tried setting up a new user on the server and logging in from the client with that, no luck. I've opened up correct ports 1433 on both PCs, even disabled the windows firewalls algother. Both server and client have SP3a installed, WinServer2003 has SP1 and XP SP2.
So I'm at a loss to how to remotely connect to my SQL Server. FYI I know the server itself is working fine because I can connect to it using Enterprize Manager/Query Analyser on the local machine. Any ideas? Many thanks for your help!
I have an SQL Server 2012 with SSIS installed on Windows Server 2008 R2 Core. I'd like to connect remotley to SSIS but I receive the following error. 'The RPC server is unavailable.'
I am having trouble getting SQL Express 2005 on Windows Server 2003 working remotely. I have set it up for TCP connections and all, and I can connect to the server fine, but I am unable to login. How do I go about creating accounts for the db that will allow me to access it remotely?
I'm new to MSSQL. At my work place, I'm using MSSQL and using SQL Query Analyzer to run queries and view all my database tables and structures.
Now, I can work remotely at home for the time being. So, how do I get SQL Query Analyzer and be able to connect remotely to my database at work?
I've downloaded SQL Server 2005 Express and it comes with SQL Server Management Studio, which looks similar to SQL Query Analyzer. The problem is though, how would I remotely connect to my database server at work? Is it possible to do this using SQL Server 2005 express?
One thing I was advised to do was configure the TCP/IP Port number from 1433 to 1435. However, I do not see an option to configure that nor do not know how to connect remotely (I do have the IP, User, and Pass).
I have checked the connection string passsword etc, and all are correct.
I have tried SQL Server Management Studio, aspnet_regsql.exe etc and all give 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: TCP Provider, error: 0 - No such host is known.)or
System.Web.HttpException: Unable to connect to SQL Server database. ---> System.Data.SqlClient.SqlException: 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: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)
I have used the surface config to enable TCP/IP and named pipes.
Since today (after installing the latest Windows Updates !on my local machine!) I cannot login to a SQLExpress instance remotely; stating that it cannot find the server/instance.
The weird thing is: it only happens when I want to login to the non-default instance (sqlexpress 2005) (<IP><instance>).
When i'm using the default instance (msde 2000 or sqlexpress 2005 on another machine) (<IP>) it seems to work fine.
Does this have something to do with the windows updates, or is it just a coincedence?
I've been trying to configure remote connections to my sql server express to no avail.
First here are some constants to clear some things up: - OS: Windows XP Pro - SQL Express version: April CTP release - Windows Firewall: disabled (to avoid any problems there) - Network type: two computers connected a router. - Router firewall: Enabled (I may be wrong but the router firewall only blocks external traffic, so I left it on.)
First, I configured my SQL server to allow remote connections in the SQL Surface Area Configuration. (Set it to both TCP/IP and named pipes)
Second, I enabled and configured sql server browser.
Third, I enabled TCP/IP and named pipes in the 'Protocols for SQL Express' option of the SQL Server Configuration Manager.
According to http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx I have done everything I need to (including edit the registry to enable the SQL Server Browser service) and the error I continue to get is:
"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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)"
So I tinkered and had no success in messing with anything that would fix it. Although, ***when I browsed for network servers on different machine, the server instance DID show up in the list***. So I find it odd that it can find the instance when browsing, but fails to 'find' it when making a connection.
So I didn't stop there, I decided to try the non-sql server browser method of remotely connecting: specifying the IP.
I went back to the blog of instructions referenced above and re-did the steps, this time specifying a TCP Port for the server instance and then after specifying the port on the remote computer connection string, and attempting to connect, I get this 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: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)"
I've done all I know how, read all the possible blogs I can, and nothing's come up. If anyone can shed some light on me, I'd pay you 1 billion pretend dollars. Any help would be appreciated. Thank you!
I am tring to access the SQL 2005 Express which installed in remote machine. Front end app is on Visual Studio 2005. Try to connect SQL Express using the application Layer which is installed on the computer where SQL Express is installed. Could not fetch data from the SQL Express. What could be the problem?
i have a Vb application on an client pc that has to connect with a sql databse file on the server. the connection string is : connectionString="Data Source=<servername>SQLEXPRESS,1433;Initial Catalog=TBSD.mdf; User Id=sa;Password=sa;integrated security=false;" /> </connectionStrings>
if i run the application i get the error message : "login failed for user 'sa'.
If i try to connect remotely to sql server express with sql server managment studio express i can connect without any problems.
I'm just wondering if there is documentation anywhere to help me with installation of SQL 2005 Express on a remote computer. I've set up IIS 6.0 and Windows Server 2003 Web Edition on another computer and am planning to use that for a development server.
Currently I've already installed VWD Express (local computer) and SQL 2005 Express, as well as SQL Query Manager (remote computer). But I seem to be having problems with VWD being able to create databases when i edit the code remotely.
For example when I right-click on "Data Connections" in the "Database Explorer" to create a new database it won't let me. The only way I can do this is to add a connection to a database which I have previously created. And even then there are still problems.
If I set up the database by adding a connection I cannot seem to create stored procedures. The error message I keep getting is "This feature is not supported in Visual Developer".
Is this due to wrong settings whilst installing SQL Express? Or am I just not configuring it right?
Any help on this issue would be greatly appreciated.
I have successfully created an Exchange 2000 linked server in Microsoft SQL server 2k. When I use my NT login, I can query it.
I'm now developping a website (ASP.NET in IIS 5). I have successfully created a web page querying my database. But now, I would like to query my linked server via my SQL server. I have try various authentification settings but I always got this error : OLE DB provider 'Exoledb.DataSource.1' reported an error. Authentication failed.
I know it is because the IIS process don't have any rights on the Exchange server but I would like to know what is the way to get around this without given rights to the IIS process (and creating huge security holes).
I have SQL Server 2005 Express installed on a windows server 2003 standard edition. I have configured the windows firewall to allow exceptions for sqlservr.exe and sqlbrowser.exe. I have enabled remote and local connections using tcp/ip & Named Pipes through the Sql Server Surface Area Connection utility. I am able to telnet into the server with: telnet <server ip> <1433>.
Here is the strange part: I am able to connect to the Sql Server remotely from a development machine via Sql Server Management Studio Express, but I am unable to connect to the Sql Server from the same development machine by registering it in Sql Server Enterprise Manager...Is it possible to register SQL Express through Enterprise Manager?
When registering the SQL Express DB in Enterprise Manager I tried both just the (IP Address) of the server and the (IP AddressSQLExpress) as the server/host but I am getting the following errors from enterprise manager:
Just the (IP Address) as the server/host: Invalid Connection. ConnectionOpen( Invalid Instance())
(IP AddressSQLEXPRESS) as the server/host: Sql Server does not exist or access denied. ConnectOpen(Connect()).
Any idea why I can€™t register/mount the instance remotely in Enterprise Manager but I can in Sql Server Management Studio Express?
Hi, I hope you can help.I have configured a Windows 2003 web server and SQL 2005 Server (on same box) to successfully allow remote connections and to allow access via SQL Server Management Studio Express 2005.The problem I have is that I want to restrict access to the databases on the server via the Management Studio to specific databases e.g. 1 database user "sees" only 1 database.I can configure it so that the user's remote access permissions do not allow access to other databases but they can still "see" the database listed in the Management Studio explorer.I can also configure it so that the users cannot see all the databases (by disabling View All Databases on SQL Server), but this means that they cannot not see their own database which they have permissions for.Is it impossible to have the desired behaviour of only displaying the database which the remote user accessing has permissions for and hiding all other databases?I have MSN'd,Googled and Yahoo'd this one to no avail :(Many thanksFergus
