Update 2:
I also tried to connect with isql from another windows 10 machine which has
firebird 2.5 installed thru VPN to the windows server. That worked.
Update:
I tested also the 64 Bit odbc client on the windows 10 machine. Same error.
From: Dimitry Sibiryakov (24. Juli 2018, 17:56)
> W
Update:
I tested also the 64 Bit odbc client on the windows 10 machine. Same error.
From: Dimitry Sibiryakov (24. Juli 2018, 17:56)
> With Firebird 3 local file path in connection string usually end up in
> using embedded
> mode which don't need running server.
Thanks for that hint! As you
From: Dimitry Sibiryakov (24. Juli 2018, 17:56)
> With Firebird 3 local file path in connection string usually end up in
> using embedded
> mode which don't need running server.
Thanks for that hint! As you have noticed I am totally greenhorn with Firebird.
The windows service for Firebird
24.07.2018 17:28, Helge Schild wrote:
Is there a different firebird server for TCP/IP connections than for
connections thru a local file path? The latter works fine.
With Firebird 3 local file path in connection string usually end up in using embedded
mode which don't need running server.
Von: Dimitry Sibiryakov (24. Juli 2018, 16:42)
> 24.07.2018 14:17, Helge Schild wrote:
> > What could be wrong?
>
>A lot of things. The most obvious one: Firebird server is not run.
Is there a different firebird server for TCP/IP connections than for
connections thru a local file pa
24.07.2018 14:17, Helge Schild wrote:
What could be wrong?
A lot of things. The most obvious one: Firebird server is not run.
--
WBR, SD.
--
Check out the vibrant tech community on one of the world's most
engagin
Hi,
I cannot establish an ODBC connection over TCP/IP from Windows 10 to Windows
Server 2016 over VPN. On the server the ODBC client works fine if I enter just
the local file path for the database.
So on the server this database name works fine:
"F:\...\FDB".
However using the local lo
