I have a website that runs on Microsoft server (I have a remote desktop connection) with the SQL database. I want to enable remote access to the SQL database, without restarting the service. Is that possible?
Related
I am testing a SQL Server for my company as an on-site database for manufacturing data and records. I have the SQL Server on my laptop and have set up permissions and downloaded SQL Server Management Studio on other computers in the company and managed to connect via SQL Server authentication.
However, I can't get Windows Authentication to work. I also have a Visual Basic program that I can run on my laptop that will communicate with the SQL Server that is locally on my machine but that program will not work on other computers in the company because they can not connect to the SQL Server.
How do I set up SQL Server to allow for Windows authentication on any company computers running that program? I opened a port on my Windows firewall on the computer that has SQL Server installed, and it seems to work with SQL Server authentication.
The connection string I am using in my Visual Basic program is as follows:
Dim connstring As String = "Data Source = Server; integrated security = true"
I assume I need to change something in my logins folder in my SQL Server?
My desired result would be for any computer running this application to be allowed to communicate with SQL Server and be able to read and write data.
any computer running this application to be allowed to communicate with SQL Server
The normal configuration to enable this is:
1) The SQL Server must be running on a server joined to the domain.
2) The SQL Server is configured to use TCP/IP and listen on port 1433.
3) The other computers are also joined to the domain.
4) The users logged in on the other computers are added as Windows logins. in SQL Server, and mapped to users in the desired databases (can use groups instead of individual users).
See eg: How to add Active Directory user group as login in SQL Server
I have deployed one vb.net desktop application and sql server is used for backend. It is properly working on local machine but when accessing database from remote machine it giving the error in the title.
I have done these things already:
Started SQL server, sql browser service using sql server configuration manager.
added the sql server, browser exe in to firewall allowed program list.
restarted sql server and browser.
enabled TCP/IP, Shared memory, Named pipes in SQL server configuration manager
enabled the remote connection for this DB in database property
Windows application is set to connect to the SQL Server using SQL Server authentication.
When I RDP to the box where the application resides and start the application, it successfully connects to the SQL Server.
When a customer runs the application on his desktop (he is on the network with the application box) and starts the application, connection fails (error. Server does not exist or access denied).
The customer can ping the SQL Server IP in his command prompt.
Yet, when I look at the error log on the SQL server I don't see the logs of his failure to connect.
What could be blocking his access to the SQL Server?
You may have to enable the TCP/IP protocol in SQL Server Configuration Manager - it's disabled by default.
I have installed SQL Server 2008 R2 Express on a Windows Server 2008 R2 machine, and now when I want to open that database using SQL Server Management Studio on the client machine it fails to open.
But the database opens normally on the server.
The owner of the database is sa and on client I am logged in with windows authentication.
How to resolve this error??
the server priciple smtech/prabhu is not able to access the database
the user is of client under the server domain
I suggest making sure that the account you are trying to connect with actually has access.
Log onto the server, open up management studio, look in object explorer. There should be a Security folder icon in the treeview, Expand that and the Logins folder.
If the user you are trying to connect with isnt present you may need to add it.
Other than this instead of connecting with windows authentication maybe try connect with SQL Server Authentication as the SA user?
Is both Client and DB sever are on SAME domain ?? If not, then I think Windows Authentication will not work for you.
(As already suggested in above answer) create a SQL Login try with to connect DB from Client using that Login.
If both machine are on same domain and still you are not able to connect server, then few things you can check,
Can your client actually "see" this server over network ??
Most common reason is firewall. By default SQL Server communicates from port 1433 and 1434. Try to see if this MSDN link helps
Make sure that your SQL Server instance is configured to communicate using TCP/IP. This can be configured from SQL Server Configuration Manager.
i am connecting to sql server 2000 on a remote computer with a dotnet application, but when i try to open the connection it gives the following error:
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
What is this?
It means that the remote SQL server is configured to not allow remote connections.
From this forum discussion:
Make sure SQL SERVER is up and the instance you try to connect is running.
Your system Firewall should not block SQL Server port.
Go to Computer Management >> Service and Application >> SQL Server 2005 Configuration >> Network Configuration Enable TCP/IP protocol. Make sure that SQL SERVER port is by Default 1433.
Now follow this KB Article of MSDN depending on your server.
Are you sure you're connecting to a sql server 2000 instance?
Possibly it's been upgraded to 2005?
Try following the procedure here: http://support.microsoft.com/kb/914277 to allow remote connections.
By default, as a security feature, SQL Server 2005 does not enable connections from other machines on the network.
Verify that your SQL Server and its databases are suitably secured (for example, have proper user accounts and passwords, etc.). Once you are satisfied, go to Start, Program Files, Microsoft SQL Server 2005, Configuration Tools, SQL Server Surface Area Configuration. Look for Database Engine, Remote Connections and change the setting to allow remote connections.