RE: AW: RE: AW: RE: Re: RE: Re: RE: IDS10 ODBC

Hi Michael, We are still waiting for netstat -anp | grep 908[89] output. Next, try on linux box this: telnet 192.168.2.236 9088 and if you receive this: Trying 192.168.2.236... telnet: connect to address 192.168.2.236: Connection refused telnet: Unable to connect to remote host: Connection refused that means that you can not connect to your IDS on external address on port 9088. This can be caused by IDS not listening on external address (if you have sles9 in 3rd column in sqlhosts, and sles9 is in /etc/hosts defined as: 127.0.0.1 localhost.localdomain localhost sles9 then IDS is NOT listening on external address. IDS resolvs third column in /etc/hosts and IDS gets ONLY localhost address (127.0.0.1) If you put asterisk (*) in 3rd column inside sqlhosts (in all rows defining local instances) then IDS should listen (bind) ALL possible addresses. E.g. sles9 onsoctcp * 9088 sles9odbc onsoctcp * 9089 Of course, netstat -anp | grep 908[89] would give us detailed information on which address(es) is IDS listening. HTH Hrvoje -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of MICHAEL MEIER Sent: Friday, January 18, 2008 4:38 PM To: ids@iiug.org Subject: Re: AW: RE: AW: RE: Re: RE: Re: RE: IDS10 ODBC [10988] Thats one of my question. In the file /usr/informix/online.log I only have one msg: "Server started". In the ISA Web interface I have some more messages but none related to any tcp communication. Maybe I can switsch that on, but I did'nt found something in onconfig. **************************************************************************** *** Forum Note: Use "Reply" to post a response in the discussion forum. See you at the IIUG Informix 2008 Conference The Power Conference for Informix Professionals April 27 - 30, 2008 Marriott Overland Park (Kansas City), Kansas http://www.iiug.org/conf Registration Now Open!!

Thanks a lot. I put * in the third column. Now it is OK nd working. sles9 in that would mean 127.0.0.2 so the ids don't listen to an external address. This is a "nice" trap. Thanks a lot for your patientness.

I do not understand what you mean by "trap" but IDS is doing exactly what you configured to do: hostname sles9 in your case is resolving to nothing else but localhost (127.0.0.1) and IDS after reading sqlhost file binds port on that address. HTH Hrvoje -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of MICHAEL MEIER Sent: Monday, January 21, 2008 12:48 PM To: ids@iiug.org Subject: Re: RE: AW: RE: AW: RE: Re: RE: Re: RE: IDS10 ODBC [11024] Thanks a lot. I put * in the third column. Now it is OK nd working. sles9 in that would mean 127.0.0.2 so the ids don't listen to an external address. This is a "nice" trap. Thanks a lot for your patientness. **************************************************************************** *** Forum Note: Use "Reply" to post a response in the discussion forum. See you at the IIUG Informix 2008 Conference The Power Conference for Informix Professionals April 27 - 30, 2008 Marriott Overland Park (Kansas City), Kansas http://www.iiug.org/conf Registration Now Open!!

For me it was a trap because the doc for sqlhosts say dbserver protocol host service I thought "host" is the host where the "service" is running. Sorry but I only have the link to the german helpfile (or it is german because of a cookie) http://publib.boulder.ibm.com/infocenter/idshelp/v10/index.jsp?topic=/com.ibm.ad min.doc/admin153.htm It says clearly: Das Hostnamensfeld (hostname unter UNIX oder host unter Windows) enthaelt den Namen des Computers, auf dem sich der Datenbankserver befindet. Shortly that means The host of the IDS. I think you must be very clever to track down that this implied that if this address is a "127" address it only allows local connections. I give you my word, there is nothing in my doc that pointed this out or give me a hint in this direction. Also, there isn't any comment that a * is allwed !

Please read: http://publib.boulder.ibm.com/infocenter/idshelp/v10/index.jsp?topic=/com.ib m.admin.doc/admin156.htm It explains wildcard usage in hostname field inside sqlhosts file. Hrvoje -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of MICHAEL MEIER Sent: Monday, January 21, 2008 2:46 PM To: ids@iiug.org Subject: Re: RE: RE: AW: RE: AW: RE: Re: RE: Re: RE: ID.... [11029] For me it was a trap because the doc for sqlhosts say dbserver protocol host service I thought "host" is the host where the "service" is running. Sorry but I only have the link to the german helpfile (or it is german because of a cookie) http://publib.boulder.ibm.com/infocenter/idshelp/v10/index.jsp?topic=/com.ib m.admin.doc/admin153.htm It says clearly: Das Hostnamensfeld (hostname unter UNIX oder host unter Windows) enthaelt den Namen des Computers, auf dem sich der Datenbankserver befindet. Shortly that means The host of the IDS. I think you must be very clever to track down that this implied that if this address is a "127" address it only allows local connections. I give you my word, there is nothing in my doc that pointed this out or give me a hint in this direction. Also, there isn't any comment that a * is allwed ! **************************************************************************** *** Forum Note: Use "Reply" to post a response in the discussion forum. See you at the IIUG Informix 2008 Conference The Power Conference for Informix Professionals April 27 - 30, 2008 Marriott Overland Park (Kansas City), Kansas http://www.iiug.org/conf Registration Now Open!!