I'm trying to connect to a SQL 2008 Express instance on Server 2008 but am having problems with Windows Firewall. If the firewall is off, I have no issues.
The error provider is SQL Network Interfaces. I've opened TCP 1433 and UDP 1434 as per many instructions on the ney but to no avail.
Any ideas? Thanks
I think you need to open more ports than just 1433 and 1434. The full list is documented on MSDN. IIS may only need 1433 and 1434 because all it will need is just access to the database engine, but SQL Management studio may need more ports open since it will want to talk to all sorts of other SQL services (e.g. for sql server agent, configuring alerts, logs, settings etc)
Related
Hello my name is Ozan Bayrak
I have SQL on my pc and I have made a C# application.
I published the C# and installed another SQL server into this computer so I have 2 SQL
and now I can't Log in into my SQL cuz I get a error it says like this
"You can't run this Sql on 2005 and 2008"
who can help me please I really need to know this.
Everytime I want to log in it gives me a error.
when I go to services the SQLEXPRESS is offline too.
Thanks for the help
Ozan Bayrak
There's many possible issues here, including all or one of the below
Test Open Port The network on your LAN, can you ping SQL Server remotely on the default port 1433 on the specific IP Address (you can use PuTTY or Telnet to check this)
SQL Configuration Manager Check SQL Configuration Manager and see if the Network Protocol for SQL is enabled for TCP/IP, Named Pipes or Shared Memory
Firewall and Default Port Check the Windows Firewall make sure its allowing 1433. Since you are testing, best thing to do is to disable the Firewall in Windows Services to confirm whether its a firewall issue or not.
SQL Server Browser SQL Server Instances (instances have the form SERVER\SQLEXPRESS or SERVERNAME\SQL1 for example). Check in services and makes sure the "SQL Server Browser" is running. Also, you must allow a Firewall rule for port 1434, which is the default port of the "SQL Server Browser". This is necessary because the SQL Server maps and forwards the traffic based on the Instance Name, so this is the service that resolves the instance name.
SQL Server Instance Port Varies SQL Server Instances does not necessarily run on port 1433, in this case you will have to have the SQL Browser Running which maps the name to the port and directs traffic to the correct instance. In your firewall, instead of allowing port 1433, you will have to allow sqlservr.exe Executeable Program. The port also can be determined by looking at the SQL Server log File in the MSSQL\LOG folder in Program Files. There will be an entry for "Server is listening on port ..."
My recommendation for you is to install SQL Server Express Management Studio (SSMS) which is the GUI interface to manage the SQL Server Express instance. The link is below for both SQL Express and SQL Management Studio. And see if you can connect to the servers that way first. Another suggestion is for you to install both on a Local Computer and simply familarize yourself with SQL Server first before exposing it on the Network.
http://www.microsoft.com/en-us/download/details.aspx?id=29062
Since you have both, its possible that ports are conflicting thereby the SQLEXPRESS instance for MSSQL 2005 isnt starting up. Change the port number with the following steps
In SQL Configuration Manager, in the left side window under SQL Server Network Configuration select Protocols for SQLEXPRESS.
On the right side window, Right Click on TCP/IP and select Properties. In protocol tab, change Enabled to Yes
Under IP Address tab, search among IP1, IP2, IP3 and IP4 which has Enabled as Yes(if neither is enabled, just enabled one)
Which ever has Enabled as Yes, make sure TCP Dynamic Ports is blank and change the TCP port to anything other than 1433.
Also under IPAll, make TCP Dynamic Ports blank and for TCP port enter the same value that you entered above.
Click Apply and close the TCP/IP Properties window.
Now go back to SQL Configuration Manager, under SQL Server Services, right click on SQL Server(SQLEXPRESS) and click Start.
Try the following:
Turn on the SQLEXPRESS service and try to reconnect.
If the above fails, then read this article.
In a nutshell, you will do the following:
Enable remote connections on the instance of SQL Server that you
want to connect to from a remote computer.
Turn on the SQL Server
Browser service.
Configure the firewall to allow network traffic
that is related to SQL Server and to the SQL Server Browser service.
I'm totally stuck I hope someone can help.
I have a fresh copy of SQL Server 2008 Express installed on a Windows 7 pro machine with 2 instances created: Dev and Test.
I can connect to an instance via SQL Server Management Studio (SSMS) from the remote client only when the SQL Server Windows firewall is turned off, client firewall on.
I checked to make sure sql server firewall and client firewall have the same rules.
I've setup rules to allow TCP and UDP on local ports 1433 and 1434, remote ports-any, for inbound and outbound, on server and client pc.
I got so fed up that I enabled and allowed everything that was disabled. But still no worky.
I really have no idea what it could be so any help would be really appreciated.
Many thanks
Ian
Finally found a solution..
1. Open SQL Server Configuration Manager
2. Select SQL Server Network Configuration
3. Select Protocols for [named instance]
4. Select IP Addresses tab
5. For each IP in the list, delete 0 from TCP Dynamic Ports and enter 7201 in TCP Port field below
6. One IP entry will have an IP address for the SQL Server - set this to Enabled and Active
7. Click Ok
8. Repeat steps 3 to 7 for another instance using port 7202
9. Open Firewall from Windows Control Panel
10. Advanced Settings
11. Add Inbound Rules based on Port:
> Name 'My Instance SQL Server', TCP, port 7201
> Name 'My Other Instance SQL Server', TCP, port
> 'Native SQL Server', TCP, port 1433
> 'SQL Server', UDP, port 1434
12. Restart services
13. Ensure SQL Server Browser service is started
I've studied other topics, tried various solutions, but cannot gain access to my SQL Server remotely from my PC.
I have not problems with accessing the Server its running on, I'm able to Remote Desktop fine.
Here are the steps I have taken :-
Enabled Remote access to SQL Server
Created a SQL Authentication User Account (which Ii can log in with whilst on the server).
Enabled Shared Memory & TCP/IP Protocols for the SQL Server Instance.
Created a Firewall Rule for TCP Port 1433
Created a Firewall Rule for UDP Port 1434
Created a Firewall Rule for SQLBrowwer.exe
Created a Firewall Rule for SQLservr.exe
Ensured SQL Browser & SQL Server are running processes.
SQL Management Studio cant even detect the instance of the SQL Server in listed Database Engines.
I'm at a loss as to what the problem could be?
** UPDATE **
Ive tried turning off my Firewall, the SQL Server in now found in SSMS, but i still cant connect to it?
All your steps are right, I'd do the same. I'm sure everything is fine with your SQL Server.
I guess it's firewall, try to turn it off or run this from command prompt:
netsh firewall set portopening protocol = TCP port = 1433 name = SQLPort mode = ENABLE scope = SUBNET profile = CURRENT
Also, check if you have antivirus software or something similar and turn it off (on both sides).
I am trying to debug a stored Procedure from Microsoft SQL Server Management Studio 2008 which is connected to MS SQL Server 2008 Database Instance running on a different system.
System Information:
1. Remote system is running with Symantec End Point Security
I have done the following settings for running the remote debugger:
I have added the inbound Rules for TCP 139, TCP 445, UDP 137 and UDP 138 ports.
My local system's instance is running with sysadmin user role.
I have added the sqlservr.exe and svchost.exe at server windows firewall exception list.
I have added the svchost.exe and ssms.exe at client windows firewall exception list.
The SSMS and SQL server services are running in the same domain.
Following necessary services are running properly
TCP/IP NetBIOS Helper
Remote Registry
RPC Service
But after doing all these specified steps i am getting following error after clicking the debugger button in client SSMS.
Unable to start T-SQL Debugging. Could not attach to SQL Server process on 'remotesystem_name'. Click Help for more information.
If there is another alternative please let make me aware of that.
I solved this problem by creating a new login account (windows authentication account) on server for my machine.
I installed an instance of SQL Server 2008 R2 Express on my 32 bit Windows 7 machine. I can see it and connect to it with SQL Server Management Studio locally but not on the network.
SQL Server Configuration Manager Settings
SQL Server Browser is running (Log on As "NT AUTHORUITY\LocalService")
Named Pipes for this instance are Enabled
TCP/IP Enabled Dynamic ports are set to nothing the TCP Ports are set to 1433
In the Server Properties from SSMS
Connections --> I have the "Allow remote connections to this server" box checked
The Firewall is turned off for testing
When I try to see this instance with a command prompt (sqlcmd -L) from another computer I get a list of network servers. Sometimes it shows up and sometimes it doesn't. If it shows up I still can't seem to connect and the error message number is 26. If feels like there is some switch somewhere that needs to be turned on.
I am leaving this up there for any other users who have mental blocks occasionally... I had not turned off all the firewalls. In windows7 you have three different firewalls and you have to turn off the right one