That's not so much a Monoblock problem per se, but an installation issue - as per your other Thread. (Ah, no - as per this Thread: Having two related ones running leads to confusion ...............)
Have you assigned the Ports correctly in your Receiver's Menus? If so, the other possibility as a root cause is, as mentioned in the other Thread, a failure of your specific Monoblock
Also stated in the other Thread, there is no innate reason at all for a Monoblock not to work as it fully and completely meets the DiSEqC switching requirements posted earlier. Indeed, that's why we have the various DiSEqC protocols (1.0, 1.1, 1.2, 2.0 etc) - to ensure components such as external switches (Including integral ones as in Monoblocks), motors etc are compatible. Consequently, incorrect behaviour almost certainly is due to incorrect configuration and/or installation.
Anyway, you appear to have cracked it now, which is the main thing.