Suddenly unable to probe http and routeros?!?

ok, I’m feeling just a little stupid here and hoping it’s something obvious… So please burn away..

I’ve just moved my Dude server from a 192.168.1.0/24 network to my DMZ on 192.168.2.0/24.

In the process we have 3 gateways setup on one firewall and are changing to a new High Speed circuit and I’m migrating the ip addresses across. Which really doesn’t make any difference in the grand scheme of things, but provides a nice back story for you.

Anyways, we’re pinging and monitoring internet and external addresses with no worries, but for some reason Dude (3.5) has stopped polling HTTP, RouterOS, HTTP, SSH, POP3, IMAP and some others. SNMP a continues to work but I’m now unable to torch or poll


A MASQ or NAT issue you say. Well I’m unable to poll devices in the same subnet (DMZ) so there is no NAT, I can browse HTTP (using firefox) from the dude server to these machines.

So it seems something has gone astray with the Agent / Probe, but I can’t really see what. I’ve also upgraded to Dude 4b3 and continue to have the same issue… Suggestions appreciated :slight_smile: