Help! Networking questions needed
Discussion
title says it all really.
On monday i have a tecnical interview and i have been told that i need to brush up on my technical knowledge on networking. O/S and web stuff is fine.
I am applying for a 2nd line support role in a finace company, pretty much the same as what i am doing now.
It would be great if i could get a taster of what questions i might be asked so at least i can read up on them.
Alternativley is there a site that i can go to that will test my knowledge of networking type question?
thanks
D3
On monday i have a tecnical interview and i have been told that i need to brush up on my technical knowledge on networking. O/S and web stuff is fine.
I am applying for a 2nd line support role in a finace company, pretty much the same as what i am doing now.
It would be great if i could get a taster of what questions i might be asked so at least i can read up on them.
Alternativley is there a site that i can go to that will test my knowledge of networking type question?
thanks
D3
Hi - I'm a CCNP (Cisco cert Network Professional) I also head up IT for an investment manager.. so seems similar.
Hmm poss questions:
What subnet mask would you use if you need to create a subnet in a class B network supporting no more than 30 hosts?
If that's a little high level.. then...
What's the difference between a switch & a hub?
What's the difference between a routing and a routed protocol, and give examples of each.
List the reasons why you would use IGRP as a routing protocol?
Wbat's the difference between full & half duplex?
These ok?
I can do more...!
Hmm poss questions:
What subnet mask would you use if you need to create a subnet in a class B network supporting no more than 30 hosts?
If that's a little high level.. then...
What's the difference between a switch & a hub?
What's the difference between a routing and a routed protocol, and give examples of each.
List the reasons why you would use IGRP as a routing protocol?
Wbat's the difference between full & half duplex?
These ok?
I can do more...!
I too can help, if you can stay awake .....
what level are you at ? Do you know what type of thing they have in mind ?
I guess very basic low level troubleshooting types of questions.
btw - reasons to use IGRP - I can't think of one.....
I would say, just basic stuff ... be aware of layers 1-4 (OSI model), understand basic IP addressing, understand what ethernet is, know the difference between switches, hubs and routers (OSI model, broadcast domains, collision domains etc), know some routing protocol basics (rip, ospf eigrp), know what vlans are, trunks, spanning tree - um... that'll probably do....
if they want very basic stuff you'll be OK, but if they want a little more detail and you're winging it - good luck (unless the list I gave you seems very basic in which case you'll walk it)
what level are you at ? Do you know what type of thing they have in mind ?
I guess very basic low level troubleshooting types of questions.
btw - reasons to use IGRP - I can't think of one.....
I would say, just basic stuff ... be aware of layers 1-4 (OSI model), understand basic IP addressing, understand what ethernet is, know the difference between switches, hubs and routers (OSI model, broadcast domains, collision domains etc), know some routing protocol basics (rip, ospf eigrp), know what vlans are, trunks, spanning tree - um... that'll probably do....
if they want very basic stuff you'll be OK, but if they want a little more detail and you're winging it - good luck (unless the list I gave you seems very basic in which case you'll walk it)
cramsession.com is good iirc
if you can find the ccna course it's mostly in there.
look out for questions about different cable (cat 5 utp etc - 100M length), speed/ duplex mismatch on cisco catalyst switches.
maybe a basic routing question, i.e. a has a route to b, but can't ping it - answer b doesn't have a route to a - that kinda thing .....
probably dns questions i.e. you can ping an ip address, but web browser can't reach the web page etc...
probably windows oriented networking i.e. basic connectivity - user can't connect to network: do they have an IP address, can they ping their default gateway, are they using dhcp, are they physically connected, do they have dns info etc
if you can find the ccna course it's mostly in there.
look out for questions about different cable (cat 5 utp etc - 100M length), speed/ duplex mismatch on cisco catalyst switches.
maybe a basic routing question, i.e. a has a route to b, but can't ping it - answer b doesn't have a route to a - that kinda thing .....
probably dns questions i.e. you can ping an ip address, but web browser can't reach the web page etc...
probably windows oriented networking i.e. basic connectivity - user can't connect to network: do they have an IP address, can they ping their default gateway, are they using dhcp, are they physically connected, do they have dns info etc
Dean, when you're going into 2nd level support, you can probably help me.
Some server stuff, I got stuck in at the moment:
I've got an NFS server that offers two shares with the options rw,sync,root_squash in /etc/exports . The NFS client mounts share a), but not share b), although both are configured with the same settings defaults,rw,user in fstab.
The mounted share doesn't give write access although the directory has write access for the group 'users' too.
Where should I look next?
Some server stuff, I got stuck in at the moment:
I've got an NFS server that offers two shares with the options rw,sync,root_squash in /etc/exports . The NFS client mounts share a), but not share b), although both are configured with the same settings defaults,rw,user in fstab.
The mounted share doesn't give write access although the directory has write access for the group 'users' too.
Where should I look next?
Answers:
Binary:
11111111.11111111.11111111.11100000
Or In Decimal:
255.255.255.224
To give you 32 hosts, which taking away broadcast and network addresses gives you 30.
A Hub will broadcast to all available ports whereas a switch will only broadcast to its intended recipients.
A routing protocol gathers and shares the information required to update and maintain routing tables (IGRP, RIP)
A routed protocol containes the data elements required for a packet to be sent outside of its host network (IP and IPX)
-Does not suffer from the 15/16 hop limit that RIP/RIP2 does. So IGRP offers large expansion support
-As Simple To Adminsiter as RIP/RIP2
-Responds quickly to network changes as IGRP updates when route changes occur
-Supports upto 4 non-equal paths between source and destination.
You can send/recieve over both but with half duplex you can't send and recieve at the same time (think walky talky/2 way radio). Full duplex can send and recieve at the same time (think telephone).
And I am available for contracts if anyone needs a decent IT chap
Network, Desktop, Mech Control, Bespoke System Support etc. etc. all covered.
Matt
>> Edited by Matt_T16 on Thursday 12th August 21:19
jh_007 said:
Hmm poss questions:
What subnet mask would you use if you need to create a subnet in a class B network supporting no more than 30 hosts?
Binary:
11111111.11111111.11111111.11100000
Or In Decimal:
255.255.255.224
To give you 32 hosts, which taking away broadcast and network addresses gives you 30.
jh_007 said:
If that's a little high level.. then...
What's the difference between a switch & a hub?
A Hub will broadcast to all available ports whereas a switch will only broadcast to its intended recipients.
jh_007 said:
What's the difference between a routing and a routed protocol, and give examples of each.
A routing protocol gathers and shares the information required to update and maintain routing tables (IGRP, RIP)
A routed protocol containes the data elements required for a packet to be sent outside of its host network (IP and IPX)
jh_007 said:
List the reasons why you would use IGRP as a routing protocol?
-Does not suffer from the 15/16 hop limit that RIP/RIP2 does. So IGRP offers large expansion support
-As Simple To Adminsiter as RIP/RIP2
-Responds quickly to network changes as IGRP updates when route changes occur
-Supports upto 4 non-equal paths between source and destination.
jh_007 said:
Wbat's the difference between full & half duplex?
You can send/recieve over both but with half duplex you can't send and recieve at the same time (think walky talky/2 way radio). Full duplex can send and recieve at the same time (think telephone).
And I am available for contracts if anyone needs a decent IT chap
Network, Desktop, Mech Control, Bespoke System Support etc. etc. all covered. Matt
>> Edited by Matt_T16 on Thursday 12th August 21:19
Guydw said:
I too can help, if you can stay awake .....
what level are you at ? Do you know what type of thing they have in mind ?
I guess very basic low level troubleshooting types of questions.
btw - reasons to use IGRP - I can't think of one.....
I would say, just basic stuff ... be aware of layers 1-4 (OSI model), understand basic IP addressing, understand what ethernet is, know the difference between switches, hubs and routers (OSI model, broadcast domains, collision domains etc), know some routing protocol basics (rip, ospf eigrp), know what vlans are, trunks, spanning tree - um... that'll probably do....
if they want very basic stuff you'll be OK, but if they want a little more detail and you're winging it - good luck (unless the list I gave you seems very basic in which case you'll walk it)
Going from what i have heard its not going to be all high level stuff. I think that the guy just wants to know if i know what i am talking about and that i won't be a burden to the team. I have an idea of what things are in my head, but it never comes out the way that it should. I think that most of the questions are going to be a mixture of low level with a bit of high level thrown in to catch me out.
IGRP?
What's the difference between a switch & a hub?
[/quote]
A Hub will broadcast to all available ports whereas a switch will only broadcast to its intended recipients.
Sorry Mat, but that is a wrong answer. Hub and switches will both forward broadcasts. Routers don't.
A hub has a single bus architecture, meaning collisions will arise with nodes transmitting at the same time.
d3ano said:
I too can help, if you can stay awake .....
what level are you at ? Do you know what type of thing they have in mind ?
I guess very basic low level troubleshooting types of questions.
btw - reasons to use IGRP - I can't think of one.....
I would say, just basic stuff ... be aware of layers 1-4 (OSI model), understand basic IP addressing, understand what ethernet is, know the difference between switches, hubs and routers (OSI model, broadcast domains, collision domains etc), know some routing protocol basics (rip, ospf eigrp), know what vlans are, trunks, spanning tree - um... that'll probably do....
if they want very basic stuff you'll be OK, but if they want a little more detail and you're winging it - good luck (unless the list I gave you seems very basic in which case you'll walk it)
Going from what i have heard its not going to be all high level stuff. I think that the guy just wants to know if i know what i am talking about and that i won't be a burden to the team. I have an idea of what things are in my head, but it never comes out the way that it should. I think that most of the questions are going to be a mixture of low level with a bit of high level thrown in to catch me out.
IGRP?
Interoir gateway routing protocol.
Cisco propriatary, however i'd use EIGRP (e= enhanced)
If you're not a cisco shop though, it does't matter.
Hub v switch - they both have a single broadcast domain, a hub has a single collision domain and a switch has individual collision domains for each port...
So a broadcast packet will be forwarded out of every port except the one that it is received on - this is the same for a hub and a switch, but on a hub every packet shares the same piece of wire, on a switch each port has its own dedicated piece of wire.
(this is basically agreeing with the previous post)
IGRP - you are both right, but the reasons given to use it are text book exam (CCNA) stuff only, in reality you would never use it (it has been rmoved from the CCIE lab along with Decnet, IPX and Token Ring....). Cisco implemented EIGRP, this is very good, very scalable, easy to administer and converges quickly. Unfortunately since it is Cisco proprietry, everyone else made a point of not supporting it, so in reality you should always use OSPF, as you will always need something non Cisco to be part of your network eventually .......
bored yet ? lol
So a broadcast packet will be forwarded out of every port except the one that it is received on - this is the same for a hub and a switch, but on a hub every packet shares the same piece of wire, on a switch each port has its own dedicated piece of wire.
(this is basically agreeing with the previous post)
IGRP - you are both right, but the reasons given to use it are text book exam (CCNA) stuff only, in reality you would never use it (it has been rmoved from the CCIE lab along with Decnet, IPX and Token Ring....). Cisco implemented EIGRP, this is very good, very scalable, easy to administer and converges quickly. Unfortunately since it is Cisco proprietry, everyone else made a point of not supporting it, so in reality you should always use OSPF, as you will always need something non Cisco to be part of your network eventually .......
bored yet ? lol
jh_007 said:
What's the difference between a switch & a hub?
A Hub will broadcast to all available ports whereas a switch will only broadcast to its intended recipients.
Sorry Mat, but that is a wrong answer. Hub and switches will both forward broadcasts. Routers don't.
A hub has a single bus architecture, meaning collisions will arise with nodes transmitting at the same time.[/quote]
He is right, but i think the choice of words cought him out.
The hub sends everything to every port, a switch doesn't.
agent006 said:
What's the difference between a switch & a hub?
A Hub will broadcast to all available ports whereas a switch will only broadcast to its intended recipients.
Sorry Mat, but that is a wrong answer. Hub and switches will both forward broadcasts. Routers don't.
A hub has a single bus architecture, meaning collisions will arise with nodes transmitting at the same time.
He is right, but i think the choice of words cought him out.
The hub sends everything to every port, a switch doesn't.[/quote]
Sorry I was trying to put it in simple terms and maybe went a little too simple.
Matt
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff