Solution

The correct answer is Both Statement I and Statement II are true

Key Points

• Statement I:
  • After the server is rebooted, the TCP server application can indeed start listening again on the same port P.
  • There is nothing technically preventing this. After a crash, provided there are no other issues (like issues with the OS, hardware, the network, etc.), the server software can start up again and bind to the same port it was listening on before the crash.
• Statement II:
  • ​When the client sends a packet after the server rebooted, it's very likely to receive a RST (reset) segment in response.
  • This is because from the server's perspective, it has no knowledge of any prior connection that might have existed before it rebooted, so if it gets a packet from the client for what the client thinks is an ongoing connection, the server's response will be to send a RST to effectively tell the client "I don't know about any such connection."