3 Months later, found out the "cause" of 1566's and 1311's

TS_Confusion

And I must say, total crap.

Anyway, I am the guy that had the three subnets that could not "talk" with
each other and the fourth could talk with the rest.

Even though I setup site links, checked DCdiag, ran repadmin, used dlp,
removed metadata, etc, I would ALWAYS get 1566 errors and 1311's.

The network admin before me had "Bridge all site links" (or whatever) on, I
took that option off 3 months ago.
According to Microsof this should replicate without having to reboot anything.

This is dead wrong, I came across a forum that another user with a similar
problem as mine fixed. All he did was reboot the DC and that fixed the
problem. He made the change on (removing the bridge all site link option) and
was having the same problem as me, two weeks later he was at witt's end and
finally restarted the server.

Well, I restarted the server (DC) that was giving me the errors and like
magic they all went away.

So if you changed the site link option to disabled and you are still having
the problem, REBOOT the server first, I wasted a LONG time trying to figure
out a simple problem.