Troubleshooting Windows Networking
Network Troubleshooting Protocol in OSI Reference Model
Your Name
Your School
Network Troubleshooting Protocol in OSI Reference Model
Troubleshooting windows networking can be challenging for both PC and large windows enterprise network. Complexity increases with the number of devices. However, there are certain steps which we can followed to solve this issue.
a. Know the infrastructure – The first thing is to know the infrastructure when one performs troubleshooting.
b. Learn about the network – If one is unaware of the infrastructure design and the documentation part, still he can troubleshoot by learning regarding the network infrastructure.
c. Network connection is down – If the physical later of the OSI model is not working, then nothing else will work and it is advisable to troubleshoot from the lowest layer to the higher ones.
d. No IP Address – Irrespective of having an automatic private IP address or no IP address, one has to get an IP address so that he can use the network.
e. No DNS Servers – One can communicate with the IP address only if the network does not have DNS servers configured.
f. No Default Gateway – One can communicate via his local LAN but not on another IP subnet if the network does not support default gateway configuration.
g. Misconfigured Subnet Mask – One will get unpredictable results if he has configured an incorrect IP subnet mask. (Davis, 2011)
Troubleshooting is easy but one has to understand the network design and layout. The different layers are physical, Ethernet, Network, Transport, Session, Presentation and Application layers. (Bauer, 2004)
Works Cited:
1. Bauer, B. (2004). A human factors extension to the seven-layer OSI reference model, 3-5.
1. Davis, D. (2011). General Networking. 7 Steps To Successfully Troubleshoot A Windows Network, 2-4.
Your Name
Your School
Network Troubleshooting Protocol in OSI Reference Model
Troubleshooting windows networking can be challenging for both PC and large windows enterprise network. Complexity increases with the number of devices. However, there are certain steps which we can followed to solve this issue.
a. Know the infrastructure – The first thing is to know the infrastructure when one performs troubleshooting.
b. Learn about the network – If one is unaware of the infrastructure design and the documentation part, still he can troubleshoot by learning regarding the network infrastructure.
c. Network connection is down – If the physical later of the OSI model is not working, then nothing else will work and it is advisable to troubleshoot from the lowest layer to the higher ones.
d. No IP Address – Irrespective of having an automatic private IP address or no IP address, one has to get an IP address so that he can use the network.
e. No DNS Servers – One can communicate with the IP address only if the network does not have DNS servers configured.
f. No Default Gateway – One can communicate via his local LAN but not on another IP subnet if the network does not support default gateway configuration.
g. Misconfigured Subnet Mask – One will get unpredictable results if he has configured an incorrect IP subnet mask. (Davis, 2011)
Troubleshooting is easy but one has to understand the network design and layout. The different layers are physical, Ethernet, Network, Transport, Session, Presentation and Application layers. (Bauer, 2004)
Works Cited:
1. Bauer, B. (2004). A human factors extension to the seven-layer OSI reference model, 3-5.
1. Davis, D. (2011). General Networking. 7 Steps To Successfully Troubleshoot A Windows Network, 2-4.
Cited: 1. Bauer, B. (2004). A human factors extension to the seven-layer OSI reference model, 3-5. 1. Davis, D. (2011). General Networking. 7 Steps To Successfully Troubleshoot A Windows Network, 2-4.