Web server conncetion status - mysql

I am new to Windows server and SQL servers.
I have this situation I have two virtual servers one for IIS and one for SQL. I want to connect my IIS site to my SQL server who is on the different virtual server. I have set connectionString with my own SQL server parameters. But it seems like something is wrong it won't connect.
I can connect to SQL server with SSMS and everything works well.
Is there any way to see why web server (IIS site) can't connect to SQL server. Any logs maybe on the web server? For example, wrong address, don't have permission.

Related

SQL Server 2014 not accessible from network

I have setup a SQL Server 2014 instance on my local drive/computer and everything is working fine. I can login and access the data inside. I have the role admin on both the SQL server and my local computer. The computer is in an AD of a network. However, if I go to a different computer in the network, (I can ping to and from machine in the network no problem) and attempt to login my SQL server 2014 under the same credentials using Windows Authentication, I got the error below:
I have checked the configuration on my local machine where the SQL server 2014 resides and have all protocol enabled.
I also have SQL Server service set to automatic:
What else do I need to look into to make sure my SQL Server can be accessible from the network? My local computer OS is Windows 8.1.
Please help as the SQL Server is pretty useless if only my local machine can access the data in the SQL Server.

how to connect sql server over the internet

I am using Windows server 2012 r2. I have installed sql server 2008 r2 on that server. I am trying to access that sql database form my PC. Using Ip address of the server and port no 1433 to access but it is showing me network related instance specific error.
I am also trying to login on server in sql server 2008 database using Ip address of server and default port no example: 192.160.45.345,1433 but I am not able to login. It is also showing me network related instance specific errorenter image description here. Please suggest me any solution
Thank you in advance...
As it said in the error message, the SQL Server might haven't been configured to allow remote connections, that's the reason you cannot connect to it over the internet.
Try this link: https://msdn.microsoft.com/en-us/library/ms191464(v=sql.110).aspx

Connecting SQL Server through Network

I have developed an App using Delphi Xe3 and SQL Server 2008. Now the app is finished and compiled. I would like to run the app on another machine that is connected to the main Machine(running SQL Server) via Wifi. However when I run the app on another machine, I get the error " Server does not exist or access denied". I have enabled the SQL server for remote access enabled TCP/IP. Someone told me I would have to be running SQL server client on the other machine to access the server database. what am I missing to be able to run my app on machine B to share the database running on machine A.
I think sql server has remote connections off by default.
Run SQL Server management studio.
Right click on the server.
Properties
Connections
Under "Remote server connections", check on "Allow remote connections to this server"
For a default SQL instance don't add the name of the instance in the connection string Data Source. It somehow works when you test the connection from udl but does not work when you use the instance name in the Delphi app.

sql server express 2008 r2 and VS2012, untrusted domain

I have a windows XP Pro in a vritual machine with SQL Server 2008 R2 and other computer in the same LAN and same workgroup with VS2012.
When I try to create a new connection in VS2012, I can see the server name, but when I trey to see the databases, I get an error that I am trying to connect from an untrusted domain.
I would like to know if it is possible to create a domain in windows XP Pro and add my two computers to the same domain.
By the moment, SQL Server are cofingurated only to use windows authentication, but no SQL Server authentication, because I would like to avoid to put user and password in my connection string of my app config file.
thanks.
You need a domain controller to make a domain, so just having XP Pro won't do it I'm afraid.
However, if you have a Windows account with identical usernames & passwords on both machines then it should still "just work". You can't put a Windows username/password in a SQL connection string - you'll need to run your code as that user. That can be done by starting your application using RunAs (shift+right-click on shortcut and choose "Run as...", or use RunAs at the command prompt).
This is pretty brittle but so long as you make sure the passwords are kept in sync then you should be ok.

How To Secure SQL Server Database On Client Machine?

I Just Completed My Window Application,In Which I Use SQL Server 2008 as Back-End.
I Install My App With Database In Client Machine.
But Problem Is That My Client Can Also See My Database Using Sql Server Mangement Studio.
I Want to Prevent Client To See Database.
How can i do this?
That's the entire purpose of a database server. For any authenticated client to be able to connect to the server. That client may be your application or any other application - Management Studio being one of them.
You can either host your database server anywhere else and set up SQL server to only accept connections from your web application's server. But anyone that knows the IP, instance, and has the proper credentials can connect anyway from that server.
Or you can set up a user on SQL server for your application and configure your application to use that user. Now only the database administrator and that user can access that database.
But anyone that browses your application's configuration files will be able to pull the credentials anyway from there. Unless you are using integrated security, in which case the user your application runs under will be the only one to have access - assuming you grant that Windows user access to the database of course.
I guess the real question is, why are you trying to prevent someone from directly accessing the database?