Solved

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

Posted on 2010-11-19
11
1,450 Views
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.

0
Comment
Question by:cwsoft05
  • 4
  • 3
  • 2
  • +2
11 Comments
 
LVL 30

Accepted Solution

by:
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.
0
 
LVL 66

Assisted Solution

by:johnb6767
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....
0
 

Author Comment

by:cwsoft05
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.
0
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

by:pgm554
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?

http://support.microsoft.com/kb/285019
0
 

Author Comment

by:cwsoft05
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
0
 
LVL 30

Expert Comment

by:pgm554
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
Services.

0
 
LVL 30

Expert Comment

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

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

Expert Comment

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

Check out this TID: http://www.novell.com/support/viewContent.do?externalId=7004092&sliceId=1

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

Author Comment

by:cwsoft05
ID: 34185047
service pack 3
0
 
LVL 66

Expert Comment

by:johnb6767
ID: 34185309
start>run>cmd

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


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

Open in new window

0
 
LVL 19

Assisted Solution

by:deroode
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.
0

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

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

I have been working as System Administrators since 2003. I recently started working as a FreeLancer and was amazed to find out that very few people are taking full advantage of their Windows Server Machines. Microsoft Windows Server comes with so…
Redirected folders in a windows domain can be quite useful for a number of reasons, one of them being that with redirected application data, you can give users more seamless experience when logging into different workstations.  For example, if a use…
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…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

772 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