# PCCC protocol causing problems

**URL:** <https://forum.inductiveautomation.com/t/pccc-protocol-causing-problems/11651>\
**Category:** Ignition\
**Created:** [May 11, 2016, 11:39pm UTC](https://forum.inductiveautomation.com/t/pccc-protocol-causing-problems/11651 "2016-05-11T23:39:55Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [August 21, 2018, 3:14pm UTC](https://forum.inductiveautomation.com/t/pccc-protocol-causing-problems/11651/15 "2018-08-21T15:14:31Z")

</div>

Ah! I was thinking the driver was falling back to the direct protocol. You won’t be able to block PCCC access via Ethernet/IP without also blocking straight E/IP. Hmmm. Sounds like we need a new advanced setting in the driver. Maybe posting in [ideas.inductiveautomation.com](http://ideas.inductiveautomation.com) would help – I’d upvote it.

---

_[View the full topic](https://forum.inductiveautomation.com/t/pccc-protocol-causing-problems/11651)._