Slow connectivity to NT4/7.30
Hi, I'm having connectivity probs from Win95 client to NT4 (SP3) running IDS 7.30. The response is like 15 secs for each new connection. Specs: 1 CPU, 256MB RAM, db on NTFS, swap=64K Tested using ilogin demo on server - response of 1-2 secs. Tested using ilogin on client - response of 15-20 secs. App developers can connect to server but initial connection is always slow, compared to subsequent connections (probably the connection is already established). Appreciate any assistance. Thank you. -----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
We had exactly the same problem, and we solved it like this: 1.) Disable the the DHCP Protocol (there is a bug with IDS on NT with the DHCP protocol: the connection can take up to 6 to 8 seconds) on both the server (NT) and on the clients (95 and 98 PC's). 2.) Make the Clients (95 and 98 PC's) use static IP adresses instead of dynamic IP adresses (provided by the DHCP server). 3.) Disable DNS on the NT Server. 4.) Create a C:\\WINDOWS\\HOSTS file on the clients, with the IP adress and name of the NT Server (aaa.bbb.ccc.ddd server server.domain.com) 5.) On the IP properties of the Clients, set the NT server as the gateway. 6.) On the client PC's set INFORMIXSQLHOSTS to blank (if using Windows 95) or to \\\\NAME_OF_THE_PC (if using Windows 98). 7.) On the client PC's, after setting the values in SETNET32, run REGCOPY.EXE (in the %INFORMIXDIR%\\bin directory) Connection time is now 1 to 2 seconds... :-) Vitorino Ribeiro SINFIC - Sistemas de Informa''o Industriais e Consultoria, S.A. sinfic@esoterica.pt williamkcwong@yahoo.com wrote in message <7d8pec$bfe$1@nnrp1.dejanews.com>... >Hi, > >I'm having connectivity probs from Win95 client to NT4 (SP3) running >IDS 7.30. The response is like 15 secs for each new connection. >Specs: >1 CPU, 256MB RAM, db on NTFS, swap=64K > >Tested using ilogin demo on server - response of 1-2 secs. >Tested using ilogin on client - response of 15-20 secs. >App developers can connect to server but initial connection is always >slow, compared to subsequent connections (probably the connection is >already established). > >Appreciate any assistance. Thank you. > >-----------== Posted via Deja News, The Discussion Network ==---------- >http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
Dear Jose, Thank you for your solution. There wasn't any WINS setup but I did removed the DNS servers that were configured on the NT server. It is now 4-5 secs instead of 55 secs ! Is this problem fixed on SP4 ? (otherwise i'll have to hardcode IP addresses everywhere !) Thank you. In article <7d92pj$htb$1@duke.telepac.pt>, "Jos' Vitorino Barata Ribeiro" <jribeiro@mail.telepac.pt> wrote: > We had exactly the same problem, and we solved it like this: > > 1.) Disable the the DHCP Protocol (there is a bug with IDS on NT with > the DHCP protocol: the connection can take up to 6 to 8 seconds) on both the > server (NT) and on the clients (95 and 98 PC's). > 2.) Make the Clients (95 and 98 PC's) use static IP adresses instead of > dynamic IP adresses (provided by the DHCP server). > 3.) Disable DNS on the NT Server. > 4.) Create a C:\\WINDOWS\\HOSTS file on the clients, with the IP adress > and name of the NT Server (aaa.bbb.ccc.ddd server server.domain.com) > 5.) On the IP properties of the Clients, set the NT server as the > gateway. > 6.) On the client PC's set INFORMIXSQLHOSTS to blank (if using Windows > 95) or to \\\\NAME_OF_THE_PC (if using Windows 98). > 7.) On the client PC's, after setting the values in SETNET32, run > REGCOPY.EXE (in the %INFORMIXDIR%\\bin directory) > > Connection time is now 1 to 2 seconds... :-) > > Vitorino Ribeiro > SINFIC - Sistemas de Informa''o Industriais e Consultoria, S.A. > sinfic@esoterica.pt > > williamkcwong@yahoo.com wrote in message > <7d8pec$bfe$1@nnrp1.dejanews.com>... > >Hi, > > > >I'm having connectivity probs from Win95 client to NT4 (SP3) running > >IDS 7.30. The response is like 15 secs for each new connection. > >Specs: > >1 CPU, 256MB RAM, db on NTFS, swap=64K > > > >Tested using ilogin demo on server - response of 1-2 secs. > >Tested using ilogin on client - response of 15-20 secs. > >App developers can connect to server but initial connection is always > >slow, compared to subsequent connections (probably the connection is > >already established). > > > >Appreciate any assistance. Thank you. > > > >-----------== Posted via Deja News, The Discussion Network ==---------- > >http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own > > -----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
We had the problem on both SP3 and SP4... It seems to be a Informix problem... If you have access to the Product Defect Query at the Informix Techinfo Center (http://www.informix.com/informix/services/ilink/kb/kb_table.html) search for DHCP and look for Defect 102690 Vitorino Ribeiro SINFIC - Sistemas de Informa''o Industriais e Consultoria, S.A. sinfic@esoterica.pt williamkcwong@yahoo.com wrote in message <7dbasd$i8r$1@nnrp1.dejanews.com>... >Dear Jose, > >Thank you for your solution. There wasn't any WINS setup but I did removed >the DNS servers that were configured on the NT server. It is now 4-5 secs >instead of 55 secs ! Is this problem fixed on SP4 ? (otherwise i'll have to >hardcode IP addresses everywhere !) Thank you. > >
williamkcwong@yahoo.com wrote: > Dear Jose, > > Thank you for your solution. There wasn't any WINS setup but I did removed > the DNS servers that were configured on the NT server. It is now 4-5 secs > instead of 55 secs ! Is this problem fixed on SP4 ? (otherwise i'll have to > hardcode IP addresses everywhere !) Thank you. I've noticed that NT DNS has severe problems resolving reverse-IPs. If you have to use MS DNS, you might try creating static entries for all DHCP IP addresses (forward /and/ reverse). This way, the ip->name->ip cycle will match quickly. -Richard