Off-platform SDK
Hi all. I have IDS 7.31 running on a Solaris machine. I have Apache/PHP/Informix SDK running on another Solaris machine - no problems. I have a Linux machine with Apache/PHP/Informix SDK. Apache/PHP work fine. I can't connect to the IDS. I've compared configurations between this machine and the Solaris Apache/PHP/SDK machine, and I haven't been able to find what the differences are between the two. $db=ifx_connect("ifas@online", "user", "password"); produces: Warning: ifx_connect(): E [SQLSTATE=IX 000 SQLCODE=-25596] in /var/www/html/informix-test.php on line 10 The same line of code on the Solaris Apache/PHP/SDK makes the connection just fine. I found on another forum that I should verify that the $INFORMIXSERVER exists in my sqlhosts file. It does. But on the Solaris Apache/PHP/SDK machine (which works), $INFORMIXSERVER doesn't appear to be set to anything! and the sqlhosts file looks identical to the Linux machine's. What should I be looking for on an off-platform machine with the SDK installed that would keep me from making a connection? Thanks, Brian McLaughlin Administrative Computing George Fox University bmclaugh@georgefox.edu
Hi,
being on the Linux machine, using username and password
can you connect to IDS (on the same Linux machine) via
network connection ?
You can test this using the "dbaccess" utility that comes with
the IDS server. With the environment set for the server (and
$INFORMIXSERVER set to a servername that is configured
for TCP/IP connections, i.e. having "onsoctcp" as protocol in
your sqlhosts file) execute the "dbaccess" utility. It starts in
a text-based terminal window. From the menu choose
"Connection" -> "Connect". Then if asked choose your
IDS server (again). Then you're prompted to enter your user
name and next prompt your password. After having entered
both it should say "Connected." in the status line (at bottom)
and offer you a choice of the databases residing on the server.
That was the good case.
If you get an error along the lines of "incorrect password"
(e.g. error -952), then my guess is that you've configured some
kind of password encryption that IDS doesn't support (assuming
you typed the password correctly).
IDS supports only the normal UNIX password encryption
(implemented by the crypt() call), but not methods like MD5 or some
other "unknown" PAM. (Since 9.40.UC2 PAM is supported, but there's
some configuration necessary to enable it.)
Some Linux distributions are known to configure a method other than
normal UNIX password encryption as default, so that may be the reason
for your problem.
Regards,
Martin
--
Martin Fuerderer
IBM Informix Development Munich
Data Management Solutions
"BRIAN MCLAU...." <bmclaugh@georgefox.edu>
Sent by: forum.subscriber@iiug.org
16.03.2004 01:40
To
ids@iiug.org
cc
Subject
Off-platform SDK [2678]
Hi all.
I have IDS 7.31 running on a Solaris machine.
I have Apache/PHP/Informix SDK running on another Solaris machine - no
problems.
I have a Linux machine with Apache/PHP/Informix SDK.
Apache/PHP work fine. I can't connect to the IDS.
I've compared configurations between this machine and the Solaris
Apache/PHP/SDK machine, and I haven't been able to find what the
differences are between the two.
$db=ifx_connect("ifas@online", "user", "password");
produces:
Warning: ifx_connect(): E [SQLSTATE=IX 000 SQLCODE=-25596] in
/var/www/html/informix-test.php on line 10
The same line of code on the Solaris Apache/PHP/SDK makes the connection
just fine.
I found on another forum that I should verify that the $INFORMIXSERVER
exists in my sqlhosts file. It does. But on the Solaris Apache/PHP/SDK
machine (which works), $INFORMIXSERVER doesn't appear to be set to
anything! and the sqlhosts file looks identical to the Linux machine's.
What should I be looking for on an off-platform machine with the SDK
installed that would keep me from making a connection?
Thanks,
Brian McLaughlin
Administrative Computing
George Fox University
bmclaugh@georgefox.edu
Thanks for those that sent me advice on this. The main problem turned out to be the service listed in the sqlhosts file on the Linux machine. I had ontlitcp, and it needed to be onsoctcp. Brian McLaughlin Administrative Computing George Fox University (503) 554-2587