Subject: Websites
From: scot <scot -at- HCI -dot- COM -dot- AU>
Date: Fri, 26 Apr 1996 10:02:09 +1000

> I'm doing research for my company, which is thinking of putting stuff for
> its employees on the Web -- stuff like sick leave policies, where the
> company picnic is this year, etc. We don't want employees surfing for Hot
> Cyberbabes or whatever else they are interested in outside of work, and we
> don't want non-employees reading our corporate policies (and crashing the
> picnic).

Sounds like you need a thing called a "firewall", as well as a web server.
It is possible to quarantine a network from the outside getting in and vice
versa. This can even be done only for certain 'port numbers'. TCP/IP
services usually have standard port numbers they use to communicate with
each other, this is how one machine can talk web/ftp/email/X to many
machines at once. For example, standard numbers are web on port 80 and smtp
(email) on 25. The firewall can block access according to a sophisticated
set of rules (based on things like, the originating address, the destination
address, the port number, etc) that will allow you to have for example,
direct email services but no web access.

Talk to your network techies and/or local security products vendor for more

#include HCI Consulting, Sydney, AU
#include std.disclaimer.

Post Message: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Get Commands: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "help" in body.
Unsubscribe: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "signoff TECHWR-L"
Listowner: ejray -at- ionet -dot- net

Previous by Author: what's in a name?
Next by Author: More on WWW graphics
Previous by Thread: Re: Websites
Next by Thread:

What this post helpful? Share it with friends and colleagues:

Sponsored Ads

Sponsored Ads