This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 59%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
I have a network around Windows Server 2008, and client workstations under Windows 7 and SQL Server 2000 database applications, everything works well by adding a workstation under Windows 10 and SQL Server 2000 locally it works well, but in network the system blocks without giving me a message this station blocks the executable and does not launch any connection with the server
Your description is not entirely clear. Are you saying that connections stop working, once you add the Windows 10 to the network?
Or are you saying that connection to the SQL 2000 instance does not work from the Windows 10 machine?
What "executable" are you talking about?
in fact the connection between the client station and the server continues but the application which calls for the connection with the database on the server blocks without message for more detail, the same application which uses sql server 2000 on windows server 2008 and windows 7 workstations works very well but with windows 10 workstations
in fact the connection between the client station and the server continues but the application which calls for the connection with the database on the server blocks without message for more detail, the same application which uses sql server 2000 on windows server 2008 and windows 7 workstations works very well but with windows 10 workstations
Hi @alaya mohsen, Not really clear about your issue, could you please describe it with more details?
Your description is still not clear.
I take that you have clients running in Windows 7, and the communication to SQL Server work for these clients. Does this communication still work, when you connect the Windows 10 machines? Or are they stalled?
I hope that you are aware of that SQL 2000 is seriously out of date, and connecting something Windows 10 to SQL 2000 may not work, although it depends on what client API you are using. If you can give details on the application, we may be able to help you.
Else, the only advice we can give is: Upgrade, it's long overdue.
Does this communication still work, when you connect the Windows 10 machines? Or are they stalled? yes all the workstations with Windows 7 continue to work, only the workstation with Windows 10 blocks the application. all shares are checked the privileges too, I access the server with ping without problem the server firewall is stopped Also the same application works well in another site with a Windows 10 server and Windows 10 client workstations.
Does that other site also have SQL 2000 as the database engine? I would not expect SQL 2000 on Windows 10.
The most likely issue is that the Windows 10 machine only wants to talk TLS 1.2, which is complete gibberish to SQL 2000.
But you are very much out in the wilderness on your own here. If it works, you are lucky. If it does not - you are out in the land of the Unsupported.
Yes the other site use same software and same data base engine " sql server 2000"Juste the server is on win 10
If you were able to install SQL Server 2000 on Windows 10, I can only congratulate you. I have never tried myself, but I know that SQL 2005 requires some trickery to install, so I would expect SQL 2000 to be even worse.
Anyway, unless it is TLS and you can fix that, the only advice I have is to upgrade.
Could you explain for me the TLS
TLS = Transport Layer Security. It's a mean to keep a communications channel encrypted. Wikipedia has more information.