Microsoft SQL Server, Error: 64

Hi,

I have a computer (Win7 Pro) on our network who cannot connect to a SQL server outside the Network. However, If I try on another computer (Windows 7 Pro) to connect on the same server with the same credentials, it works. I have attached the error message from MS SQL Server Management Studio 2008. I am using the server's IP as a server name.

SQL Server Management Studio error
Thank you for your help.
David DumaisAgent au support technique et logistiquesAsked:
Who is Participating?
 
arnoldCommented:
Working client info versus?
Ip/netmask can not be the same, ip has to be unique.

Do you have vlans?
Disconnect client that does not work from network, change working client ip to that that the client that does not and see if it relates to ip, do the same on the client that does not work, set its ip to the one that did.
0
 
Kyle AbrahamsSenior .Net DeveloperCommented:
From:
https://social.msdn.microsoft.com/Forums/vstudio/en-US/2d11b6f9-3ada-4682-b643-c721a97af4ba/cant-connect-to-database-after-installing-vs-11-pro-beta?forum=vssetup

try opening up a command prompt as admin and running:
netsh Winsock reset

Open in new window

0
 
arnoldCommented:
Ip/netmask of the system that works versus the one that does not?
Are you entering the SQL login/or us it using Windows authentication? Same user logged into the two computer when the connection is attempted?
Do you require connection encryption?
Check the installed SQL native client library make sure you have SQL 2008 native client library Installed .....

What version of ssms is installed on this system versus the one that works?
0
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
Daniel JonesData Research AnalystCommented:
> Go to the SQL Configuration Manager
> Expand the SQL Network Configuration > click on the PROTOCOLS node
> Right click on TCP/IP > open up the PROPERTIES panel
> Select the IP ADDRESS tab
> Make sure the values for the IP ADDRESS fields are correct and match the system it is running on.
Restart the service

Make sure you fill in the TCP PORT, even if you are using the default 1433
0
 
arnoldCommented:
The error is a protocol mismatch, an ssms for SQL 2005 will not connect to SQL 2012 or newer successfully.
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Arnold may have a point here.
What's the version of the SQL Server instance that you're trying to connect to?
What's the version of the SSMS in your client computer? This should be equal or greater version than the target SQL Server version.
0
 
David DumaisAgent au support technique et logistiquesAuthor Commented:
I tried the netsh Winsock reset and no sucess

Ip/netmask of the system that works versus the one that does not are the same

I am using a SQL login with no encryption

The Server has this SQL Version

Microsoft SQL Server Management Studio                                    12.0.2000.8
Microsoft Analysis Services Client Tools                                    12.0.2000.8
Microsoft Data Access Components (MDAC)                                    6.3.9600.17415
Microsoft MSXML                                    3.0 6.0
Microsoft Internet Explorer                                    9.11.9600.18427
Microsoft .NET Framework                                    4.0.30319.42000
Operating System                                    6.3.9600

And the client computer:

Microsoft SQL Server Management Studio                                    12.0.2569.0
Microsoft Analysis Services Client Tools                                    12.0.2569.0
Microsoft Data Access Components (MDAC)                                    6.1.7601.17514
Microsoft MSXML                                    3.0 6.0
Microsoft Internet Explorer                                    9.11.9600.18499
Microsoft .NET Framework                                    4.0.30319.42000
Operating System                                    6.1.7601
0
 
David DumaisAgent au support technique et logistiquesAuthor Commented:
I did:
ipconfig /release
ipconfig /flushDNS
immediately shut down the computer.

After a fresh start, computer had a new IP and everything was working fine. Thank you very much for the help.
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.

All Courses

From novice to tech pro — start learning today.