Re: Extremely slow connect process and setnet32 processing

Thanks for the responses. It did turn out that I had an invalid DNS server as the first in my list. I removed it and now it only takes 15-20 seconds to start up setnet32. I used LAN analyzer software to figure out that Informix is first trying to resolve a host name 'informix' and a host name '#SoftwareMicrosoftRpcClientProtocols'. I can ALMOST understand it trying to resolve a host named 'informix' even if there is no such host anywhere in my configuration, but trying to resolve an NT Registry key ? I have configured a list of 4 domains to search for the hosts in which makes the problem worse. It tries to search all 4 domains plus an unqualified search (hostname with no domain). It sounds like Informix can't read the registry properly. Does anyone understand what informix is doing here or could suggest a way of validating the registry ? Thanks Jerry Jerry Flood wrote: > > I had I-CLI 2.5 working fine on an NT 4.0 client to an Informix > 5 server. I configured access to a 7.2 server. I now experience > extremely slow connect times as well as an extremely long delay > starting up setnet32. It is apparent that, during startup of > setnet32 (and probably during the connect process) that Informix > is searching the network for something and eventually timing out. > > I cannot figure out what I changed to cause this behaviour. > > Thanks > Jerry Flood -- M. J. Flood Email: jerryflood@attmail.com AT&T Data Services Development Phone: +1 732.949.9706 Room 2G-214, 101 Crawfords Corner Rd Alt: +1 732.866.1602 Holmdel, NJ 07733-3030 http://qweb.ho.att.com/~jflood