• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 66
  • Last Modified:

SQL Management Studio Connection Issues

I am having an issue where I am no longer able to connect to our SQL server from the office.  This could be related to a reset of our office firewall though I've gone through all the settings and haven't been able to get it working so far.  I was able to connect from another location and am able to connect to is from the problem location with different applications that use connection strings which is curious considering the error message (attached) indicates that there is an issue with the connection string that management studio doesn't use... I'm hoping that it is something simple that I'm overlooking but have had no luck with the different blog posts I've come across to date.  Any help would be appreciated.

Thanks,
Greg
Screenshot---12_13_2017---3_58_24-PM.png
0
Greg_L_WER
Asked:
Greg_L_WER
  • 6
  • 2
  • 2
  • +1
1 Solution
 
Pawan KumarDatabase ExpertCommented:
Are you able to ping your server?
0
 
Greg_L_WERAuthor Commented:
Hi Panwan... thanks for the quick reply.  Yes I am able to ping it... average 55ms response time.   I can telnet to it from my local PC as well "telnet 000.000.000.000 8452"
0
 
Pawan KumarDatabase ExpertCommented:
are you sql services running ?

Run -> Services.msc -> check SQL Server services... if not running , start them

It could be one of the problems mentioned here.. firewall...

http://support.sysonline.com/support/solutions/articles/4000016491-errmsg-a-network-related-or-instance-specific-error-occurred-while-establishing-a-connection-to-sql
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
Greg_L_WERAuthor Commented:
Thanks Pawan... the services are definitely running and we are able to connect to the database through other means (eg: different locally run software).  It's just management studio that isn't able to connect for some reason.  I'll have to go through the article tomorrow when I'm back in the office and report back what I find.  Thanks for the help so far :)

Thanks,
Greg
1
 
Mark WillsTopic AdvisorCommented:
Could be a ports problem.... you would normally use port number after the iP address... and mixed authentication (not windows)

Will look at your error message and get back to you.

Just to be clear, you can see the server, you can invoke SSMS, but when you go to log in, that's when you get the error message.

Or,

You are running your own (local) SSMS and trying to connect to the remote DB.

And the server does have remote connections enabled ?
0
 
Nakul VachhrajaniTechnical Architect, Capgemini IndiaCommented:
It could be Ports as mentioned by Mark.

Other thing would be to click on "Options" in the SSMS login screen and review the "Connection Properties" and "Additional Connection Parameters" tab. Confirm that the network technology, packet size and any other custom connection string properties are correct.

A very remote chance is that someone from the DBA team blocked access to the SQL Server Management Studio?
0
 
Greg_L_WERAuthor Commented:
Thanks Mark & Nakul!

You are correct SSMS is working fine and I'm able to connect to local DB's.  It's when I try to connect to using my local SSMS connecting to the remote server that there is an issue.  I am able to connect to the remote server from another office using SSMS locally so it shouldn't be anything that's changed on the remote server end (where the firewall is managed by our ISP but changes are only made if I request them to) .  

I'm quite certain that it's related to a restore of our local firewall settings after it lost some settings and we found out that the latest available backed up config file didn't contain the some changes... though when I compare firewall settings between the office that is able to connect to the DB and ours I've not come across anything that is different...

I checked the "Additional Connection Parameters" tab that there aren't any being used.

Forgive my firewall port ignorance but are outbound ports normally closed or is it just incoming that are configured to be opened or closed?

Thanks,
Greg
0
 
Greg_L_WERAuthor Commented:
Back at this issue after the holidays :)  I am able to successfully ping and telnet to the server from a command prompt from the same PC that I can't connect to with SSMS.  Any chance this is a clue? Back to the port question above... are outbound ports normally closed or is it just incoming that are configured to be opened or closed?

Thanks,
Greg
0
 
Greg_L_WERAuthor Commented:
Have finally found the solution.  It's so obvious now that I see it but clearly was well hidden to all up front :)  It turned out to be that I'd used a colon instead of a comma to separate the IP and the port numbers.
0
 
Greg_L_WERAuthor Commented:
Solved it on my own.
0
 
Mark WillsTopic AdvisorCommented:
Pesky Colon....

Glad you were able to figure it out....

Cheers,
Mark Wills
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

  • 6
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now