Internet connection sharing - Norton, server, workstations

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am ready to share an internet connection for my small office network. The
DSL is going into the PC which is serving as my server via USB. The "server"
is connected to the office network via ethernet. Will running Norton Internet
Security 2004 on the "server" protect the whole network?

Thanks very much for your help!
 
On Sat, 11 Sep 2004 09:55:04 -0700, "Kirk Bogle" <Kirk
I am ready to share an internet connection for my small office network. The
DSL is going into the PC which is serving as my server via USB. The "server"
is connected to the office network via ethernet. Will running Norton Internet
Security 2004 on the "server" protect the whole network?

Thanks very much for your help!

Kirk,

Running NIS on the "server" will protect the whole network from network based
threats. NIS also claims to protect you against content based threats such as
email and scripting based malware, but please don't make it your only defense.
Make it your outermost layer, in a layered defense. Each layer is necessary
because no layer produces complete protection.

A NAT router passes only requested traffic, back to the computer that requested
it. It won't selectively block traffic from known hostile addresses, nor
selectively filter bad protocols or programs.

See <http://www.firewall-software.com/firewall_faqs/what_is_a_firewall.html>

One NAT router protects your entire LAN. Your "server", with NIS protecting it,
provides that functionality.

The second layer is a software firewall on each client computer. You need a
software firewall on each computer in your LAN; in case one computer gets
infected, a software firewall on the others could save you a lot of trouble.

The third layer is good software, also on each computer. This layer has
multiple components.

AntiVirus protection. Realtime, plus a regularly scheduled virus scan.
Regularly updated. AV protection is not all that's needed today.

Adware / spyware protection. Realtime, plus a regularly run adware / spyware
scan. Regularly updated.
Complete instructions, using Spybot S&D and HijackThis (both free) are here:
<http://forums.spywareinfo.com/index.php?showtopic=227>.

Harden your browser. There are various websites which will check for
vulnerabilities, here are three which I use.
http://www.jasons-toolbox.com/BrowserSecurity/
http://bcheck.scanit.be/bcheck/
https://testzone.secunia.com/browser_checker/

Block Internet Explorer ActiveX scripting from hostile websites (Restricted
Zone).
<https://netfiles.uiuc.edu/ehowes/www/main.htm> (IE-SpyAd)

Block known dangerous scripts from installing.
<http://www.javacoolsoftware.com/spywareblaster.html>

Block known spyware from installing.
<http://www.javacoolsoftware.com/spywareguard.html>

Make sure that the spyware detection / protection products that you use are
reliable:
http://www.spywarewarrior.com/rogue_anti-spyware.htm

Harden your operating system. Check at least monthly for security updates.
http://windowsupdate.microsoft.com/

Block possibly dangerous websites with a Hosts file. Three Hosts file sources I
use:
http://www.accs-net.com/hosts/get_hosts.html
http://www.mvps.org/winhelp2002/hosts.htm
(The third is included, and updated, with Spybot (see above)).

Maintain your Hosts file (merge / eliminate duplicate entries) with:
eDexter <http://www.accs-net.com/hosts/get_hosts.html>
Hostess <http://accs-net.com/hostess/>

Secure your operating system, and applications. Don't use, or leave activated,
any accounts with names or passwords with trivial (guessable) values. Don't use
an account with administrative authority, except when you're intentionally doing
administrative tasks.

The fourth layer is common sense. Yours. Don't install software based upon
advice from unknown sources. Don't install free software, without researching
it carefully. Don't open email unless you know who it's from, and how and why
it was sent.

The fifth layer is education. Know what the risks are. Stay informed. Read
Usenet, and various web pages that discuss security problems. Check the logs
from the other layers regularly, look for things that don't belong, and take
action when necessary.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top