What's the difference between... 1

[CodeDeficitDisorder]

What's the difference between a "Network Administrator" and a "System Administrator"?

 

[KenCunningham]

My twopennorth - a Network Admin administers things outwith the server environment, a sys admin those within it.

 

[CodeDeficitDisorder]

You mean, a Network Administrator works on Switches and Routers (not servers) and a System Administrator works on Servers (not switches/routers)?

 

[EBGreen]

I think it depends on the shop. I've seen shops where the system admin is a true admin and the network admins were glorified cable monkeys.

[red]"... isn't sanity really just a one trick pony anyway?! I mean, all you get is one trick, rational thinking, but when you are good and crazy, oooh, oooh, oooh, the sky is the limit!" - The Tick[/red]

 

[CodeDeficitDisorder]

So what are the main differences between the true network adminisrator and the true system administrator?

 

[rphips]

None, they are only words that mean the same thing.



bob

"ZOINKS !!!!!"

Shaggy

 

[RiverGuy]

Can a system exist without a network?

 

[EBGreen]

Can a network exist without a system?

What is the sound of one hand clapping?

If a network crashes and their is no admin to see it, does it really crash?

[red]"... isn't sanity really just a one trick pony anyway?! I mean, all you get is one trick, rational thinking, but when you are good and crazy, oooh, oooh, oooh, the sky is the limit!" - The Tick[/red]

 

[CajunCenturion]

It all depends on how do you define system.
Where do you place the boundaries of the network?

Good Luck
--------------
To get the most from your Tek-Tips experience, please read FAQ181-2886
As a circle of light increases so does the circumference of darkness around it. - Albert Einstein

 

[RiverGuy]

Where do you place the boundaries of the network?

That is very true. If you had a mainframe with a few dumb terminals attached to it, in the same room, I doubt one would consider it a network. Therefore, a "Network Admin" title wouldn't be appropriate, but a "System Admin" would. However, if one had a few dumb terminals attached in other offices, would it be considered a network? Maybe.

 

[CodeDeficitDisorder]

I guess I just don't know what to put on my resume for future jobs. I've been working the help desk since 2000, and I want to go the next step.

 

[RiverGuy]

Are you talking about to put what your goals are? This is a really good option, but go to some place like salary.com and look up the job descriptions for each. See what you like best.

 

[screwloose]

A system admin is responsible for the server itself. Installing, upgrading, maintaining the operating system, user maintenance, security on the server, documenting the system, monitor system activity, etc.

A network administrator is responsible for the LAN/WAN: switches; routers; hubs, etc. If a new server is installed, the network admin is the one who assigns and IP or subnets a network. They will monitor the network for performance and use sniffers to trace activity. They are also responsible for security outside of the server. Firewalls may or may not be included on this team depending on the company setup.

At my last job (Fortune 500) the system/network admins were completely separate, and are separate in my current job too. In a smaller company they will be the same because a company won’t/can’t afford two salaries.

Even if you work in a large environment though, a system administrator should have knowledge of networking. Though I have worked with other sys admins who take the opinion that networking is someone else’s job so, therefore, they don’t need to know it – and don’t. But again, it is good to know.

 

[CodeDeficitDisorder]

Thanks for the replies. It seems to make sense now. I'll probably go System Admin.

 

[willir]

Often times, the two "tasks" share areas of responsibilities. As a Network Admin, I was responsbile for System Admin. As a System Admin, I was also responsible for Network Admin. But ScrewLoose is correct in that in larger companys, these tasks are separate responsibilities.

To be a good System Admin, it helps to have a strong grasp on the network administration, and vice versa. This helps you trouble shoot, isolate problems and resolve issues. Moreover, when you design a server or intergrated server design, you have to have a strong graps on the network topology. To design a superior network, you have to understand the purpose and functionality of the servers, databases and end user requriements.