Novell client loaded, WinXP, slow initial browse/load of Windows 2008R2 files

Posted on 2010-11-19
Last Modified: 2012-05-10
We are moving from a Novell 5.1 network to a Windows 2008R2 server.  Still need the novell server for a while.  Have the Novell Client 32 4.91 sp5 loaded (tried with IR1 also).  No problem with Windows7 machines.  However, on WindowsXP machines, if the machine is idle for even 5 minutes, when you click on My Computer/Windows Explorer, or Application File open dialog or tried to open a file, the display of files in explorer delays for about 45 seconds as well as when tryinig to open the file.  Then after that it is quick,unless you have another period of inactivity.  

Symantec's SEP is not a factor.  If I uninstall the Novell Client, then the problem goes away.  If I reinstall the client, the problem reappears.  Since I need access to the Novell Server for a while yet, what is the solution.

Question by:cwsoft05
  • 4
  • 3
  • 2
  • +2
LVL 30

Accepted Solution

pgm554 earned 167 total points
ID: 34180087
Check the binding order of the client on the XP machine(no ipx)and make sure you have SLP configures correctly.
LVL 66

Assisted Solution

johnb6767 earned 167 total points
ID: 34182117
Not only the Bindings, but also check to make sure that the Providers are in teh right order.... Microsoft Networks at the top, WebClient at the bottom.....Any Novell stuff in the middle....

Author Comment

ID: 34183284
There is typically ms ms file and print sharing. Ms net client. Ms terminal service. Synantec xxxx client. Novell client. Maybe ms web client. What is proper order. Win7 gas msfp. Msclient. Symantec or ms term next and netware last. Plea4ae clarify what specidfica"ly is best.
Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

LVL 30

Expert Comment

ID: 34183481
What is doing your DHCP,the Windows box?

Do you have an SLP (usually the ip address of the Netware box)provider in the in the DHCP scope configured?

Author Comment

ID: 34183659
Don't think I do. Win is doing dhcp. Netware was but I switched. I will chec0k that slp is configured on the netware box also. This is a 5.1 box
LVL 30

Expert Comment

ID: 34183884
SLP is how the NW client finds the NW box.If it can't see it ,it tries to multicast to find out what the resources are.
You could try putting in a static slp provider in the NW client and see if that fixes your issue.
You may be experiencing a hang because of this.
I remember this issue a very long time ago (2001)and am trying to remember the fix.

You might want to try this too:

Go int o the client properties, Protocol Preferences, for IP select just
SLP and NDS; then, still in the client properties, go into Advanced
Settings and change the Name Resolution timeout to 1 second from the
original 10.

Close Client settings, go into Control Panel -> Networking, then from
the Top menu Bar Go to Advanced -> Advanced Settings -> Provider Order.
Move the Microsoft Windows Network to the top, followed by the NetWare

LVL 30

Expert Comment

ID: 34183896
What's the MS spack on the XP boxes?

There was an issue with the mups.sys in earlier versions of XP.
LVL 17

Expert Comment

ID: 34184584
For us, the problem was with name resolution, NetWare looking up Windows server and vice versa.  

Check out this TID:

Specifically, scroll down to "solution 6".  It requires some registry editing, but it really did the trick for us.

Author Comment

ID: 34185047
service pack 3
LVL 66

Expert Comment

ID: 34185309

Post the contents of the txt file please.....

reg query "HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order" /s>np.txt
notepad np.txt

Open in new window

LVL 19

Assisted Solution

deroode earned 166 total points
ID: 34186135
The problem comes from having two network providers (MS client and Novell client) .

When the workstation starts looking for a server, whichever Network provider is configured first in the binding order (Control panel - Network connections -  Advanced - Advanced settings - Provider order) will go out on the network looking for the servername. When it finds the correct name and type server it will return quickly, but when it doesn't find the correct type server (e.g. the MS clients looking for a Netware servername) it will timeout after 45 seconds, and only then pass control to the other network provider.

When most of your servers are MS, you may want to configure the MS client first, but experience delays when accessing a Netware server.

The Badnameserver cache configuration mentioned by BudDurland works well, but only works with the Novell client, so this works best when the Novell client configured as first. You then would either configure a high timeout (a day) but have each windows server lookup experience a delay as the Novell client times out and places the server in the Bad name cache, or prepopulate the bad name cache.

Featured Post

Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
GPO not showing IE10 in GP Preferences 14 72
Application Crash 2 25
Clone Hype V Machine with ISCSI SAn storge 3 36
RDS licensing 2008 to 2016 9 53
We recently had an issue where out of nowhere, end users started indicating that their logins to our terminal server were just showing a "blank screen." After checking the usual suspects -- profiles, shell=explorer.exe in the registry, userinit.exe,…
New Windows 7 Installations take days for Windows-Updates to show up and install. This can easily be fixed. I have finally decided to write an article because this seems to get asked several times a day lately. This Article and the Links apply to…
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…

839 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question