Dennis,
You can connect to a remote pc, via a remote DAS? In other words, if
you change your jdbc connect string from:
jdbc:ingres://localhost:II7/iidbdb
to
jdbc:ingres://remote_ip:II7/iidbdb
Does that work? If it does, than try this: create a vnode on the
remote ingres installation pc that points back to your machine:
my_company_pc_vnode, and test it. Does that work? If not, you either
have a firewall issue or some other problem with your installation. I
would uninstall ingres then reinstall it.
If you can connect via Ingres Net to your local machine, then try
this: change your jdbc connect string to :
jdbc:ingres://remote_ip:II7/my_company_pc_vnode::iidbdb
You will be connecting from a remote iigcd back to your local machine
over Ingres Net; if that works, then you will have proven that you
have a problem with the local DAS server (I'm still betting it's a
firewall issue -- either windows firewall or whatever software your
company uses to protect the machine!).
IIRC, the ingres installer should automatically add an exception to
windows firewall (or prompt you during startup?) That, along with the
ODBC problems you are having, point to some kind of failed install
scenario. Just out of curiosity, was this a clean install of Ingres
2006 Rls 2 Beta? Or did you install on top of a previous version?
Did you use the express install or custom install? Do you remember
any problems or error messages appearing during the install?
You don't have to answer all of those questions ... mostly just
rhetorical! It might be easier just to reinstall everything. Good
luck!
Regards,
Jim Gramling
Rio de Janeiro
Post by Dennis RoeslerPost by Jim GramlingDennis,
Post by Dennis RoeslerAn error occurred while establishing the connection.
Type: com.ingres.gcf.util.SqlEx Error Code: 802817 SQL State: 08001
Message: Communications error while establishing connection.
This is a generic connection error ... which means the jdbc driver
failed to connect to the iigcd port.
My guess would be that, either you have multiple Ingres installations,
and your Ing 2006 Rls 2 installation ID is not "II" ... or you have a
firewall issue. If you use windows firewall, make sure that <Ing2006
path>\ingres\bin\iigcd.exe is listed as an exception in the firewall
configuration dialog.
This is a company pc and I don't think we're using Windows firewall, but
will check into this. The installation ID is II, or at least that is
what the Visual Manager says :-).
Post by Jim GramlingBTW, if you haven't installed the Ingres DTP for Eclipse, you
should ... you're in for a real treat. Very nice integration with the
Eclipse Data Source Explorer! Makes working with Ingres in Java feel
a lot more mainstream!
I did install the Ingres DTP for Eclipse and had the same problem in
Eclipse. When setting up the connection and hitting the test button it
returns "Ping failed." As I mentioned before, remote connections aren't
a problem - I'll just need to figure out what is going on with Windows.
Actually I would like to see a lot of the functionality they showed in
Eclipse in VDBA. I realize that the Eclipse stuff is targeted at the
developer, but they showed a lot of functionality that would also help a
DBA.
Dennis