Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

File Lock Capacity - Windows 2003 server

Status
Not open for further replies.

crabilll

IS-IT--Management
Sep 27, 2006
9
US
I am running MMS Generations, an application for school districts (a student information system) which uses Foxpro. We have a Novell network but run this application on a Windows 2003 server because of certain add-ins with the product. This application has been running very slow on our network and I researched some information but I can't find where to make the setting change. One suggestion is to increase the numbers of file lock capacity but I don't know where to go to do this. Does anyone know?

Or any other suggestions to change to possibly speed up program performance over the network.

Thanks!
 
I just did the same thing. My experience is that Windows is not as fast of a file server as Novell. Novell does a better job of caching files and delivering them to workstations from cahche rather than off the server hard disk.

Also not that you need to turn off OpLocks on the server and the workstation. Look on the Microsoft web site for Oplokcs and you will find a doc or two that tells you what you need to change in the registry. This will probably not help your speed, but it will cut down on the possibility of file corruption.

All that said, I didn't notice much of a speed change at all when moving from Novell to Windows 2003. I suspect that your problem may be related to how hard the server is working with these extra "add-ins" you referred to or the network card, the CPU, the RAM, the switch or router, antivirus software on the clients (configure it to exclude the folders the Foxpro app and data is in)? Any one of these could be the source of your problem.

Bill
 
I should have proofread this first. Let me try again with paragraph 2.

Also note that you need to turn off OpLocks on the server and the workstation. Look on the Microsoft web site for Oplocks and you will find a doc or two that tells you what you need to change in the registry. This will probably not help your speed problem, but it will cut down on the possibility of file corruption.
 
PS - If I remember correctly the Maximum Files Locks setting is for Novell not Windows - but I could be wrong.
 
wtotten is correct, the max file locks is a Netware server setting


All you need in this life is ignorance and confidence; then success is sure.
- Mark Twain
 
I will definitely try the Opslock and see what happens. I did find that if I disable "Scan Network Drives" in Auto-Protect of Norton AntiVirus it speeds it up too but I don't think that is too safe. So, I tried File caching with NAV on our MMS server and it is okay so far. Thanks for your info.
 
I do have "Scan network Drives" turned off. If you want to leave it on, exclude the following file types:
DBF
CDX
FPT
SCX
SCT
FRX
FRM
IDX
PJT


Those are the main file types FoxPro uses.
 
I actually have a question about that (San Network Drives). Do you know what that directly affects by having that disabled (unchecked)? I told my boss (our Network Administrator) that I disabled that and he said that he wants it on because of the chance of getting a virus on that server. I figured that NAV Auto-Protect is still running on the server itself and NAV is running at the workstation level. So, I guess I am basically asking if it is save to have that turned off?

Also, I did put those files in as an exception in NAV but that didn't seem to make a difference. The disabling of Scan Network drives did make a difference in program performance but my boss wants it checked.

Thanks!
 
If you enter those file extensions but still have "scan network drives" disabled, then the file extensions, for files on network drives, is a moot point. However, if you enabled the network scan option, then I expect that the file exclusions will help keep the speed up.

FWIW - My philosphy on the network scanning is this;
If I have:
AV on the clients and the user can't disable it.
AV on the servers including Excahnge and so on.

Then I disable the network scan option. You could enable the client-side firewall in XP if someone is concerned about an outbreak across the network.

Bill
 
If you've got server side AV (that is regularly updated) then there is no point in having the Scan Network Drives switched on at the client. Unless, of course, there are different AV engines running on the server and the client.
 
If you have the option available in NAV and your AV options are locked so that the users can't change or disable them, you can also have one way file scanning set on your servers (we use outgoing) as long as you have two way file scanning on your clients and your cliens are set to scan floppy and removable disks. We find the one way file scanning on the servers noticebly speeds things up.

Sorry, we use CA eTrust InoculateIT so I don't know if you have the option in NAV.

Cheers.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top