Hi! I have had a fb-virtual windows server on aws without problems. This time i went for .x64, superserver.
I could CREATE a database from my client machine, but not CONNECT to it in Amazons aws. The same thing happened when i went and tried Microsofts Azure. *Funnily enough, i could connect when i specified the PORT even though i did a standard install.* So, FYI, if you can remotely add users and create databases, but not connect to the databases, the (strange) solution was to use a connection string including the port number "cloud.ip.address/3050:F:\Data\Database.fdb" works "cloud.ip.address:F:\Data\Database.fdb" does NOT work This is interesting because during all the years i have deployed firebird behind walls and NATs and all sorts of VPNs it never ever behaved like this. HTH someone, Regards, /Dany
