Informix Client SDK on Solaris 2.7
Posted in 2000
Topics: Installation, Setup & Upgrades, Connectivity: ODBC / JDBC / .NET, Connectivity: ESQL/C, 4GL & Embedded SQL, Networking & sqlhosts Configuration, Platform-Specific Issues
I am attempting to connect to an Informix server running on an HP-UX
machine from a Sun Solaris box. I installed the Client SDK 2.40 on the
Sun box and I am not able to connect. I get the following error from a
simple esqlc program:
Error -25574 while connecting to the database: Network driver cannot
open the network device.
My sqlhosts settings are:
mbiodbc ontlitcp mbi 1004
Has anyone successfully set up the Client SDK on Solaris? Any help would
be greatly appreciated.
Thanks,
Mark
Mark Aardsma wrote:
> I am attempting to connect to an Informix server running on an HP-UX
> machine from a Sun Solaris box. I installed the Client SDK 2.40 on the
> Sun box and I am not able to connect. I get the following error from a
> simple esqlc program:
>
> Error -25574 while connecting to the database: Network driver cannot
> open the network device.
>
> My sqlhosts settings are:
>
> mbiodbc ontlitcp mbi 1004>
> Has anyone successfully set up the Client SDK on Solaris? Any help would
> be greatly appreciated.
Yes, and I've been using the reverse connection (HP-UX ClientSDK 2.40
to Solaris 7 IDS.2000) without problem. Can you ping the machine mbi?
Can you rlogin to it? I assume yes. Are you sure that you've got the
environment set as you expect? Probably.
Since the server name, service type and (presumably) hostname are OK,
the residual issue is "What did you mean by service name 1004"? If you
expect that to be used as a number, only root will be able to use that
service; all service numbers less than 1024 are reserved for root only.
That is probably the source of your trouble. Do what you're supposed to
do and create a service in /etc/services called, for example, mbiodbc,
with port number 2004. On both the Sun and the HP. Modify the HP setup
to use the new service number and not 1004 (it worked on the HP because
oninit is a SUID root program and can do privileged operations like use
a reserved port number). Then you should be OK.
--
Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net)
Guardian of DBD::Informix v1.00.PC1 -- see http://www.perl.com/CPAN
#include <disclaimer.h>