Thanks for responding!

Yes, what you have looks right. The customer's network is large enough that they mask only the first 2 octets generally, meaning that anything on the 10.136.xxx.xxx network should communicate unless the masks are set up differently in the device's settings, like in my problematic case.

Your answer will work for sure. I have not gotten clearance for another IP on the 10.136.4.xxx subnet as of yet, so I was hoping there was some slicker way to pull it off until I do.

If I don't have any other answers once I get the 2nd IP in the 10.136.4.xxx subnet, I'll mark this as the correct answer for the post.

Thanks, @CarltonR !