Cannot connect to second SQL instance

Hello there,

I have SQLServer 2008R2 (PG-REPORT\SQLSERVER2008R2) and SQL Server 2012 (PG-REPORT) on my reporting server and I have SQLServer 2008R2 (PG-KAIZ) on my production server. They are in WORKGROUP setup.
Now I am trying to setup Log shipping between the 2 SQLServer 2008R2. From the production server when I type in cmd SQL CMD -L it shows me the SQL instance in my network,like so

C:\Documents and Settings\Administrator>sqlcmd -L

Servers:
    PG-KAIZ
    PG-REPORT
    PG-REPORT\SQLSERVER2008R2

From my Management studio of production server I can connect to the PG-REPORT instance database but not the PG-REPORT\SQLSERVER2008R2 instance database. What could be the reason.Please help!!

Error I get is

TITLE: Connect to Server
------------------------------

Cannot connect to PG-REPORT\SQLSERVER2008R2.

------------------------------
ADDITIONAL INFORMATION:

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 that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476

------------------------------
BUTTONS:

OK
------------------------------
zolfAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Vitor MontalvãoMSSQL Senior EngineerCommented:
From my Management studio of production server I can connect to the PG-REPORT instance database but not the PG-REPORT\SQLSERVER2008R2 instance database.
What's the error?
This can be for the following reasons:
- PG-REPORT\SQLSERVER2008R2 has the SQL Browser running?
- PG-REPORT\SQLSERVER2008R2 has any firewall rule blocking the SQL Server port?
- PG-REPORT\SQLSERVER2008R2 has the Remote Connection enabled?
- The user you're using has connect permission on PG-REPORT\SQLSERVER2008R2?
zolfAuthor Commented:
I posted the error,please see. By the way, on the firewall I opened TCP 1433 and UDP 1434.
But I can connect from the production server to the reporting server's default instance which is the server 2012 but not the named instance PG-REPORT\SQLSERVER2008R2 whcih happens to be mssql 2008r2
zolfAuthor Commented:
By the way in the Config file I should be seeing both the instance but I see 1 showing. why??

1
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

zolfAuthor Commented:
- PG-REPORT\SQLSERVER2008R2 has any firewall rule blocking the SQL Server port

What port is the second instance using, any idea???

- PG-REPORT\SQLSERVER2008R2 has the Remote Connection enabled?
Where do I check this

- PG-REPORT\SQLSERVER2008R2 has the SQL Browser running?
Where do I check this
Vitor MontalvãoMSSQL Senior EngineerCommented:
You can verify the ports in SQL Server Network Configuration / Protocols for the desired instance and TCP/IP.
zolfAuthor Commented:
Here is my service on the Report server

1
zolfAuthor Commented:
I dont see TCP Port for the named instance but the default instance has port 1433

1
Vitor MontalvãoMSSQL Senior EngineerCommented:
This means the named instance is using dynamic ports (it's the default configuration for named ports).
Now, you have two options:

1.

Set a static port for the named instance by providing the new port number in TCP Port field and remove the 0 from TCP Dynamic Port

2.

Keep the Dynamic Port and create an exception in the Firewall to sqlservr.exe (the SQL Server service) instead of a specific port number
zolfAuthor Commented:
Thanks for your help. What do you recon??
Can you provide some tutorial link doing those 2 methods.
What port do I assign to this instance if i have to go for the first option??
Vitor MontalvãoMSSQL Senior EngineerCommented:
Any port that isn't used officially. Yo can see the list here in this Wikipedia article but something between 49152 and 65535 would be safe for sure.

There's no correct or wrong method. All depends on the security policy of your company. Talk with the Security Engineers if there exists in your company.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
zolfAuthor Commented:
Thanks
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.