Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

SQL2008 R2 on Windows 2008 R2 firewall Question

Posted on 2013-01-16
2
Medium Priority
?
239 Views
Last Modified: 2013-02-04
I have just finished installing a SQL 2008 r2 cluster, no errors all looks well

but when i try and start the SQL managemnt studio (on one of the nodes)

it errors saying
A network related or instance-specific error occurred while establishing a connection to SQL server.
The server was not found or was not accessible. Verify the instance name is correct…..
Error: 26 – Error Locating Server/Instance specified (Microsoft SQL Server)

when i start SQL Managent studio if i add, 1433 to the server name it works.

I dont have to do this on othe rsql clusters in diffrent domains, what have i missed?

config manager shows 1433 as default for the Instance im using

Windows firewall was turned off, tried turning it on and adding  135,1433,1434,2383,4022
0
Comment
Question by:mhamer
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 23

Accepted Solution

by:
Ayman Bakr earned 1200 total points
ID: 38781921
0
 
LVL 28

Assisted Solution

by:Ryan McCauley
Ryan McCauley earned 800 total points
ID: 38802627
SQL instances on a cluster require you to specify the instance name, even though it's listening on port 1433 (unless you installed the default instance on your cluster, that is). However, when you specify the instance name, SSMS actually connects to the name/ip you've provided on UDP port 1434 and talks to a service called the SQL Browser - it uses this service to get the port information for the instance you're asking about. That's where it gets tricky - if the port your instance is running on is dynamic, your firewall is going to have trouble because it could change any time you start up SQL Server.

You can obviously work around it by specifying the explicit port, as you've done above (give ",1433" after your instance name) - that's the easiest way around it, since that's working now.
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Did you know SD-WANs can improve network connectivity? Check out this webinar to learn how an SD-WAN simplified, one-click tool can help you migrate and manage data in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Mailbox Overload?
If you troubleshoot Outlook for clients, you may want to know a bit more about the OST file before doing your next job. IMAP can cause a lot of drama if removed in the accounts without backing up.
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This tutorial will walk an individual through the steps necessary to install and configure the Windows Server Backup Utility. Directly connect an external storage device such as a USB drive, or CD\DVD burner: If the device is a USB drive, ensure i…

721 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question