'TCP Out-of-Order' error message

Solved
CKYI
Comes here often

'TCP Out-of-Order' error message

After the power of MX device is turned on and attach is completed, the address of the specific server is received through the DNS query,

I am getting a 'TCP Out-of-Order' error message when I connect a TCP session to this address.
Symptom: The device continues to attempt DNS query operation at the address: meraki.com, ** brightcloud.com.
→ Question: Is it normal for the device to perform the corresponding DNS query operation by default?

Symptom: meraki.com, ** brightcloud.com These two servers appear to be unresponsive, resulting in a TCP Out-of-Order error message.
→ Question: Is not the server currently turned on? Or is it necessary to register the device separately for the response?

1 Accepted Solution
ww
Kind of a big deal
Kind of a big deal
1 Reply 1
ww
Kind of a big deal
Kind of a big deal
Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels