Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Mark Collins could not connect to Informix 11.70 Developer Edition on Windows 7 from dbaccess (error 908) though Server Studio worked. Jim Xiao suspected IPv6 and the host setting with a leading asterisk. Mark tried several host values, each fixing only one tool. Jim then suggested a dummy file IFX_DISABLE_IPV6 in $INFORMIXDIR/etc, which made both work.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
MARK COLLINS — — source: IIUG Forums & Mailing Lists
I'm sure I'm missing something simple in my configuration. I installed 11.70
Developer Edition on Windows 7 64-bit. The installation went fine, and I was
able to run 'onstat -p' and 'dbaccess'. In addition, I have the core edition
of Server Studio, and I was able to define a connection and open that
connection to run SQL queries against the Windows installation.
Then, I logged off and went home for the day. Now, I can still connect via
Server Studio, but I have problems when connecting from the command prompt. I
have set INFORMIXDIR, INFORMIXSERVER and DB_LOCALE environment variables, and
'onstat -p' (and other onstat options) runs fine. Also, dbaccess starts and
looks fine, until I try to go to the Query menu.
At that time, it presents me with a SELECT DATABASE prompt at the top of the
screen, with a status message 'Running . . .' at the bottom. After a bit of
time passes, the status message changes to '908: Attempt to connect to
database server (ol_informix1170) failed.'
I am logged into the Windows PC with the same user-id that successfully
connects via Server Studio, so I think the user-id is OK. This is the same
user-id that I used when installing the product in the first place.
All of my experience with Informix to date has been on Unix. This may be
something specific to Windows setup?
Thanks in advance.
probably the IP address issue, you can put a '*' before the host name through
setnet32, then client can connect to IDS after moving from one network to
other network. also you can check if it's IPv6 related. if the server is only
listening on the IPv6, the IPv4 client cannot connect.
you can run "netsat -na | grep <port>" to get detail information.
↪ replying to JIM XIAO
MARK COLLINS — — source: IIUG Forums & Mailing Lists
Thanks for the suggestion. The issue was related to the HOST key in the
Sqlhosts section of the registry. I had issues connecting with Server Studio
because the HOST key had the "*" at the beginning of the hostname, and Server
Studio says that causes IDS to listen only for IPv6 requests and SS doesn't
support IPv6. The error message suggested setting the HOST key to 0.0.0.0,
which I did, and I was able to connect from Server Studio.
Unfortunately, that prevents me from connecting from dbaccess at the command
prompt. So I tried the following values for the HOST registry key --
127.0.0.1, <computer-name>, and <fully-qualified-computer-name>. In each case,
I am able to connect from dbaccess, but not from Server Studio.
At this time, I can at least use the command line utilities that I currently
need, but I would like to be able to get Server Studio working again. Anyone
have any ideas on how to do that? Server Studio is running on the same machine
as the IDS Dev Ed instance, if that makes any difference.
Thanks.
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.