June 3, 2015 at 7:33 am
I am having a strange issue with connecting to SQL server instance with management studio from my local computer. But I can connect to SQL instance if I RDP into the box itself. Also, my credentials work when I try from my colleague's computer. Sounds like it has to do something with the local installation of management studio. We have SQL server 2014 . Appreciate any suggestions. Thanks!
June 3, 2015 at 7:36 am
Start by telling us what the error message is :-D!
June 3, 2015 at 7:51 am
Here is the error message -
Cannot Connect to<servername>
-The 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 remore connections (provider::Named Pipes Provider, error:40- Could not open a connection to SQL Server)(Microsoft SQL Server, Error:53)
- The network path was not found
June 3, 2015 at 7:55 am
Troubleshooting SQL Server connectivity issues
-- Gianluca Sartori
June 3, 2015 at 10:01 am
Hi Spaghettidba, Everything looks good in comparison to the article you provided. The problem still exists.
June 3, 2015 at 12:41 pm
Try forcing the protocol to TCP IP in SSMS
-- Gianluca Sartori
June 3, 2015 at 2:00 pm
I tried to force TCP protocol. This time the error is slightly different..
Cannot Connect to<servername>
-The 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- No Connection could be made because the target machine actively refused it. )(Microsoft SQL Server, Error:10061)
-No connection could be made because the target machine actively refused it.
On Configuration manager, I checked the status of TCP/IP, Named Pipes and shared memory (under SQL Server Network Configuration) and they are all enabled. What else should I check?
Thanks!
June 3, 2015 at 2:18 pm
Can you connect to other instances? If so, it's not likely to be a SSMS issue.
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
June 3, 2015 at 2:58 pm
If this is a named instance, try disabling the firewall on your computer. Named instances rely on SQLBrowser, which uses UDP port 1434 to communicate. Some firewalls don't like the behavior of SQLBrowser that sometimes replies from a different address from the one being contacted (happens often with clusters, but any machine with multiple IP addresses can experience this).
If it works with the firewall down, add a rule for port 1434 UDP any-any.
-- Gianluca Sartori
June 4, 2015 at 8:02 am
Can you PING the server name?
Also, can you connect using the server's IP address instead of the server name?
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
June 4, 2015 at 2:51 pm
@Alvin - I can connect to other instances.
@spaggetidba- It's a default instance
@Eric- I can ping server. Trying to connect with IP address don't work either.
Thanks!
June 4, 2015 at 3:19 pm
The coworker who can successfully login, have them come by your desk, and then do the following using your PC.
While holding down Shift key, right click on the SSMS program icon. Choose the option 'Run as different user'. Have your coworker run SSMS using their own credentials, and then attempt to login to the SQL Server instance as themselves.
If it works, then at least you've confirmed it's probably not an issue related to client tools, networking, or IP address filtering.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply