The problem is twofold: it's as slow as molasses, and sucks CPU cycles like crazy. I seem to recall that we used to have to run some SHARE configuration options even to make this stuff work on a 286. Oh well, I much prefer Bill G anyway. MCSE-NT4.0, MCP-WIN2K
1) Check that you have the current driver for FastTrak100 (current dated March 2002). I've had good success with this controller. It is capable of RAID 0 (striped) or RAID 1 (mirrored).
2) Used matched drives whenever possible; use performance matched drives if exact brand-matched drives are not...
Correct. It is not technically RAID, as nothing is 'redundant'. RAID 0 is nothing more than a stripe set. If one disk goes down, everything is lost. Yes, a stripe set can have more than one partition.
If the system is listing the drives separately in Explorer, that means the stripe set is no longer functioning. This is not good news (unless you actually had a Mirror and not a stripe set), in which case you should be able to boot the working drive.
The best tool set I know comes from Winternals.com. You can boot into a command line version of NT/Win2k using modified setup diskettes. Replace files to your heart's content.
At this point, use the Device Manager to verify that the FastTrak driver is loaded, check to see if the hard drives are listed. Use Disk Management to see whether a drive letter is assigned to the stripe set.
The following service pack is compatible with Small Business Server:
Microsoft Exchange 5.0 Service Pack 2
The following service packs and updates are compatible with Small Business Server, but may require additional information:
Microsoft SQL 6.5 Service Pack 5
Microsoft Proxy Server...
This is true only as long as there is a possibility that the user might return, or specific files that the user owns have not been transferred to another user.
The reason is that the user ID is not stored in plain text, but rather an encrypted security ID (SID) is created when the user account...
This is probably due to Media management; the Backup program is not managing the media. I resolved this by manually running each new tape, naming it, and backing up 1 small file. Then I ran the scheduled backup, selecting the appropriate tape. It's worked fine ever since.
Thot: Take a look at the network packet sizes. Win2k assumes a packet size (TCP/IP) of 8k where NT4 assumed a size of 4k. Certainly in mixed environments, I've seen this to be an issue, and forcing the Win2k box down improved performance considerably.
Win2k defaults to DNS vs. WINS name resolution. If DNS is not running (and it often is not used on NT4 domains) it will definitely slow down the name resolution process. Also check the time required to actually copy a file of >30MB to see how the network performs once name resolution is...
Did you create the policy using a Windows 98 workstation and running a Windows 98 Policy Editor? Policies must be created within the intended OS, then copied to the NT server.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.