Re: I-Net 5.01 WF2 hangs on disconnect
Posted in 1996
Topics: Connectivity: ODBC / JDBC / .NET, Networking & sqlhosts Configuration, Cloud, Docker & Containers
Hello Mike, I do remember reading about the support of Winsock complaint TCP/IP stacks from different vendors in the Informix NET Release Notes. Informix has mentioned that it works well only with some TCP/IP stacks for the particular version of INET you are using. I know for sure it works well with Microsoft TCP/IP for WFW , but regarding other vendors, looking into the release/documentation notes for INET may indicate something. HTH. Puru Balakrishnan Symantec Mike_Dawson@cc.chiron.com (Mike Dawson) wrote: >Can anyone help with the following I-Net problem. >Our problem is that a large number of our PCs consistently crash when >disconnecting (logging off) from the Informix database. Generally, what >happens is that upon disconnect the user is instantly dumped from Windows to >a C:> prompt and the PC is hung. Sometimes the PC will hang inside Windows >without dumping to a C:> prompt. We have no problems establishing the >connection and retrieving data from the database. This happens strictly >when disconnecting from the database. >Our environment is the following: >We connect PCs to Informix SE (version 5) running on a SunOS 4.1 based host >via I-Net 5.01 WF2. The applications we use are MS Access and Crystal >Reports, both of which use ODBC to connect to Informix I-Net. We are using >InterSolv's latest 2.0 ODBC driver for Informix as the ODBC link from the >application to I-Net. Our company uses a wide assortment of Compaq PCs >running Windows 3.1. And finally, our PCs use WinSock 1.1 on top of a >TCP/IP stack from FTP Software (version 2.31). I don't think this matters >but our LAN environment is Banyan VINES. >PCs that have this problem always have the problem. Other PCs, like mine, >NEVER have this problem. We have not been able to pinpoint any common >factors between PCs which exhibit this problem and those that don't. >Has anyone had this problem? More importantly, can anyone make any >suggestions as to what our problem is or things to check? >-- >Mike Dawson >Chiron Corp. (IS&T) >Emeryville, CA >Mike_Dawson@cc.chiron.com >Voice: (510) 420-4259 FAX: (510) 420-4820 >-------------------------