I am facing this problem:
EXE files made with different versions of TD (4.1, 6.0, 7.0) cannot connect to any database on the network, neither SqlServer2008 via ODBC neither SqlBase 9.0 via native connection. Only Access d.b. with connection string (REMOTEDBNAME=CARSHOP,Driver=Microsoft Access Driver (*.mdb);Dbq=G:\database\access\carshop.mdb;MaxBufferSize=2048;PageTimeout=5;UID=admin;
Connection strings for SqlServer databases are similar (REMOTEDBNAME=ORTOF,Driver=Sql Server;Server=GIGI00\SQL2008;Database=ORTOF;LastUser=sa;UseProcForPrepare=0;AnsiNPW=No;QuotedId=No;AutoTranslate=No;Language=English;
On local d.b. for sqlserver 2008R2 or 2012 there is no problem.
The strange thing is that at runtime I can connect to any d.b. on network or local. With SqlTalk too.
Only one SQL.INI along the path. SqlBase environment variable correctly set. firewall disabled for private and public networks. No changes from last week. Only a W10 upgrade . I am sure that this is the problem but what it changed?
Many thanks in advance
This, of course, is a little problem. so I have to copy and maintain all executables in a local directory instead having all EXE on the network.
This problem happens here to me, I hope that my customers will be safe.
great bheilscher again
Windows 10 update 1803 does not open network connections on executables files on SMBv1 share.
You have to change the network protocol to SMBv2 on your server. Starting with Windows Server 2008, this version is supported.
- Founder/Site Admin
- Posts: 454
- Joined: 24 Feb 2017, 09:12
- Location: Gouda, The Netherlands
I found on Microsoft Italian support an answer with this link
https://www.google.com/url?q=https%3A%2 ... A_Cj9WwUWw
and the guy suggested to verify if SMB.1 was active. Of course it isn't enough. Many thanks again.
Who is online
Users browsing this forum: No registered users and 0 guests