hping3 is typically used as an attacking tool that attempts to break the normal way of doing things-in the described case the 3 way handshake- in order to inflict damage to the destination.
Having a tool to a establish a flood of TCP connections would probably be classified as a stress-testing tool rather than an attacking tool.
-S which is the most popular option of hping3 refers to SYN flooding attack and I will take a guess that this is what you used. In this mode hping3 sends a myriad of SYN messages but intentionally refrains from sending the last message of the 3-way handshake. The connections are left "half-open" and the victim has already committed a ton of resources (in theory) for the totality of these connections.
In your case the attacking machine's kernel is issuing the RST messages almost immediately preventing the attack to complete. The reasons for this are mentioned by @MarkoPolo. If the attack would work, you should actually expect to see several retransmission attempts of the SYN-ACK message from the victim corresponding to each SYN.
If your plan is actually to successfully execute the attack then I suggest you enter a firewall rule to effectively drop your outgoing RST messages.
iptables –A OUTPUT –p tcp –s 192.168.56.101 --tcp-flags RST RST –j DROP