Hi:

Have you tried using service NUMBER in place of the service name?

As each new Windows version (and possible Winsock version) change the path
of the services file I always use the port number in the setnet32.

HTH

----- Original Message -----
From: <joe (AT) colsys (DOT) com>
To: <informix-list (AT) iiug (DOT) org>
Sent: Thursday, June 26, 2003 10:12 AM
Subject: Problem connecting under Windows 95


sending to informix-list

I tested this on my system (Win2000) and it worked with service number
instead of the name.

I tried it on the problem Win95 system at the customer site and it kind of
worked. In the ODBC config window for the Informix data source, when I
click the "Apply & Test Connection" button, it connects successfully.

But none of our software that connects to the database through ODBC will
connect. It gets a "Cannot connect to the database server <servername>"
error (where <servername> is correct). Additionally, DBPing's ODBC tab
cannot connect either - it bombs out with an exception - not even a real
error message.

The only other thing I can think of to try (sort of telling them to scrap
Win95) is to download the latest MDAC - even though we don't use MDAC, but
it may replace the ODBC subsystem.

"Fernando Ortiz" <fortiz (AT) lacorona (DOT) com.mx> wrote