I use the 172.16 as a DMZ network, where I place my routers, and have DHCP for public access. The 10.0 network is my private network and houses my private esxi/server environments.
Ive never had any issues previously with both wired and wireless devices connecting to my DHCP server running in my DMZ network. Heck, even my android and Raspbery PI's have no issues.
As I said earler, I normally use static IP's in the 172.16.0.x block and reserve dhcp for 172.16.1.x.
It's been like this for almost 10 years, although with different routers, firewalls, barracudas etc...
so you main ip is not dhcp then that makes sense i had one of those once but it cost to much to justify keeping . your main IP is a static ip because if that's the same IP you have had for 10 years it has never changed even with a new router then it more then like is a static IP at no more cost to you, nice . then if that's the case and they don't set the miner to DHCP by default your network won't find it . the miner is static at 192.168.0.x or 192.168.1.x, if the miner is set to dhcp and works then it should pop on your network no matter what the network is at .turn off dmz and try that way ?. doesn't dmz only allow one thing thu it, don't know never used it .
The miner the way it sounds doesn't come as DHCP by default and is set to the normal network for china with a static IP . unless it doesn't work or something is corrupted in the mining software that's stopping it from getting a ip
I'm guessing now wish I had one to play with .
. gl i hope you get it, please let us know.!!!
cyz