Discussion:
[Firebird-odbc-devel] ODBC Connection
Woody
2010-12-07 23:02:56 UTC
Permalink
Hello,

Was directed here from firebird-support group.

I've never connected to FB using ODBC so I downloaded the driver from the
FirebirdSQL.org site and installed it in an XP virtual machine. My main
machine is running FB SS 1.5 and using normal client connections
(fbclient.dll) everything works fine.

When trying to configure an ODBC connection through the Windows control
panel, I can connect to the local (in the VM) FB server but it won't connect
to my main computer FB server.

I'm using the IP connection string format:

myserver:d:\databases\wonderware.fdb

Windows firewall is turned off in the virtual machine. IBOConsole connects
fine using normal client so I know everything is working normally. I just
can't get the ODBC driver to connect.

Any suggestions on what else I can try or whether I need to supply more
information?

TIA

Woody (TMW)
Maya Opperman
2010-12-08 03:59:48 UTC
Permalink
whether I need to supply more information?
Got an error message?
Woody
2010-12-08 04:05:22 UTC
Permalink
Post by Maya Opperman
whether I need to supply more information?
Got an error message?
I get a dialog that says Connection to <dbname> failed. That's it. I have
tried several databases but none will connect.

Woody (TMW)
Helen Borrie
2010-12-08 03:40:29 UTC
Permalink
Post by Woody
Hello,
Was directed here from firebird-support group.
I've never connected to FB using ODBC so I downloaded the driver from the
FirebirdSQL.org site and installed it in an XP virtual machine. My main
machine is running FB SS 1.5 and using normal client connections
(fbclient.dll) everything works fine.
When trying to configure an ODBC connection through the Windows control
panel, I can connect to the local (in the VM) FB server but it won't connect
to my main computer FB server.
myserver:d:\databases\wonderware.fdb
Windows firewall is turned off in the virtual machine. IBOConsole connects
fine using normal client so I know everything is working normally. I just
can't get the ODBC driver to connect.
Any suggestions on what else I can try or whether I need to supply more
information?
Does your datasource setup look anything like this?
Note, this connection is made using a database alias for that database on the remote server.

The client entry should point to fbclient.dll on the *client* computer.
Emacs!


The cursor in this screenshot is sitting on the "Test" button and the test was ok.

No drama, either, using dBrowser (free download from dbSoftlab, http://www.dbsoftlab.com/database-editors/database-browser/overview.html ).

Emacs!

I'm rather pleased with this. :-) My first test of Alexander's RC2, no dramas!

Helen
Woody
2010-12-08 14:15:36 UTC
Permalink
Post by Helen Borrie
Does your datasource setup look anything like this?
Note, this connection is made using a database alias for that database on
the remote server.
The client entry should point to fbclient.dll on the *client* computer.
Emacs!
Looks about the same, Helen. I tried it with and without aliases, with and
without the client setting.

Do you actually need to the client when working through ODBC? I know that
using the local database, it works fine without the client setting.

Woody (TMW)
Dimitry Sibiryakov
2010-12-08 14:23:19 UTC
Permalink
Post by Woody
Do you actually need to the client when working through ODBC? I know that
using the local database, it works fine without the client setting.
Yes, FB client is required. No, ODBC driver cannot work with databases without server.
--
SY, SD.
Woody
2010-12-08 14:34:21 UTC
Permalink
Post by Dimitry Sibiryakov
Post by Woody
Do you actually need to the client when working through ODBC? I know that
using the local database, it works fine without the client setting.
Yes, FB client is required. No, ODBC driver cannot work with databases without server.
I know it can't work without a server. What I said was that connecting to
the local server works fine, without specifying the client library. Trying
to connect to a remote server doesn't work, with or without the client
specified.

Woody (TMW)
Woody
2010-12-08 17:18:13 UTC
Permalink
Post by Woody
I know it can't work without a server. What I said was that connecting to
the local server works fine, without specifying the client library. Trying
to connect to a remote server doesn't work, with or without the client
specified.
OK, after further searching and testing, apparently you still need to direct
the ODBC connection to the firebird client, which means it needs to be
installed along with the ODBC driver, something I didn't know.

What was throwing me off when testing, if you put the client location in and
test the connection, it works. However, taking out the client location by
deleting the entry, the connection still works so MS must be storing the
location somewhere even though I removed it from the form. The only way to
clear it is to totally exit the ODBC settings dialogs without saving
anything. The next time you go to create a connection, you have to put the
location in again the first time for even a local connection to work.

Now, on to my problem of connecting to a remote server (my main computer)
from a client (in my VM). I seem to have lost my link totally now since even
IBOConsole won't work. Undoubtedly, my problem isn't related to the ODBC
setup but rather has to do with my own internal issue.

Thanks all for listening and helping. Having never tried to use ODBC with
Firebird, this was very enlightening for me. (I will post further if
resolving my internal issue doesn't fix the problem.)

Woody (TMW)
Michael Möhle
2010-12-08 22:17:57 UTC
Permalink
Which setting do you use for the VM network?
NAT or Bridged? If I remember it right, NAT will not
Work, because VM and Host will have the same ip.
Michael

-----Original Message-----
From: Woody [mailto:woody-***@gt.rr.com]
Sent: Wednesday, December 08, 2010 6:18 PM
To: firebird-odbc-***@lists.sourceforge.net
Subject: Re: [Firebird-odbc-devel] ODBC Connection
Post by Woody
I know it can't work without a server. What I said was that connecting to
the local server works fine, without specifying the client library. Trying
to connect to a remote server doesn't work, with or without the client
specified.
OK, after further searching and testing, apparently you still need to direct

the ODBC connection to the firebird client, which means it needs to be
installed along with the ODBC driver, something I didn't know.

What was throwing me off when testing, if you put the client location in and

test the connection, it works. However, taking out the client location by
deleting the entry, the connection still works so MS must be storing the
location somewhere even though I removed it from the form. The only way to
clear it is to totally exit the ODBC settings dialogs without saving
anything. The next time you go to create a connection, you have to put the
location in again the first time for even a local connection to work.

Now, on to my problem of connecting to a remote server (my main computer)
from a client (in my VM). I seem to have lost my link totally now since even

IBOConsole won't work. Undoubtedly, my problem isn't related to the ODBC
setup but rather has to do with my own internal issue.

Thanks all for listening and helping. Having never tried to use ODBC with
Firebird, this was very enlightening for me. (I will post further if
resolving my internal issue doesn't fix the problem.)

Woody (TMW)


----------------------------------------------------------------------------
--
This SF Dev2Dev email is sponsored by:

WikiLeaks The End of the Free Internet
http://p.sf.net/sfu/therealnews-com
Woody
2010-12-09 14:03:04 UTC
Permalink
Post by Michael Möhle
Which setting do you use for the VM network?
NAT or Bridged? If I remember it right, NAT will not
Work, because VM and Host will have the same ip.
Michael
VM and host have different IP's. As a matter of fact, the main computer has
a static IP.

I believe my issue is related to the firewall in Windows 7 on my main
machine. Turning it off allows the connection to go through. I recently
updated to Windows 7 from XP Pro and I've found several things different
regarding interoperability within my home network.

Thanks,

Woody (TMW)

Loading...