System Admin
System Admin
System Admin
Q: What are main Email Servers and which are their ports?
A: Email servers can be of two types:
Incoming Mail Server (POP3, IMAP, HTTP)
The incoming mail server is the server associated with an
email address account. There cannot be more than one incoming
mail server for an email account. In order to download your
emails, you must have the correct settings configured in your
email client program.
Introduction
Network Administration is a field that has an enormous amount of responsibility
associated with it. Despite the fact that it sounds like a relatively
straightforward concept at the outset – keep the systems talking to each other-
that simple phrase covers a multitude of different compatibility issues, operating
systems, troubleshooting techniques, the list goes on and on and on. As a result,
the responsibilities you face when you are just starting out as a Network Admin,
may be completely different from those that you face at a very high level. To that
end, we will once again be dividing up different questions you may face in a
Network Admin interview into 5 levels- least experienced to most experienced.
That’s not to say that these questions cannot appear in different tiers- you may
very well see some of the level 1’s during a level 5 interview. Rather, this means
that in order to reach level 5, you want to be comfortable with everything up to
that point- not necessarily remember everything by rote, but at least be able to
have a resource you can get the answers from quickly. So without further ado, let’s
begin.
Level 1 — The User
For most people growing up in a certain time period, networks seemed like a magical
thing. All of a sudden things that had been completely isolated could see each
other- communicate with each other- and thus interact with each other. In the late
90s and early 2000s, the LAN party was an art form. Being able to bring together
people across a wide variety of backgrounds to a place that they all shared a
common goal: to blow up pixels. Quite a number of dedicated locations were built
for this purpose, and many of them still exist to this day. For me however, the
ability to bring your own system over to somebody else’s house and create a network
from nothing was amazing. Network cables strewn across the house, tvs and monitors
in every possible corner, cheering and trash talk echoing from room to room- it was
truly rewarding if you could make it work. Thus it became more important to learn
more about troubleshooting systems, getting them to talk to each other across
common protocols, watching as all of a sudden instead of a collection of noisy
arguing computers, you had a cohesive network. Everyone starts as a User- having a
need to learn more about networks, and something pushing them to discover what’s
needed to make that work. Regardless of whether that need was a specific
application such as Starcraft or Halo, or more important concepts such as sharing
company files and hardware, at the beginning there is a spark that says “How do I
make this work?”
1. What is the difference between a hub and a switch?
At first glance it may be difficult to judge the difference between a hub and a
switch since both look roughly the same. They both have a large number of potential
connections and are used for the same basic purpose- to create a network. However
the biggest difference is not on the outside, but on the inside in the way that
they handle connections. In the case of a hub, it broadcasts all data to every
port. This can make for serious security and reliability concerns, as well as cause
a number of collisions to occur on the network. Old style hubs and present-day
wireless access points use this technique. Switches on the other hand create
connections dynamically, so that usually only the requesting port can receive the
information destined for it. An exception to this rule is that if the switch has
its maintenance port turned on for an NIDS implementation, it may copy all data
going across the switch to a particular port in order to scan it for problems. The
easiest way to make sense of it all is by thinking about it in the case of old
style phone connections. A hub would be a ‘party line’ where everybody is talking
all at the same time. It is possible to transmit on such a system, but it can be
very hectic and potentially release information to people that you don’t want to
have access to it. A switch on the other hand is like a phone operator- creating
connections between ports on an as-needed basis.
2. What is HTTP and what port does it use?
HTTP or HyperText Transfer Protocol, is the main protocol responsible for shiny
content on the Web. Most webpages still use this protocol to transmit their basic
website content and allows for the display and navigation of ‘hypertext’ or links.
While HTTP can use a number of different carrier protocols to go from system to
system, the primary protocol and port used is TCP port 80.
3. What is HTTPS and what port does it use?
HTTPS or Secure HTTP (Not to be confused with SHTTP, which is an unrelated
protocol), is HTTP’s big brother. Designed to be able to be used for identity
verification, HTTPS uses SSL certificates to be able to verify that the server you
are connecting to is the one that it says it is. While there is some encryption
capability of HTTPS, it is usually deemed not enough and further encryption methods
are desired whenever possible. HTTPS traffic goes over TCP port 443.
4. What is FTP and what port does it use?
FTP or File Transfer Protocol, is one of the big legacy protocols that probably
should be retired. FTP is primarily designed for large file transfers, with the
capability of resuming downloads if they are interrupted. Access to an FTP server
can be accomplished using two different techniques: Anonymous access and Standard
Login. Both of these are basically the same, except Anonymous access does not
require an active user login while a Standard Login does. Here’s where the big
problem with FTP lies however- the credentials of the user are transmitted in
cleartext which means that anybody listening on the wire could sniff the
credentials extremely easily. Two competing implementations of FTP that take care
this issue are SFTP (FTP over SSH) and FTPS (FTP with SSL). FTP uses TCP ports 20
and 21.
5. What is SSH and what port does it use?
SSH or Secure Shell is most well known by Linux users, but has a great deal that it
can be used for. SSH is designed to create a secure tunnel between devices, whether
that be systems, switches, thermostats, toasters, etc. SSH also has a unique
ability to tunnel other programs through it, similar in concept to a VPN so even
insecure programs or programs running across unsecure connections can be used in a
secure state if configured correctly. SSH runs over TCP port 22.
6. What is DHCP?
Dynamic Host Configuration Protocol is the default way for connecting up to a
network. The implementation varies across Operating Systems, but the simple
explanation is that there is a server on the network that hands out IP addresses
when requested. Upon connecting to a network, a DHCP request will be sent out from
a new member system. The DHCP server will respond and issue an address lease for a
varying amount of time. If the system connects to another network, it will be
issued a new address by that server but if it re-connects to the original network
before the lease is up- it will be re-issued that same address that it had before.
To illustrate this point, say you have your phone set to wifi at your home. It will
pick up a DHCP address from your router, before you head to work and connect to
your corporate network. It will be issued a new address by your DHCP server before
you go to starbucks for your mid-morning coffee where you’ll get another address
there, then at the local restaurant where you get lunch, then at the grocery store,
and so on and so on.
7. What is TCP?
Even if you don’t recognize anything else on this list, you like have heard of
TCP/IP before. Contrary to popular believe, TCP/IP is not actually a protocol, but
rather TCP is a member of the IP protocol suite. TCP stands for Transmission
Control Protocol and is one of the big big mindbogglingly massively used protocols
in use today. Almost every major protocol that we use on a daily basis- HTTP, FTP
and SSH among a large list of others- utilizes TCP. The big benefit to TCP is that
it has to establish the connection on both ends before any data begins to flow. It
is also able to sync up this data flow so that if packets arrive out of order, the
receiving system is able to figure out what the puzzle of packets is supposed to
look like- that this packet goes before this one, this one goes here, this one
doesn’t belong at all and looks sort of like a fish, etc. Because the list of ports
for TCP is so massive, charts are commonplace to show what uses what, and
Wikipedia’s which can be found here is excellent for a desk reference.
8. What is UDP?
The twin to TCP is UDP- User Datagram Protocol. Where TCP has a lot of additional
under-the-hood features to make sure that everybody stays on the same page, UDP can
broadcast ‘into the dark’- not really caring if somebody on the other end is
listening (and thus is often called a ‘connectionless’ protocol). As a result, the
extra heavy lifting that TCP needs to do in order to create and maintain its
connection isn’t required so UDP oftentimes has a faster transmission speed than
TCP. An easy way to picture the differences between these two protocols is like
this: TCP is like a CB radio, the person transmitting is always waiting for
confirmation from the person on the other end that they received the message. UDP
on the other hand is like a standard television broadcast signal. The transmitter
doesn’t know or care about the person on the other end, all it does care about is
that its signal is going out correctly. UDP is used primarily for ‘small’ bursts of
information such as DNS requests where speed matters above nearly everything else.
The above listing for TCP also contains counterparts for UDP, so it can be used as
a reference for both.
9. What is ICMP?
ICMP is the Internet Control Message Protocol. Most users will recognize the name
through the use of tools such as ping and traceroute, as this is the protocol that
these services run over among other things. Its primary purpose is to tell systems
when they are trying to connect remotely if the other end is available. Like TCP
and UDP, it is a part of the IP suite and uses IP port number 1. Please note, this
is not TCP port 1 or UDP port 1 as this is a different numbering scheme that for
reference can be located here (For your reference, TCP uses IP port 6, while UDP
uses IP port 17). That being said, different functions of ICMP use specific ports
on TCP and UDP. For example, the ‘echo’ portion of ping (the part where someone
else is able to ping you) uses TCP port 7.
10. What are IP Classes?
For the IP address that most people are familiar with (IPv4), there are 4 sets
(octets) of numbers, each with values of up to 255. You likely have run into this
when troubleshooting a router or a DHCP server, when they are giving out addresses
in a particular range- usually 192.x or 10.x in the case of a home or commercial
network. IP classes are primarily differentiated by the number of potential hosts
they can support on a single network. The more networks supported on a given IP
class, the fewer addresses are available for each network. Class A networks run up
to 127.x.x.x (with the exception of 127.0.0.1, which is reserved for loopback or
localhost connections). These networks are usually reserved for the very largest of
customers, or some of the original members of the Internet and xkcd has an
excellent map (albeit a bit dated) located here showing who officially owns what.
Class B (128.x to 191.x) and Class C (192.x to 223.x) networks are much more fuzzy
at the top level about who officially owns them. Class C addresses are primarily
reserved for in-house networks which is as we mentioned above why so many different
manufacturers use 192.x as their default setting. Class D and E are reserved for
special uses and normally are not required knowledge.
7 5 5
This would give us 755 as shorthand for owner read, write and execute, and
everybody else is read and execute. Let’s try this again with the 644 values. Let’s
work out the following string: rw-r–r–:
rwx rwx rwx
6 4 4
This would give us 644 as shorthand for owner read and write, with everybody else
read-only.
46. Why is it easier to maintain permissions via groups instead of individually?
As you can see from the demonstration up above, if you try to work out permissions
for every single person in your organization individually you can give yourself a
migraine pretty quickly. Therefore, trying to simplify permissions but keep them
strong is critical to administering a large network. Groups allow users to be
pooled by their need to know and need to access particular information. In this
way, it allows the administrator to set the permissions once- for the group- then
add users to that group. When modifications to permissions need to be made, its one
change that affects all members of that group.
47. What is the difference between a Forest, a Tree, and a Domain?
When you’re working in Active Directory, you see a tree-type structure going down
through various organizational units (OU’s). The easiest way to explain this is to
run through a hypothetical example.
Say that we had a location reporting for CNN that dealt with nothing but the
Detroit Lions. So we would setup a location with a single domain, and computers for
each of our users. This would mean starting at the bottom: OU’s containing the
users, groups and computers are at the lowest level of this structure. A Domain is
a collection of these OU’s as well as the policies and other rules governing them.
So we could call this domain ‘CNNDetroitLions”. A single domain can cover a wide
area and include multiple physical sites, but sometimes you need to go bigger.
A tree is a collection of domains bundled together by a common domain trunk, rules,
and structure. If CNN decided to combine all of its football team sites together in
a common group, so that its football sports reporters could go from one location to
the next without a lot of problems, then that would be a tree. So then our domain
could be joined up into a tree called ‘football’, and then the domain would be
‘CNNDetroitLions.football’ while another site could be called
‘CNNChicagoBears.football’.
Sometimes you still need to go bigger still, where a collection of trees is bundled
together into a Forest. Say CNN saw that this was working great and wanted to bring
together all of its reporters under a single unit- any reporter could login to any
CNN controlled site and call this Forest ‘cnn.com’ So then our domain would become
‘CNNDetroitLions.football.cnn.com’ with another member of this same Forest could be
called ‘CNNNewYorkYankees.baseball.cnn.com’, while yet another member could be
‘CNNLasVegas.poker.cnn.com’. Typically the larger an organization, the more
complicated it becomes to administer, and when you get to something as large as
this it becomes exponentially more difficult to police.
48. What are the differences between Local, Global and Universal Groups?
Microsoft themselves answer very succinctly here.
“A domain local group is a security or distribution group that can contain universal
groups, global groups, other domain local groups from its own domain, and accounts
from any domain in the forest. You can give domain local security groups rights and
permissions on resources that reside only in the same domain where the domain local
group is located.
A global group is a group that can be used in its own domain, in member servers and in
workstations of the domain, and in trusting domains. In all those locations, you
can give a global group rights and permissions and the global group can become a
member of local groups. However, a global group can contain user accounts that are
only from its own domain.
A universal group is a security or distribution group that contains users, groups, and
computers from any domain in its forest as members. You can give universal security
groups rights and permissions on resources in any domain in the forest. Universal
groups are not supported.”
49. What are Strong Password Requirements?
An excellent guide to password strength can be found on Wikipedia’s password
strength entry located here.
“Use a minimum password length of 12 to 14 characters if permitted.
Include lowercase and uppercase alphabetic characters, numbers and symbols if permitted.
Generate passwords randomly where feasible.
Avoid using the same password twice (eg. across multiple user accounts and/or software systems).
Avoid character repetition, keyboard patterns, dictionary words, letter or number sequences, usernames, relative or pet
names, romantic links (current or past) and biographical information (e.g. ID numbers, ancestors’ names or dates).
Avoid using information that is or might become publicly associated with the user or the account.
Avoid using information that the user’s colleagues and/or acquaintances might know to be associated with the user.
Do not use passwords which consist wholly of any simple combination of the aforementioned weak components.”
50. What is SNMP?
SNMP is the “Simple Network Management Protocol”. Most systems and devices on a
network are able to tell when they are having issues and present them to the user
through either prompts or displays directly on the device. For administrators
unfortunately, it can be difficult to tell when there is a problem unless the user
calls them over. On devices that have SNMP enabled however, this information can be
broadcast and picked up by programs that know what to look for. In this way,
reports can be run based on the current status of the network, find out what
patches are current not installed, if a printer is jammed, etc. In large networks
this is a requirement, but in any size network it can serve as a resource to see
how the network is fairing and give a baseline of what its current health is.