Thanks for the reply!
I took a look at some of those searches to look for additional messages.
I don't think it would be the firewall, because if I change the interval to 30 it can eventually connect to the DS and shows up in the Forwarder Management. I still double checked though and see no blocks and the port is also added in firewalld.
For the deployment server side I didn't get any messages from that that search.
For the client side I saw the following messages
- Attempted handshake xxx times. Will try to re-subscribe to handshake reply
- Phonehome thread start, intervals: handshakeRetry=60 phonehome=300.0
- channel=deploymentServer/phoneHome/default Will retry sending phonehome to DS; err=not_connected
- channel=tenantService/handshake Will retry handshake message to DS; err=not_connected
Also I saw some messages that look related.
HTTPPubSubConnection - Unable to parse message from PubSubSvr:
Could no obtain connection, will retry after=xxx.xxx seconds.
I did a tcpdump and made two different pcaps to look at in wireshark and I kinda wanna say this looks like the client is sending resets before the TLS connection could be finished? Is that what is happening here?
interval set to 300 (Bad connection to the ds)
client SYN
ds SYN, ACK
client ACK
client TLSv1.2 Client Hello
ds ACK
ds Server Hello, Certificate, Server Hello Done
client ACK
client TLSv1.2 Client Key Exchange, Change Cipher Spec, Encrypted Handshake Message
ds TLSv1.2 New Session Ticket, Change Cipher Spec, Encrypted Handshake Message
client TLSv1.2 Application Data
ds ACK
client FIN, ACK
ds ACK
ds TLSv1.2 Application Data
client RST
ds TLSv1.2 Application Data
client RST
ds TLSv1.2 Encrypted Alert
client RST
ds FIN, ACK
client RST
interval set to 30 (Good connection to ds)
client SYN
ds SYN, ACK
client ACK
client TLSv1.2 Client Hello
ds ACK
ds Server Hello, Certificate, Server Hello Done
client ACK
client TLSv1.2 Client Key Exchange, Change Cipher Spec, Encrypted Handshake Message
ds TLSv1.2 New Session Ticket, Change Cipher Spec, Encrypted Handshake Message
client TLSv1.2 Application Data
ds TLSv1.2 Application Data
ds TLSv1.2 Application Data
client ACK
client FIN, ACK
ds TLSv1.2 Encrypted Alert
client RST
ds FIN, ACK
client RST
After all that I went through and started verifying the cipherSuites and sslVersions between the client and ds for web.conf and server.conf which both are using splunks default values.
Verified also the date on each server because I saw that could be another issue when dealing with TLS connections.
... View more