Why is the Subnet Mask and DHCP Status not Resolved

Follow

Q: When refreshing a target system with Lieberman products, the subnet mask and DHCP status is not properly identified. Why?

A: The subnet mask and DHCP status are resolved via remote registry call. If the target system's remote registry service is disabled, not running, or remote registry access is otherwise not permitted by the calling user (user running the Lieberman product), the subnet mask and DHCP status will be empty or represented with a question mark (?).

Was this article helpful?
0 out of 0 found this helpful

Comments

Powered by Zendesk