[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 674
  • Last Modified:

Windows SP2 very slow in Netware 6.0 SP5 server

1. I have Netware 6.- SP5 and Windows XPSP2 client, I'm using Mas90 accounting system. The server is running Xeon 2.0 GHz with 1.0 GB RAM. The server and clients access is running good, but after few our client access and MAs90 program very very slow. To make thing faster i have to restart the netware server again.

2. How to configure my client to use only IP accessing the server, how to specify from the server side to use IP only not IPX

thanks
0
tropicmar
Asked:
tropicmar
  • 3
  • 2
1 Solution
 
umang505Commented:
2.Install Netware client Ver 4.9 sp2 using "custom" option and select "IP protocol only".

On the server side it is very easy .
Check for the line similar to
 "Load ce1000 int=x frame ethernet_802.2 name = abc"
"bind ipx to ce1000---"
remark the line beginning with " Bind ipx ...."

1.For Ques.1 please check ' number of files and buffers in the config.sys on Server's c: drive.(Dos Partition)
Best of luck
0
 
umang505Commented:
you can download and  install the latest client ver 4.91 also
http://download.novell.com/Download?buildid=2ss2JIYshRc~
Novell® Client™ v4.91 for Windows* 2000/XP is the latest Windows 2000/XP client software release available from Novell.
0
 
ShineOnCommented:
To expand on umang505's #2 answer - that way will work if you do not use inetcfg to configure networking.  A lot of people do, and although PsiCop hates it, it has a couple of good things like the "reinitialize system" command to reset your network configuration on-the-fly to whatever you changed it to.  If you don't use inetcfg and follow umang5095's directions, that will work going forward, but for immediate "gratification" you would also have to unbind IPX from the network card that IPX is bound to, using the unbind command.

If you have inetcfg, you unbind IPX from the card and turn IPX protocol off from inside inetcfg and then issue the "reinitialize system" command from the console prompt.

For question 1, it is possible that you are experiencing the NSS cache memory leak problem  Did you update your eDirectory to 8.7.3 also, in addition to the NetWare 6 Support Pack 5?  If so, you should check out this TID: http://support.novell.com/cgi-bin/search/searchtid.cgi?/10091980.htm
0
New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

 
tropicmarAuthor Commented:
To narrow the problem, i ask the user just to restart the workstation running windows xpsp2 with client 4.83sp3 and she said the computer work fine as far as the speed is concern. So she always have to restart client computer if she encounter a slow processing of her Mas90 program that is install to anetware 6 sp5 server.

thanks
0
 
ShineOnCommented:
So it's not the server that needs a reboot, but the client.  Ignore the NSS cache issue for this, then.
0
 
ShineOnCommented:
Is the Novell Client set for File Caching = off and File Commit = on?  Have unnecessary services been turned off in Windows XP?  Have you set a fixed-size swap file?  When was the last time this PC was defragmented?  Is Internet Explorer set to delete cache on close?  Is Windows Explorer's "Automatically search for network folders and printers" and "simple file sharing" settings unchecked? They should be...

My philosophy: The first thing to do when debugging Windows XP slowness is to turn off everything that isn't necessary for what you do - that includes the Windows Explorer settings I mentioned above, 'cause they're only good for a home environment.  The second thing is to check for spyware and trojans.  The third thing is defrag the hard drive.  The fourth is get rid of your Internet Explorer cache and make sure it stays clean.  Then, when you try to fix the actual problem, you know that those are not contributing factors, and can concentrate on the problem itself.

After you clean up Windows' act, download Process Explorer from sysinternals, so you can see all of the modules the MAS90 program uses.  It might be as simple as a bad DLL causing a memory leak, which would be my first guess, since a reboot clears it up for a while.

If it turns out the bad DLL is part of the Novell Client32 v 4.83sp3, updating the client to current might be the fixl.  It might be a MAS90 module, though.  You need to find out what is using up the PC's resources.

0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now