SQL Server 2014 not accessible from network - sql-server-2014

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.

Related

Web server conncetion status

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.

Deploy SSRS report to remote server over VPN from different domains

After connecting to the VPN, in Visual Studio on my local machine, I set the target server to
http://[RemoteServer]/ReportServer
but I get the error
"The specified report server URL could not be found"
I can RDP to the remote server, but my login is DOMAIN-B\MyUser. On my local machine, my login is DOMAIN-A\MyUser.
On RDP, I am able to verify that Reporting Services are running and the target URL is correct.
How can I deploy an SSRS project from Visual Studio on my local machine to a remote server, on a different domain, over a VPN connection?
More broadly, how does Reporting Services authenticate report deployments? I would imagine Visual Studio would require some credentials when trying to deploy to the Target Server, just like when you connect to a database in SQL Server, but I am never prompted on my local machine, and I don't know how to set that up on the remote server.
Try:
http://[RemoteServer].[Domain].local/ReportServer

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.

SSIS 2005 running in SQL Server Agent on local PC connecting to database on remote server produces error

I'm trying to run an SSIS 2005 package from a SQL Server Agent job on my local PC. This package is attempting to connect to a SQL Server 2005 database on a remote server, but it gets the error message, Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. What is the problem and how can I solve it?
you can create a SQL job to run the start_execution command and then the process will run under the user running the job.
the approach is explained here.
The problem is that the SSIS package is being executed under the NT credentials of the account running the SQL Server Agent service (likely to be either your local PC's "local system" or "network service" account), and is attempting to connect to the remote SQL instance with windows integrated security. This fails because the remote SQL server cannot authenticate the service account as permitted to connect.
When you developed it, the package was connecting to the remote SQL server using your NT credentials (a domain account which the remote SQL server could authenticate).
The quickest fix will be to change the service account under which your SQL Server Agent service runs to a domain account with rights to connect to the remote SQL server. To prove that this is the issue you could use your own domain account for this, although this isn't really a long term solution.
Another thing to consider if above fails is "hop count". If I try to run a SP from a local machine that is connected to remote DB that is trying to connect to another remote DB. I will get the error above. However, if I remote connect to the primary server first, then run the SP with the remote connection, it works fine.