Project One Stepping Stone: Network Troubleshooting Practice Melisa Hutchison Southern New Hampshire University CYB-310-R3478 Network Defense Kevin Kenna 01/27/2024
Network Deficiencies Issue One The Sales Department network segment needs read/write/execute privileges to the Customer Service Department network segment. Identify the configuration error causing the issue by providing appropriate screenshot(s). The firewalls had rules set that was blocking traffic from private networks % PC3_SALES - VMware Workstation 14 Player (Non-commercial use only) Player . II. @BH2 - 0 × +1 / nfSense.Incalciomain - X pfSense.localdomain - Interfaces: WAN (em0) + v 0 × U 3 Recycle U 192.168.1.1/interfaces.php ... and bogon traffic (outside networks excluding private networks and loopback address). It is not necessary to have bogon traffic blocked if there is cmd Shortc Firefe Alias IPv4 1 32 v address The value in this field is used as a fixed alias IPvd address by the DHCP client. Reject leases from To have the DHCP client reject offers from specific DHCP servers, enter their IP addresses here (separate multiple entries with a comma). This is useful for rejecting leases from cable modems that offer private IP addresses when they lose upstream sync. Reserved Networks Block private networks and loopback addresses Blocks traffic from IP addresses that are reserved for private networks per RFC 1918 (10/8, 172.16/12, 192.168/16) and unique local addresses per RFC 4193 (fc00:/7) as well as loopback addresses (127/8). This option should generally be turned on, unless this network interface resides in such a private address space, too. another firewall blocked said traffic coming from the internet. Having these Block bogen networks Blocks traffic from reserved IP addresses (but not RFC 1918) or not yet assigned by IANA. Bogons are prefixes that should never appear in the Internet routing table, and so should not appear as the source address in any packets received. Note: The update frequency can be changed under System > Advanced, Firewall & NAT settings 11:54 AM Tune here to search settings on can mess up the sharing properties between networks. They needed to be removed. Other rules then needed to be set in place to only allow traffic from internal networks. PCI_SALES - VMinare Workstation 14 Player (Non-commercial use only) × cod - Shoncut Ethernet adapter Ethernete 3: Connection-specific DNS Suffix Link-local IPV6 Address IPV4 Address. Subnet Mask . Default Gateway fell@: : 7995:199e: 18f6 :< 211X2 192.168.1.30 255.255.255.0 1 192.168.1.1 C: \Windows\ System32>ping 192.168.2.38 Pinging 192.168.2.30 with 32 bytes of data: Request timed out. Oneply from 192.168.1.30: Destination host unreachable. Reply from 192.168.1.30: Destination host unreachable. Reply from 192.168.1.30: Destination host unreachable. Ping statistics for 192.168.2.30: Packets: Sent = 4, Received - 2, Lost - 1 (25% locs). C: \Windows \System32>_ O e × fSense ?: 1.49 Network: Human Resources Server_Texthetwork vm PC4_Network3-1 PEL_Networky-1 vm vm PC3_Subnct2 . VMware Workstation 14 Player (Non-commercial use only) - × cmd - Shortcut × Windows IP Configuration Ethernet adapter Ethernete 3: Connection-specific DNS Suffix Link-local IPve Address IPV4 Address. Subnet Mask Default Gateway fe80 :: 6doftabea: 5882:729a%2