[[https://www.revelation.com/|Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community]]


==== Slow loading of OI (OpenInsight Specific) ====
=== At 03 JUN 1999 04:22:22PM Holly wrote: ===
 
{{tag>"OpenInsight Specific"}}
 
<QUOTE>
We have a new NT network running OI 3.6.



The first terminal loading OI takes about 10 seconds to load OI.  Subsequent terminals take approximately 56 seconds.  



Is there any way to speed this up?



Other NT networks load much quicker (eg 3-10 seconds).
</QUOTE>
----

=== At 03 JUN 1999 07:19PM Duane ALDATA} wrote:  ===

<QUOTE>Holly,



  We noticed a similar problem when we first switched from Novel to Windows NT.  Check your protocol stack for your network.  It seems that Windows NT doesn't handle IPX and OI very well.  TCP/IP seems to work much better.  The solution is to either remove IPX entirely from the client computers, or move it down in the protocol stack so that TCP/IP gets used first.  

  Note: this only seems to apply when using the NT Service.  If the Linear Hash service is turned off from the server, OI speeds up again.



     Duane

     ALDATA Software

     duanep@aldatasoftware.com

</QUOTE>

----

=== At 03 JUN 1999 08:10PM Don Bakke wrote:  ===

<QUOTE>We don't have that much experience with NT, but whenever OI has been slow to load on a network (like Novell) it's been because there were too many protocal bindings on too many adapters that weren't necessary. Once the excess baggage was removed everything starting humming again quite nicely.



dbakke@srpcs.com

[url=http://www.srpcs.com]SRP Computer Solutions[/url]

[img]http://www.srpcs.com/srpicon1.gif[/img]

</QUOTE>

----

=== At 04 JUN 1999 05:19PM Holly wrote:  ===

<QUOTE>Don and Duane



Many thanks for your helpful suggestions.



Unfortunately, I have little knowledge of NT and hence would appreciate a little help on how to implement your suggestions.



Thanks

</QUOTE>

----

=== At 08 JUN 1999 05:07PM Duane ALDATA wrote:  ===

<QUOTE>Holly,



    The easiest way to fix this problem is not actually related to NT at all.  If the network is using TCP/IP, simply remove all the IPX protocols from the clients (click on the "IPX -] 'your adapter name'" in the listbox, and then click on Remove).  You can find this in Network Properties on the individual machines.  Remove as many as you can.  You can find out what protocols you need on the network by going to the server(s) and finding out which protocols are listed in their network properties.  As long as the client and the server have one protocol in common, the machine will still find the network.



     Hope this helps

     

     Duane

     ALDATA Software

     duanep@aldatasoftware.com

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=497BF076AD622DA385256785006FE998|View this thread on the  forum...]]