Re: SQLEXECD problem

Mark, Your problem is not with protocol because setlitcp and sesoctcp are compatible, we have that configuration over here and it works fine. Maybe something is missing from your I-Connect configuration. Have you set the DBPATH env. variable to the path on your server? Also, have you run the regcopy utility (in C:/informix/bin) to copy your i-connect values in the windows registry? Chris >From owner-informix-list@iiug.org Tue Feb 16 14:54:56 1999 >Received: (from majordom@localhost) by iiug.iiug.org (8.7.5/8.7.3) id QAA24119; Tue, 16 Feb 1999 16:45:06 -0600 (CST) >From: Mark Hayden <mhayden@robertson-associates.com> >To: informix-list@iiug.org >Subject: SQLEXECD problem >Date: Tue, 16 Feb 1999 22:08:36 GMT >Organization: @Home Network Canada >Message-Id: <36C9EB9D.C5CC57D6@robertson-associates.com> >Reply-To: Mark Hayden <mhayden@robertson-associates.com> >X-List-Gateway: comp.databases.informix >Sender: owner-informix-list@iiug.org >Precedence: bulk > >Hello... > >I am trying to set up a UNIXWARE 7 database server using Informix SE >7.23. Most clients will be Windows 95 or NT 4.0 boxes connecting using >ODBC (Intersolv's ODBC driver supplied with the Windows client SDK). >I've been able to locally connect and create or use databases using >DBACCESS, but have not been able to get a remote connection from a >windows box (not even using the ilogin.exe demo program) > >On the Unixware 7 server, I have created the $INFORMIXDIR/etc/sqlhosts >file, added the proper entries to /etc/services and hosts.equiv and >re-started the inetd process to load the changes to the services file >(basically everything the manuals tell me to do). The only problem is, >I can only get sqlexecd to run using a nettype of "setlitcp". Using >"sesoctcp" gives me an error 25507 (service name or protocol unknown) >when I try to start sqlexecd. The only problem is that "sesoctcp" is >the only option INFORMIX-CONNECT seems to allow me! When I run >ilogin.exe when the client is set for sockets and the server for TLI, I >get "database 'stores7' not found on server", even though I can connect >to stores7 locally. Trying to connect from M$ Access using the ODBC >driver gives me a similar error. Obviously both the client and the >server must be set to use the sockets interface > >Can somebody tell me how to get the socket interface to work on the >server? All the documentation I've seen seems to suggest it should work >by simply specifying "sesoctcp" as the nettype in SQLHOSTS. > >Thanks in advance... > >Mark. > > ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com