Don't worry about the access violations. Those will fix themselves once you have connectivity to CCC.
I know a lot of this is rehash, but perhaps by writing all this out again in a new way, it will help identify the problem.
Something to consider: connectivity issues can be caused by local firewall (CMC PC), remote firewall (CCC PC),
or something in between the two PC's (network equipment). Since I don't know the layout or configuration of your home network, I want to make sure that you're looking at all places.
CMC Network Access
First, CMC needs unblocked TCP network access, and the ability to reach the CCC PC on the network using TCP. Don't assume this works just because you can reach the network shared folder (though that is a good sign). An easy way to test this is to temporarily disable the firewall and see if CMC connects. If CMC now connects, then the CMC PC's firewall is the culprit. I don't know what firewall software you use, but it is possible that you have multiple firewall parameters competing with each other, and even though you've opened TCP Any for CMC, it might be blocked by another setting.
Another good test is to open a Command prompt and Ping the CCC server using the same name you configured in CMC, to validate that name resolving is working.
CCC Network Access
Next, CCC needs unblocked TCP inbound on port 1031, and CCC must be running. Again, a good way to test if the CCC PC's firewall is the issue is to temporarily disable the firewall and see if connectivity begins to work. And as with the CMC PC, it's possible you have multiple rules and even though you unblocked port 1031, another rule might be blocking access. Also, from your screenshot I can't quite see the full path to the exe that you have excluded.
Other Thoughts
On the CCC Firewall, I see you are only opening port 1031 for [assuming CCC.exe, but can't see it in the screenshot]. This is a step more restrictive than I normally recommend. Typically, we just open for 1031 Inbound for the entire PC (all apps) - the only thing that will be using 1031 is CCC, so it's essentially the same thing, but eliminates the possibility that the firewall is opening 1031 for a different filepath than the currently running CCC.exe.
EDIT: I also couldn't see in your screenshot if the CCC rule was inbound or outbound, it needs to be inbound.
Final Thoughts
That's pretty much it.
- CMC needs TCP Outbound general access
- CCC needs TCP Inbound Port 1031 (but usually we just open 1031 for the entire PC, not just CCC)
- CCC needs to be running
- The CMC PC needs to be able to ping the CCC PC.
If the individual firewall tests described above don't work, you may want to try disabling the firewall on both the CCC PC and the CMC PC at the same time.