It looks like you've already done a fair bit of troubleshooting yourself. I think your best bet for this particular issue is to open a support ticket so we can get additional discovery logs and try to reproduce in-house.
Just from the sounds of the situation, I would recommend the following:
- From within "Device Tab > Discovery > Previously Scan Results", select the DMZ server and delete it
- Next, from "Device Tab > Add New Device", supply the address / community / and network credential (*possible)
- Let it rescan and click the "modify button" to review everything it found.
- Let us know if that gets you any further / If support moves you along one step further?
* Note: You can establish a trust relationship using the following technique:
- Create a local account (on the ipMonitor host) with a specific account name and password
- Create an identical local account (including password) on the DMZ server
- Use the credential wizard within the "Add New Device" page (Select Credential > New Credential) to register this account and password within ipMonitor for use.
Thanks for your replies, Chris and Peter. I'm out of the office for a few days but I'll try your suggestions on my return.
I tried your suggestion of deleting the previously scanned server and adding it as a new device using it's IP address. This worked fine and offered up a bunch of monitors to add (ping, pop3, smtp, ftp, http).
Do you have any idea why ipMonitor will scan one way but not the other?
Thanks - Simon
Under the hood, it's the same stuff. I'm going to stretch and suggest maybe an invalid reverse DNS entry got picked up through the discovery pass (where possible we'll try using DNS names to configure new Monitors so the cost to maintain your installation is less over time).
I'll check that out and see if DNS is to blame.
Thanks for all your excellent help,