Content Comparison

...

1. Connected DC to TCS via gray ethernet cable. Saw changes in DC-reported ipconfig  before and after (see below).
2. We see that the new connections find MAC addresses and IPs, but we don't know where the IPs come from.
3. We followed this tutorial https://www.maketecheasier.com/connect-two-windows-computer-on-lan/
4. After the tutorial, T.C.S connects to D.C 0. With TCP/IP connection on, Zenmap detects host up on 192.168.0.2:5003 (IP address : port)
5. A Wireshark scan confirms connection to T.C.S from D.C. and it also confirms packets are sent (converting hexadecimal output from wireshark to ASCII confirms command was sent)

   1. Code Block
      language text title Wireshark output on TCP connection between D.C. and T.C.S linenumbers true collapse true
      insert wireshark output from simple connection of TCP/IP client

      Code Block

      language	text
      firstline	4
      title	Wireshark output of commands sent over TCP
      linenumbers	true
      collapse	true

      insert wireshark output from command sent from TCP/IP client

      Image Added

      The first 3 packets are the connection of the TCP/IP client to the TCP server. The rest are commands sent which seem to be successful, but they don't update the values in DFMTCS.

Other Notes

PORT     STATE    SERVICE

5003/tcp filtered filemaker

MAC Address: 00:18:7D:12:A1:D0 (Armorlink .Ltd)



Nmap done: 1 IP address (1 host up) scanned in 0.35 seconds

...