Skip to main content

A screenshot of a computer

Description automatically generated

 

Designing a SOHO network with DHCP


Network requirements for the office

Sales department – 4 computers

Finance department – 3 computers

Networking devices requirement:

·         1 router

·         2 switches (one for each department)

·         1 DHCP server


Documentation

I started by setting up the network topology and used the automatic connecting cable to connect all the devices together.

A diagram of a computer network

Description automatically generated

Then I configured the server with IPv4 address and a subnet mask. to do this you have to press on the server and then go to desktop. Then I filled in all the parameters as seen below.

A screenshot of a computer

Description automatically generated

Then I had to configure the DHCP server. To do this I clicked on the server > services > DHCP. Then I turned on the serves and configured the server as seen in this screenshot.

A screenshot of a computer

Description automatically generated

For the next step I configured the router with the IPv4 address and subnet mask. To assign these IP addresses I went into the router > config > interface, and then turned on the ports. Then I went into FastEthernet and configured it according to IP addressing table below.

S.N. O

Device

Interface

IPv4 Address

Subnet Mask

1.

Router0

FastEthernet0/0

172.168.10.1

255.255.255.0

FastEthernet0/1

192.168.10.1

255.255.255.0

 

A screenshot of a computer

Description automatically generatedAfter that step I had to configure all the PC’s and changed the IP configurations. To do this I had to press on a PC > desktop > IP configuration. And then I changed its state from static to DHCP. But then I quickly ran into an issue as DHCP failed and started giving out APIPA addresses.

 

 













Re-starting

There were a few things that went wrong the first time when I tried to complete this like:

·         The router didn’t allow traffic to go between the two subnets

·         The DHCP wasn’t configured on the sales subnet to use the DHCP server that was on the finance subnet.

When I tried to fix these mistakes cisco packet tracer also crashed so I had to restart this project. But on the second try it worked perfectly.

A diagram of a network

Description automatically generated

Comments

Popular posts from this blog

Types of network adapters in virtual box

  Types of network adapters in VirtualBox In VirtualBox there’s multiple types of network adapters that can be used to configure virtual machines for different networking needs. Down below will give you a brief overview of each type. NAT (network address translation) The VM is placed behind a VirtualBox-managed router. This allows the VM to access the external network via the networks host’s IP, but the VM itself remains invisible to the outside. Its most suitable for simple internet access with minimal configuration NAT network This is like NAT, but it allows multiple VM’s to communicate with each other in the same NAT network all while sharing the host’s internet connection. Its commonly used when you want to simulate a small, isolated network of VM’s that can also access the internet. Bridged adapter This VM is connected directly to the physical network as if it is a separate device, it also receives its own IP address from the same network as the host. This is ide...

API's

  API's Types of API's REST API - Representational State Transfer is a commonly used API category that isn’t dependent on a specific protocol. It’s considered a relatively user-friendly API to work with and many developers are experienced in this technology. It’s an architecture style of communicating interfaces. SOAP API - Simple Object Access Protocol is an API that connects different platforms together through HTTP and XML. Its relatively older than other API implementations, but it provides more security as it follows strict protocols. It’s a protocol for communication between applications. ASP.NET API - Specific form of REST API developed around .NET technology. REST vs SOAP Both have some similarities for instance they both support SSL/TLS for secure and encrypted communications, also they both use HTTP to exchange information. When deciding which API to use you must take in many factors into consideration like, security, ACID compliance, and overall application design. F...