12 replies
by jacky chin
by ctl
by mckaytech
You haven't told us about how your network is set up but my best guess would be that your database is living on an underpowered server. With 12 workstations, if the database is not living on its own box, I would expect this kind of slowness.
However, you said you are also getting disk and network errors. That's a whole 'nother issue. If you could re-post with the specific errors you're seeing, it is likely that you'll get a better answer. One possibility is that one of the workstations on your network has a jabbering NIC so everybody else has to try and get their packets in through the noise. That alone could explain the slowness because each workstation could be sending each packet ten times or more to get one good one.
regards!
paul
by ctl
by rtab
First of all:
be sure that your network equipment works properly, you have not a lot of collision and so on.
Next check that your server is optimized for Network file sharing (see Control panel/Network/Services/Server);
Next:
- Open "Control Panel/Network/Bindings" tab;
- Select "Show bindings for: all services";
- Expand services tree below;
- Select "NetBEUI protocol" and press "Move Up" button (NetBEUI must be binded before WINS);
- Do it for "NetBOIS interface", "Server" and "Workstation" services.
by ctl
by ryank
I would try several of the following.
You can continue using NetBEUI and get better work performace if you move your network to a switching device. While NetBEUI is not routable at layer3 (OSI model) the data packets can still be manipulated at layer2 by a switch. This will help to reduce traffic on your network and speed it up a little but moving to IP would be recommended if you plan to keep this business growing well into the future and also performance wise. Setting up IP would actually be fairly simple, just use 255.255.255.0 as your subnet mask and then use 10.0.0.20 through 10.0.0.32 as the IPs for copmuters and if your printers are networkable (have JetDirect cards or the like, not simply shared off of a PC) give them IPs of 10.0.0.5 through 10.0.0.8.
Also, what kind of system is the access database on? Could faster DiskIO improve this situation (on the machine hosting the DB file). I would look at possibly cheap SCSI disk RAID or even IDE RAID solutions to help with the DB preformance
by ctl
by pan 13 x
one problem that is have seen with data bases is that the access data base is on a different partion , so you can add an addition swap file to that partition. if you need directions email me.
pan 13x@aol.com
other thing you may want to check is look at where the server service in the control panel /network select the service tab. Using netbeui as a protocol it maybe defaulted to there. if not change it there and reboot. the only other one i could see working is maximize troughput for network applications because the software for access may do its own caching.
by ctl
by trmcdougle
The other answers cover network problems, which seems likely with the disk/network errors that you mentioned.
You might also want to look at removing FindFast if it got installed (assuming you use Office 2000).
Alternatively splitting the front-end and data apart in the database and putting the front end on the clients would reduce start-up times. There may also be some bad design in the front end causing more work at start-up than is realy needed.
by ctl
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending