# NR_PROXY_REJECT (0x0003)

> What NACK reason 0x0003, NR_PROXY_REJECT, means when a fixture sends it, and what to do about it at the bench.

- **Code:** 0x0003
- **Decimal:** 3
- **Kind:** NACK reason
- **Version:** 0.12.0
- **Runs on:** macOS 15 Sequoia or later, Apple silicon or Intel
- **Needs:** An Enttec DMX USB Pro with its DMX/RDM firmware (major version 2), or, on a rig, an Art-Net 4 node with RDM on at its ports
- **Price:** Free

`NR_PROXY_REJECT` is NACK reason `0x0003` (3): the reason a fixture gives when it refuses an RDM request this way. RDMBench says it as: *the proxy in front of the device rejected the request (NR_PROXY_REJECT)*.

## At the bench

Something between the controller and the unit, a node, splitter or proxy that answers RDM for the units behind it, turned the request away, and the unit may never have seen it. Put the unit on a direct line before reading anything into it.

Numbered in [E1.20](https://tsp.esta.org/tsp/documents/published_docs.php), Table A-17. Every NACK reason is listed in [NACK reasons](/codes/nack/).
