Archives
What's New
Site Map
Subscriptions

Home
NetFlash
This Week
Forums
Reviews/buyer's guides
Net Resources
Industry/Stocks
Careers
Seminars and Events
Product Demos/Evals
Audio Primers

IntraNet


Error 404--Not Found

Error 404--Not Found

From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:

10.4.5 404 Not Found

The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.


















For more info:

Dunkelberger is a Microsoft Certified Systems Engineer and Microsoft Certified Trainer. His firm, Intelligent Information Systems, Inc., provides corporate network consulting and training services and builds Web sites. He can be reached at jeff@i-squared.com.

Back to the IntraNet index page


What does it take?

Quota Manager runs on any NT Server Version 3.51 or later machine. Installing Quota Manager is simple - it took us about five minutes both times we tried. The setup is fast. After that, it takes a little while to set up your quota, and you're all set.

Quota Manager runs as a background NT service and is active only when processing changes that occur to the size of quota-restricted areas.

The installation process starts by creating a user account that the Quota Manager service uses to log on. You also must create a local group to contain the users subject to quotas.

Next, you must add users to this new group so the quotas will affect them. It is best here to add users as a global group, such as Domain Users, to take full advantage of NT's security model, although you can add single users if you wish. The end result is that Quota Manager will enforce quotas on any user who is a part of this group. Any users outside the group will not be affected by the quotas.

After this, the setup program to install the service is run on the server on which the quotas will be set. The service install needs to be done on each server on which quotas will take effect. The setup program asks for the user name and group you created, and for an administrative account to which messages about the quotas are sent.

The final step is installing the administrative tool on the administrator's desktop and the inquiry tools on any user's Windows NT or 95, or Windows for Workgroups 3.11 machines.

These are difficult days for intranet administrators rushing to keep pace with the changing face of corporate Webs, and any truly useful tools to ease this burden are always welcome. NTP Software's Quota Manager is one of these. Even whispers from Microsoft that quota management will be included in NT 5.0 won't eliminate the current need intranet administrators have for Quota Manager.


Feedback | Network World, Inc. | Sponsor Index
Marketplace Index | How to Advertise | Copyright

Home | NetFlash | This Week | Industry/Stocks
Buyer's Guides/Tests | Net Resources | Opinions | Careers
Seminars & Events | Product Demos/Info
Audio Primers | IntraNet