I have already posted this in a couple of places. I will post here again to increase the viewer base.
After doing some testing on my network I contacted my ISP. We were able to find the culprit for my Cattle Error. It had to do with the packet routing. Who ever was handled routing table for the outgoing traffic probably had something messed up. My ISP switched were there outbound traffic was going and I was able to connect immediately. This is because the internet traffic was taking a different path to the Destiny servers. My buddy who lives in the same town and has the same ISP, was also having the cattle error code and this fixed his problem as well. So you guys might want to call your ISP and see if they can switch who they are routing their outbound traffic through. If you are using a larger company for your ISP , for example Comcast, just have them look into their packet routing for destiny. Those of you who have a smaller local based ISP might get quicker results. I hope this helps someone. If you have any quests please feel free to ask and I will answer them to the best of my ability.
English
-
Helps to tell people the route and/or ips that were having the problem. Also, the destination you are using.
-
My ISP was routing their traffic through NTS out of Dallas TX
-
Where to for destination? I've not bothered to log it yet, going to at home myself, since windstream will require full routing logs, but others might require herp who aren't so network inclined.
-
I don't have the routing info.
-
Then how did you tell your ISP to do any of this?
-
Small company and they just routed their outbound traffic through a different company.