Firebird database connection by FireDAC after Windows 10 update

0
votes

I have some delphi applications with connection to Firebird database by FireDAC technology. It works fine, but after Windows 10 update 1803, cannot connect to database when I call application stored in network path (example: \comp1\share\myapp.exe or Q:\myapp.exe, Q: is mapped server path). Error status is 335544721 with illegal parameter. The same build of application stored on local path works fine. Can anybody help Me?

2
delphiwindows-10firebirdfiredac
It might help to know what value the Database property is in each case. Debug to make absolutely certain it's the same. – Dave Nottage
what OS is running the share? The latest Win 10 forbids access to SMBv1 shares. – whosrdaddy
@whosrdaddy was that the reason they removed Home Group feature I wonder ? – Arioch 'The
What is connection string you pass to the database server? – Arioch 'The
Using databases on a shared drive by default is not possible, to do so would mean that a very unsafe feature would have been enabled in the Firebird config. You should always connect through a Firebird server on the machine hosting the database file. I do wonder though if the networking changes made in Windows 10.1803 maybe broke the Firebird WNET protocol. – Mark Rotteveel

2 Answers

0
votes

I've got the same problem!! The reason is the Firebird version 1.5.x (maybe 2.5 too?). Windows Update 1803 blocks the communication between client and server. The only solution is to migrate to Firebird 3.0.x (or to uninstall the update - not a really good option).

0
votes

I had the same problem with my delphi application I developed a couple years ago, after an update to windows 10 in one of my machines it suddenly drops the connection to the firebird server (2.50 in superserver mode) installed on a windows 7 host, while my other hosts (win xp, win 2003, win 7 and 8.1) connects normally, when I ping or telnet to the server adresse from win10 (telnet 192.168.1.X 3050) the connection establishes, I have tried everything like enabling Smbv1 and disabling v2 and v3, run it under a VM (win 7) machine inside win10 I was surprised to not being able to connect too, then I realised that it wasn't a network hardware configuration problem, but for unexplained reasons WINDOWS DEFENDER, I just disabled it and then my app was able to connect.

And don't rely on firebird's returned error messages they don't discribe the real issue, and can mislead you.

I forgot to mention that I did enabled some services before disabling win defender, wich were disabled after windows update 1803: Set both Function Discovery Services to Automatic and Start Them SSDP Discovery set to automatic. UPnP Device Host set to automatic.