I have a SQL Server version 12.0 instance installed on a Windows Server 2012R2 (SERVER/SQL), and a SQL Server Express version 11.0 instance installed on a windows 10 workstation (WIN10/SQLEXPRESS). Both are on the same domain. I am logged in as the domain admin and have full rights on both SQL instances.
On my WIN10 machine I am able to create a linked server from (WIN10/SQLEXPRESS) to (SERVER/SQL).
On my SERVER when I attempt to create a linked server from (SERVER/SQL) to (WIN10/SQLEXPRESS) I am told to ensure that the instance will allow for remote connections. I have gone through about 40 hours of troubleshooting this, ensuring that all firewalls, ports, security and agents and browsers are open.
Is there any reason I cannot link a SQL Server Express to another SQL Server, but can the other way around?
I would like to be able to call stored procedures from my main SQL Server but am not able to.
Please note, the purpose for the SQLEXPRESS on the WIN10 machine is due to the vendor requirements for the software I am using. Otherwise I would have the instance on my SERVER.
Almost certianly a network issue.
Using SQL Server Configuration Manager configure SQLEXPRESS to enable TCP/IP and listen on a fixed port, preferably 1433 if no other instance is on the server. Restart the instance.
Create a Windows Firewall rule enable inbound TCP/IP connections to the port.
Test network connectivity to the target port from the other server with powershell, eg:
PS C:\> test-netconnection WIN10 -Port 1433
Test SQL connectivity with SQLCMD or SSMS on the server to the WIN10 box.
Create the linked server.
Related
I have installed MSSQL Express 2012 on Windows Server 2012 R2, I have set up database and logins. Everything works fine while I'm logged in at the server, but once I want to login from another machine I got the message:
"login failed for user sa".
Settings that I have made:
Added permission for port 1433 in Firewall,
Named Pipes,
TCP/IP,
VIA are enabled from Sql Server Configuration Manager.
Also for TCP/IP I have set IPALL - TCP Dynamic Ports (blank) and TCP Port 1433. ( These settings are used on other versions of windows that are working, but cant get it on Windows Server 2012 R2 when I want to connect from another machine ).
Thank you Larnu - I have just checked the instance name and it was another instace, because also on that machine was installed and older version and I was doing settings on that older version using that older Sql Server Configuration Manager.
I am an employee of an organisation which uses Remote Desktop Computers. We log in from personal devices with Windows Remote Desktop to an IP/port combo, say 12.23.1.234:5431.
Once in I have servers accessible on the root path e.g. SVR1
Our main software uses a SQL Server instance on SVR1 e.g. Database_01. I can see this on the software loading screen and switch between SVR1\Database_01 and SVR1\Database_02 etc.
How can I identify the server name/address to connect MS Powerpivot to this server directly from my personal machine?
For this you have static ip address provided by your isp provider or your machine should have connected to your VPN and if you have one of them then you can access database by enabling tcp/ip in sql server in host machine
for this open SQL Server management configuration
in configuration tab go to
SQL Native Client *.0 Configuration =>Client Protocol
then Right Click on TCP/IP in right panel and make it enable
after that you can able to access sql server remotely by using ip address in server name
Follow the below mentioned steps to connect to SQL server remotely on a remote desktop:
Configure SQL Server machine
Windows Firewall ->Advanced Settings->Inbound Rules.
Run SSMS (SQL Server Management Studio) on SQL Server machine.
Server Properties - > Connections -> Allow Remote Connections ..”
Add a SQL login (if not already there)
Enable SQL Service to listen on TCP/IP.
Restart SQL Server Service.
Using SQL Server 2008 R2
I have 2 SQL Server instances on my PC, SQL1 and SQL2.
I have Windows XP installed in a VirtualBox. In XP, I have an application which can connect to SQL Servers.
When I try to connect to SQL1, everything is fine, but when I try to do that with SQL2 it errors out with
Could not open a connection to SQL Server
So I started checking the settings. I can connect to SQL2 using SQL Server Management Studio (on a local PC), so I checked that 'Allow remote connections to this server' was enabled. Also, in SQL Server configuration tool I enabled all protocols for this instance, just as it is for the SQL1. SQL Server browser is working.
Configuration of both instances seem to be identical. There is only one difference between SQL1 and SQL2 that I have noticed.
SQL1 version is 10.50.4000
SQL2 version is 10.50.1600
What can cause one of the instances to be unreachable through the network while the other one can be, and both settings are the same?
It could be firewall settings or network settings. For an instance to be reachable, configure at least the following.
TCP protocol enabled (SQL Server Configuration Manager)
Fixed TCP port (SQL Server Configuration Manager)
Enable SQL Server Browser Service
Open firewall for SQL Browser service (UDP port 1434) if you have a named instance.
Open TCP ports for SQL Server Instances.
See Configure the Windows Firewall to Allow SQL Server Access
I have an SQL Server 2008 hosted on a different computer in a different domain. I am able to ping to this machine using the IP address, but not using the machine name. I have also checked the settings of the sql server instance and it is configured to provide access to remote connections.
(Allow remote connections, tcp/ip enabled)
When I try to find this server using Sql server management studio 2008 or VS 2008, I get the error saying that the server cannot be found.
what could be the reason for this?
Please check SQL Browser service is running.
Please make sure you are providing valid authentication details.
Also make sure that TCP/IP connections are allowed by the SQL Server instance by checking the SQL Server Configuration Manager. If you are using an express version of SQL Server then all remote connections are typically disabled by default.
You need to create a trust relationship between the domains I think, it's been a while since I've done things between domains.
Windows Firewall will block SQL Server connection requests from a client machine by default. These are the steps I normally do to allow SQL Server through Windows Firewall:
Windows Firewall-> Allow app or feature through Windows Firewall-> Change
Settings-> Allow another app-> Browse to SQL Server exe (eg: C:\Program
Files (x86)\Microsoft SQL
Server\MSSQL10.SQLEXPRESS\MSSQL\Binn\sqlservr.exe)-> Open-> Add.
Windows Firewall-> Allow app or feature through Windows Firewall-> Change
Settings-> Allow another app-> add SQL Brower service by going to
C:\Program Files (x86)\Microsoft SQL Server\90\Shared\sqlbrowser.exe.
SQL Server configuration Manager-> SQL Server Network Configuration->
Protocols for Your_SQL_Instance-> Right click TCP/IP on the right pane
and enable.
The SQL Server instance does not need to be configured to run on 1433 and therefore no need to open the 1433 port through the firewall. SQL Browser will find it for you whichever port it is running on.
Hi i want to know how to enable remote server connection in sql server 2000. I have sql server 2000 installed in a system with windows server 2003 os. i want to create a dsn connection to the database through remote. I have created a dsn locally in the server it is working. but how to create dsn from the remote system and make it work.
To allow remote connections to the server, do the following:
In SQL Server Enterprise Manager, right-click the server and choose Properties.
On the General tab, click the Network Configuration button and enable Named Pipes, and TCP/IP in the new window. I'm not sure if you need to restart SQL Server after doing this.
After doing this, you should be able to connect to the SQL Server from a remote computer, by referring to e.g. MYSERVER\MyInstanceName.
It helped me.
BTW I've also added sqlservr.exe to my firewall exception list:
http://support.microsoft.com/kb/841251
Try installing MSDE/connectivity tools on remote system.