Return to Answer

For reference please see TLS/SSL handshake.

Both of clients have same content, the difference in the labeling comes from the fact that in the first instance the negotiation doesn't complete, therefore wireshark labels both packets differently. In pcap files you can see that after client trying to establish SSL connection server replaying with RST, ACK packet. Than again client trying to establish another connection hello is labeled TLSv1.2. But again server is sending RST. Both hello are TLSv1.2 there is only difference how wireshark is labelling them. I would assume that server is misconfigured. I would suggest checking cipher suits used on server.

Possibly the best way to troubleshoot this is by simply trying to connect to the server with openssl.

openssl s_client -connect example.com:443

You should see what cipher is selected in this transaction (if it works at all).

But this post is offtopic for this group.

For reference please see TLS/SSL handshake.

Both of clients hello have same content TLSv1.2, the difference in the labeling comes from the fact that in the first instance the negotiation doesn't complete, therefore wireshark labels both packets differently. In pcap files you can see that after client trying to establish SSL connection server replaying with RST, ACK packet. Than again client trying to establish another connection hello is labeled TLSv1.2. But again server is sending RST. Both hello are TLSv1.2 there is only difference how wireshark is labelling them. I would assume that server is misconfigured. I would suggest checking cipher suits used on server.

Possibly the best way to troubleshoot this is by simply trying to connect to the server with openssl.

openssl s_client -connect example.com:443

You should see what cipher is selected in this transaction (if it works at all).

But this post is offtopic for this group.

For reference please see TLS/SSL handshake.

Both of clients have same content, the difference in the labeling comes from the fact that in the first instance the negotiation doesn't complete, therefore wireshark labels both packets differently. In pcap files you can see that after client trying to establish SSL connection server replaying with RST, ACK packet. Than again client trying to establish another connection hello is labeled TLSv1.2. But again server is sending RST. Both hello are TLSv1.2 there is only difference how wireshark is labelling them. I would assume that server is misconfigured. I would suggest checking cipher suits used on server.

Possibly the best way to troubleshoot this is by simply trying to connect to the server with openssl. openssl s_client -connect [server IP:port] You should see what cipher is selected in this transaction (if it works at all).

But this post is offtopic for this group.

For reference please see TLS/SSL handshake.

Both of clients have same content, the difference in the labeling comes from the fact that in the first instance the negotiation doesn't complete, therefore wireshark labels both packets differently. In pcap files you can see that after client trying to establish SSL connection server replaying with RST, ACK packet. Than again client trying to establish another connection hello is labeled TLSv1.2. But again server is sending RST. Both hello are TLSv1.2 there is only difference how wireshark is labelling them. I would assume that server is misconfigured. I would suggest checking cipher suits used on server.

Possibly the best way to troubleshoot this is by simply trying to connect to the server with openssl.

openssl s_client -connect example.com:443

You should see what cipher is selected in this transaction (if it works at all).

But this post is offtopic for this group.

For reference please see TLS/SSL handshake.

Both of clients have same content, the difference in the labeling comes from the fact that in the first instance the negotiation doesn't complete, therefore wireshark labels both packets differently. In pcap files you can see that after client trying to establish SSL connection server replaying with RST, ACK packet. Than again client trying to establish another connection hello is labeled TLSv1.2. But again server is sending RST. I would assume that server is misconfigured. I would suggest checking cipher suits used on server.

Possibly the best way to troubleshoot this is by simply trying to connect to the server with openssl. openssl s_client -connect [server IP:port] You should see what cipher is selected in this transaction (if it works at all).

But this post is offtopic for this group.

For reference please see TLS/SSL handshake.

Both of clients have same content, the difference in the labeling comes from the fact that in the first instance the negotiation doesn't complete, therefore wireshark labels both packets differently. In pcap files you can see that after client trying to establish SSL connection server replaying with RST, ACK packet. Than again client trying to establish another connection hello is labeled TLSv1.2. But again server is sending RST. Both hello are TLSv1.2 there is only difference how wireshark is labelling them. I would assume that server is misconfigured. I would suggest checking cipher suits used on server.

Possibly the best way to troubleshoot this is by simply trying to connect to the server with openssl. openssl s_client -connect [server IP:port] You should see what cipher is selected in this transaction (if it works at all).

But this post is offtopic for this group.