Re: Newbie Questions

That's great information! Thanks!

I just love computers. At work I was put in charge of Win2K and Citrix
administration. Nothing fancy. Stuff like joining domains, resetting
passwords, etc. But the higher end stuff like switches, routers, etc.
they didn't want to tell me about.

I think it was after I found a security hole in the company's software.
They told me that it was "insignificant" and got mad at me. Then they
went and fixed it. After that they just got hush hush about a lot of
things when it came to me.

One day the network admin. decided to play a prank on me. He used the
@command to schedule net send messages to me. I shut down my messenger
service, and then placed an internet file in his start up folder.
Whenever his computer started it went to a gay porn site. (Mind you, he
had issued the prank challenege to begin with), Well, after that it was
all out paranoia. I came in to work one day to find a fellow technician
combing through all my files. He said the net admin told him to because
they thought I was doing something illegal.
Moe Trin wrote:
On 28 Jun 2006, in the Usenet newsgroup comp.os.linux.networking, in article
<1151524465.975589.143660@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, nick wrote:

Geoff wrote:

Davide Bianchi wrote

With 50/100 machines you're gonna need more than one.

And you forgot one basic element, one that you can't get away without:
YOU NEED A SYSADMIN, one that can make all that junk run, and keep your
'network' running.

yeah totaly
if you have this amount of machines, you NEED to employee someone who knows
what they are doing

Don't misunderstand...I'm not doing this myself. I've just always been
curious. The IT guys at work are hush hush about everything.

If you had to put up with the questions they get, you'd be hush-hush too.

I see a router. I see switches. But no one explains.

Is there some compelling need to know? Nope. You should probably start
with the HOWTOs - and then graduate to the "Linux Network Administrator's
Guide" (from the LDP).

I assume that the router connects to the switch. They have like five
switches with 16 or so ethernet ports. They also have a Cyberguard
firewall, I think it is.

Sounds plausible.

So the firewall just firewalls, and the router does NAT, etc. right?

"That depends". The router could be just connecting to another medium
that connects to the upstream, and the firewall is doing NAT. There
are several ways to do things.

Now onto the proxy server, is there a certain point in a company's size
when they REALLY need the proxy server?

Another great big "that depends". You might use a proxy server to act as
a filtering gateway for your employees to reach the net - filtering meaning
that pr0n sites and other things that expose the company to lawsuits are
not accessible (or this could be implemented by _written_policies_ and
firewall rules, or just the policies and threat of instant dismissal
alone). We run a combination of the two. The company's public facing
servers (mail, web, ftp, and maybe DNS) would be better located at some
bandwidth provider's location or a colo, for security, reliability and
speed.

Setting up a company network is not a 'follow the recipe' type of thing,
as one size definitely does NOT fit all. It strongly depends on what
the network is for, how secure it needs to be, what access to/from the
world is needed/desired/allowable. And it's not set up on the whim of
a sysadmin, or the company president - who probably would be hard pressed
to choose between AOL and the local cable service provider (which probably
wouldn't present a good image to the public). Likewise, if there is ANY form
of Internet access, there must be written policies in place BEFORE the
hardware is ordered, not after a disgruntled ex-employee takes the
company to the cleaners over a sexual harassment lawsuit. That also means
running those policies past the official company legal-weasel and getting
his/her blessings.

Old guy

.

Relevant Pages

  • Re: The Hard Problem for Behaviorists
    ... correct low level abstractions to define the operation of the brain with - ... Do you not know how computers work? ... you can think of this type of network like you ... when you drop a marble in hole X1, ...
    (sci.cognitive)
  • Re: Networks : Workgroups and Domains. How Do I Use Them?
    ... I think the problem is from my lack of understanding whether these machines are together as a workgroup or domain. ... If I want to configure solely for a workgroup network, then I would think I do not need to provide a domain name, and vice versa for a domain network. ... It's not clear whether any of your computers is running Windows 2000 *Server.* If not, you don't have a "domain" and shouldn't be using domain names. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall or overlooked firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ...
    (microsoft.public.windowsxp.network_web)
  • Re: {workgroup}"...is not accessible" after removing NWLINK
    ... I generally reboot the machine whenever I make network ... >problem is a browse service that won?t run on the XP machine using the TCP/IP ... >?The browser has forced an election on network ... >> computer, and one, or preferably two, of the Windows 98 computers. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Help with 070-217
    ... The network contains 25,000 computers. ... > single Windows 2000 domain named research.contoso.com. ... > Server computers that are configured as domain controllers. ...
    (microsoft.public.cert.exam.mcse)
  • RE: Help with 070-217
    ... The network contains 25,000 computers. ... > single Windows 2000 domain named research.contoso.com. ... > Server computers that are configured as domain controllers. ...
    (microsoft.public.cert.exam.mcse)