WOW!
That's a bunch. Will do.
Thanks heaps.
Pete


>Hi,
>
> The weathers nice here at present, 20-30C, just a few more things to look at, apply them one at a time and test, hopefully by the end we will have found what was causing it.
>
> A lot of these problems are caused by timeouts etc.
>
>1. Optimize The Redirectors on the PC
>If unused directors are installed on a PC or rarely used directors are configured with a high preference, you will see degraded performance. Common redirectors are the MS Client for Microsoft Networks, Novell Client 32, and various NFS clients.
>
> If any of these clients are not needed, they should be removed. If they are needed, make sure to only bind the necessary protocols. A client with only IPX bound to the Novell client and IP to the Microsoft and NFS clients may be significantly faster in accessing network resources than one which has IP and IPX bound to the Novell client, IP, IPX, and Netbios to the MS client due to the unneeded searches performed by the MUP.SYS. Also be sure to make the most used redirectors the primary redirectors.
>
>To do this under Win2000 -
> Select Properties of "My Network Places", then Advanced - Advanced Settings from the menu. In the Pop Up window that appears, select the "Provider Order" tab.
>
>The protocol bindings to each redirector should also be optimized. Within the Network Control Panel, select the bindings tab and move the most used protocol for each redirector to the top.
>
>If running Windows2000 with the Novell Client, it is recommended to place the Microsoft Redirector first if MS browsing speed is important.
>
>2. Disable DFS Support if not used.
>
>DFS is a feature of NT which allows multiple physical file systems to be logically grafted together to appear as a singe directory structure. This can ease the difficulties of users locating resources across many different servers.
>
>The first step in locating a server via UNC is to check to see if it is DFS. This Disabling DFS support will cause this step to be skipped. To disable DFS, create the DisableDFS registry entry (DWORD with a value of 1) at HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Mup\
>
>(Note: Even when Client32 is set a the primary redirector, NT will still do an initial Netbios query to test to see if the UNC path is a DFS directory. Therefore, it is highly recommended that this be disabled in Netware environments that do not use DFS.)
>
>3. Disable Remote Computer Task Scheduler - By default, Win2000 will attempt to access the remote scheduler service on remote computers such as Win95, Win98, and Novell Netware. This can cause long delays of over 30 seconds while futilely attempting to access the remote service. This was scheduled to be fixed in SP2, but was not. Use the Registry File below to delete this key, which will disable this feature.
>
>Windows Registry Editor Version 5.00
>[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\RemoteComputer\NameSpace\{D6277990-4C6A-11CF-8D87-00AA0060F5BF}]
>
>http://support.microsoft.com/support/kb/articles/Q245/8/00.asp
>
>4. Install the Client IPX ONLY - Do Not USE IP and IPX
>
>By Default, the Novell client will install in IPX an IP mode with IP as the preferred protocol. This means that if you attempt to locate a server, it will first attempt to locate it via IP before it attempts to locate it via IPX. If the server is not a NW5 server running IP, there will be an added delay before the server is located. It is recommended to run the client as IPX only until all or nearly all servers are upgraded to NW5 to support native IP. At this point workstations can be converted to IP only.
>(Note: Under Some Conditions, the Novell Client will install IP support even when IPX Only is selected. Be sure to disable all IP resolution methods under protocol preferences if they exist and you operate in an IPX only Netware environment.)
>
>5. Disable Unused protocol Search Methods
>
>By default, the Novell client will attempt to use many different resolution methods for IP that may not be configured for use on your network. Under the "Protocol Preferences" tab of the Novell Client configuration, disable all resolution methods not used. I normally disable Host File, DNS, and DHCP DNS. I leave NDS and SLP enabled. If SLP is not setup on the servers and configured on the clients, disable this resolution method also.
>(Note: Under Some Conditions, the Novell Client will install IP support even when IPX Only is selected. Be sure to disable all IP resolution methods under protocol preferences if they exist and you operate in an IPX only Netware environment.)
>
>6. Enable/Disable Packet Burst
>
>IPX communication originally was designed in which the sender sent a single packet to the receiver and waited for a response before sending a second packet. Packet bursting was developed to allow the sender to send multiple packets before needing a response to send additional packets. Normally this greatly enhances performance. Some cards, however, do not handle this well and drop a large number of packets. This causes a significant performance drop. Disabling packet bursting can improve performance in these cases. If disabling packet bursting increases performance, new NIC drivers or a new LAN card is recommended. ( Packet Bursting frequently causes performance problems in Win2K. Disabling it will normally improve performance.)
>
>7. Tweak Novell's Name Resolution Timeout
>
>Under the advanced settings tab of the Novell Client, change the Name Resolution Timout to 1 from 10. This setting can be pushed via the following registry entry -
>(HKLM\SOFTWARE\Novell\NetwareWorkstation\Policies\Network
>Timeout in Seconds=1)
>
>8. Install Novell Client 4.8 w/patches
>
>Novell officially released client 4.8 on Sept. 1, 2000. This client tends to be much faster than previous clients. This is especially true for Windows2000 clients. There is also a few patches that can help quite a bit.
>
>NWFS.sys patch available for the 4.8 client that will help reduce UNC delays. - 234860a.exe
>
>Another patch prevents unnecessary printer connections during application starts, printer installs, and print operations - 264514.exe
>
>Another patch to resolve some high processor utilization related to the Spooler service (Instead of applying patch, rename file). - 253829.exe
>
>A service pack is also available for the 4.8 Client ( 48sp3.exe ), but there have been some issues with the NWFS.SYS file in this patch. If SP3 is installed, I would recommend backdating to the NWFS.SYS patch listed above. IPCOST.EXE is another important patch if the 4.8sp3 patch is applied. NEVER apply ipcost.exe to 4.8 w/o SP3.
>
>9. Don,t forget the setting the redirector to Novell. I sent it to you previously.
>
>
>Regards