Remote Firebird 3 client cannot connect to the DB on my PC - firebird

For years I was unable to get my app, on a laptop on my LAN, to connect to the db on my PC.
I was getting the “rejected by” message.
One day I was trying again and viola! It was connected. I do not remember what I had done on my PC (Win 10 Pro, FB 3). Then my PC C drive crashed. After reinstalling all the parts needed I am back to the rejected message. The PC firewall (Win Defender) has a Firebird entry using port 3050. The connection string is “ServerName:c:\FBData\dbname.fdb”.
I am stumped, again. Does anyone have tips on what do to connect?

Related

Mongosqld runs fine, but ODBC fails on test and PowerBI throws error 10060. Connector not working. Windows to two seperate RHEL Servers

The Goal
I need to get data from a MongoDB updated every 15 minutes to use to build into a PowerBI report.
The Gear
I am connected from my windows machine via ssh to an RHEL server (server a). This server is running powerbi connector (SQLD) which is connected to my MongoDB that is running on a different server (server b). I'm also running MySQL on server b. My powerBI connector is installed on server b.
Exactly where I'm at
I am using the steps listed here (and all the associated pages) and have tried everything listed short of writing a config file, as the fact that things are working on mongosqld's end makes me think I don't need it... and if I can't get it working manually, having a config file won't exactly help.
https://docs.mongodb.com/bi-connector/current/connect/powerbi/
Using:
mongosqld --mongo-uri="mongodb://10.xxx.xxx.xx" --auth --mongo-username="ThisGuy" --mongo-password="test"
I successfully map the schema and show an active connection in the command window. I can also access my database from compass using an authorization enabled URL.
When I set up an ODBC connector I use the IP of server a, the user and password from my url, and port 3307. Nothing shows up in the dropdown, when I click 'test' I get the following message:
Connection Failed
[MongoDB][ODBC 1.4(w) Driver]Can't connect to MySQL server4 on '10.xxx.xxx.xxx' (10060)
I have also tried 3306, 27017, and 27015. Just to be safe I also added firewall rules for all traffic on these ports. I've tried this many times, including (just for the hell of it, and I'm kind of new to this stuff) the ip of server b, the ip of my machine, the credentials for MySQL, basically any combination of these things that I can think of.
In powerBI, my odbc driver shows up, and when selected in the dropdown, it asks for a username and password. I have tried both mongo credentials and MySQL. Not sure which I should be using?
regardless, I get the following error inside PowerBI:
Details: "ODBC: ERROR [HY000] [MySQL][ODBC 1.4(w) Driver]Can't connect to MySQL server on '10.xxx.xxx.xxx' (10061)
ERROR [HY000] [MySQL][ODBC 1.4(w) Driver]Can't connect to MySQL server on '10.xxx.xxx.xxx' (10061)"
Thoughts
I don't control either server, although I have root access, being new to this tech and company I am wary of screwing anything up that a co-worker will have to fix. I read in a different SO thread that maybe I need to downgrade the version of MySQL that is running on the server and that it could fix the problem, but I don't think that it will actually help and am afraid I might screw up something else on the server if I do this:
The C Authentication plugin was developed against MySQL 5.7.18 Community Edition (64-bit), and tested with MySQL 5.7.18 Community Edition and the latest version of MongoDB Connector for BI. The plugin is not compatible with MySQL Server or Connector/ODBC driver version 8 and later.
https://dba.stackexchange.com/questions/219550/access-denied-when-connecting-to-mongosqld-with-mysql
Maybe the problem is that server B is listening to server a on port 3307, and that there is another unknown port (not mentioned above) that my ODBC driver must be listening to? I'm not sure how to test for this when you get a step away like this.
So that's it. I'm really stuck and would love some help, I am going to try the downgrade tomorrow if nothing else shakes loose and will keep this thread updated.
Thank you for reading

Unknown issue in PostgreSQL Function

I develop an application using VB6 and ODBC that fetch data from PostgreSQL function.
I used the function "F0006" to get information about item code, name, etc.
So far, my application runs smoothly on the current PC ( Windows 7 SP1 ). Because of the end of the support of Windows 7, we buy a new PC to replace the current that has Windows 10 installed.
We set up the same ODBC connection based on the currently running one and Connection success. But when we try to test our application to fetch the data, it seems can't find the function "F0006" and throw an unknown function message in the New PC ( Windows 10 ).
FYI, PostgreSQL is managed by others, and we don't have Admin DB access to it, and Active Directory is used in our network.
But if we try the same application in the current PC ( Windows 7 ) and other PC that using Windows 10 that has not configured to network AD, the application can get fetch data from the function.
Where could be the source of the problem?
Thanks

PostgreSQL could not receive data from server: Software caused connection abort (0x00002745/10053)

I tried to establish a connection in pgAdmin to the PostgresSQL server.
I always get the message:
could not receive data from server: Software caused connection abort (0x00002745/10053).
I read several posts where people had the same problem but they didn't help me.
Because my version was a bit older I uninstalled the whole postgresql and installed the newest version with the installer of EnterpriseDB (PostgreSQL 9.6 on windows 64). Everything looks fine. But I can't connect to the server from pgAdmin 4 again. I get the same error message.
In the logfile is written: "An existing connection was forcibly closed by the remote host"
Has anybody a clue what the problem could be?
A partial solution for me was to restart the postgresql-server each time after booting up my computer with NET STOP and NET START. This was cumbersome but worked.
Because my computer still had other connection problems, subsequently I updated my system to Windows 10 which totally solved all my problems.

How can I prevent connection error to postgreSQL database after computer restart?

I tried this several times:
I have windows 7. I installed postgresql 9.6.1.-1. I can connect via pgAdmin 4 to the database. But as soon as I restart the PC, I get a connection error:

Can't connect to postgresql server installed locally on my machine

I have installed the DSP(Dreamfactory Service Platform) locally on my Mac Book Pro using Bitnani.
I have a PostGreSQL server running locally on my Macbook, which I want to connect to using the DSP.
I am successfully able to connect to my PostGreSQL server from other applications, which essentially means that there is no problem with the setup.
However, on trying to connect the same from DSP I get the error:- "Failed to launch service "sql": CDbConnection failed to open the DB connection."
My connection string is :- "pgsql:host=localhost;dbname=Pinu"
Also, the password has been correctly entered.
The port is default as 5432. Whether or not I enter the same in the connection string, the connection always fails.
Even though I am trying to add the service as Remote SQL DB, I know that it's actually on the same local host. Not sure if that is the issue.
I also tried entering - 127.0.0.1 in place of localhost, but still I see the same issue.
Any help in this regard would be highly appreciated!
After talking to you via email, it looks like the root issue here is that you haven't successfully upgraded your DSP to the latest version. We are releasing DreamFactory version 1.8 on Bitnami tomorrow, so you should upgrade to the latest version.
As far as your PostgreSQL issue let's explore some options:
1) Connection strings:
a) pgsql:host=localhost;dbname=Pinu
b)
pgsql:host=localhost:5432;dbname-Pinu
c)
pgsql:host=localhost;port=5432;dbname=Pinu
2) If these don't work, try substituting your localhost with
127.0.0.1 (as you've tried previously, but test this in all scenarios).
3)
pgsql:host=localhost;port=5432;dbname=series1;schema=schema_name_here
Typically, Option A should work without a problem.
Give these a try if you would, and if you need some help upgrading then reach out to me again via email.
--Thanks,
Mark