Cannot connect from windows client to IDS 10 with sdk 2.9 on Linux

We are running redhat enterprise 4, and IDS 10. We just cannot connect via tcp from clients on our LAN. We HAVE set up INFORMIX SE on other machines in the past and had no problem. Now we are stumped. On past machines we have run SE and are used to seeing the sqlexecd demon, but how do we see if the IDS tcp service/demon/whatever is even running. What could be wrong? IDS (shared memory) is running, DBaccess is OK - it is just the tcp connectivity we are having a problem with. When we test with ilogin it just hangs and if we wait a hundred years we get a -908. Any help would be much appreciated. Details of setting follow. 1:$INFORMIXDIR - set set as per default 2: path set as per default 3: $INFORMIXSERVER set - pic_ids 4: onconfig ROOTNAME rootdbs ROOTPATH /home/informix/dbspaces/online_root ROOTSIZE 16 giga ... DBSERVERNAME pic_ids DBSERVERALIASES pic_ids1 5: services sqlexec1 1536/tcp 6: sqlhosts pic_ids onipcshm kylie pic_ids pic_ids1 onsoctcp *kylie sqlexec1 7: hosts 192.1.2.3 matilda 127.0.0.1 localhost.localdomain localhost kylie 192.1.2.101 kylie xxx.xxx.xxx.xxx kyliewww where xxx.xxx.xxx.xxx is the external ip[ address (we have two cards)

kjuliff@gmail.com said: > We are running redhat enterprise 4, and IDS 10. > We just cannot connect via tcp from clients on our LAN. We HAVE set up > INFORMIX SE on other machines in the past and had no problem. > > Now we are stumped. On past machines we have run SE and are used to > seeing the sqlexecd demon, but how do we see if the IDS tcp > service/demon/whatever is even running. What could be wrong? I'm pretty sure that it's more likely to be a configuration issue than a listener issue. > IDS (shared memory) is running, DBaccess is OK - it is just the tcp > connectivity we are having a problem with. > > When we test with ilogin it just hangs and if we wait a hundred years > we get a -908. > > Any help would be much appreciated. Details of setting follow. > > 1:$INFORMIXDIR - set set as per default > 2: path set as per default > 3: $INFORMIXSERVER set - pic_ids > 4: onconfig > ROOTNAME rootdbs > ROOTPATH /home/informix/dbspaces/online_root > ROOTSIZE 16 giga > ... > DBSERVERNAME pic_ids > DBSERVERALIASES pic_ids1> > 5: services > sqlexec1 1536/tcp > > 6: sqlhosts > pic_ids onipcshm kylie pic_ids > pic_ids1 onsoctcp *kylie sqlexec1 Have you tried: pic_ids1 ontlitcp *kylie sqlexec1? > 7: hosts > 192.1.2.3 matilda > 127.0.0.1 localhost.localdomain localhost kylie > 192.1.2.101 kylie > xxx.xxx.xxx.xxx kyliewww > > where xxx.xxx.xxx.xxx is the external ip[ address (we have two cards) Good luck! -- Bye now, Obnoxio Information within this post contains forward looking statements within the meaning of Section 27A of the Securities Act of 1933 and Section 21B of the S E C Act of 1934. Statements that involve discussions with respect to projections of future events are not statements of historical fact and may be forward looking statements. Don't rely on them to make a decision. The poster is not a reporting company registered under the Exchange Act of 1934. I have received a life peerage from Her Majesty, who is not an officer, minister or affiliate Labour party member. I intend to recover my loan now, which could cause the parliamentary majority to go down, resulting in losses for you. Today's Labour party has: an accumulated deficit and a reliance on loans from officers and affiliates to pay expenses. It is not an operating political party. The party is going to need financing to continue as a going concern. A failure to finance could cause the party to go out of business. This report shall not be construed as any kind of investment advice or solicitation. You can lose all your money by investing in this party.

We got it to work!!!! We deleted the following from hosts 192.1.2.101 kylie xxx.xxx.xxx.xxx kyliewww