Windows Server Discovery Fails with RPC Error When Using IP Address but Works with Hostname
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday - last edited yesterday
Hi All,
We are facing an issue with Windows Server Discovery in ServiceNow and would appreciate your suggestions.
We have configured Windows Server Discovery, but the credential test is failing. The same credentials work successfully when connecting to the target server through RDP.
We also executed the following PowerShell command from the MID Server:
gwmi win32_operatingsystem -computer SERVER_IP
When we use the IP address, we receive the error "The RPC server is unavailable" with error code 0x800706BA.
However, when we use the hostname instead of the IP address, the same command works successfully.
Has anyone encountered a similar issue? Could this be related to firewall rules, RPC dynamic ports, WMI/DCOM configuration, or Windows authentication when connecting using an IP address?
Please suggest what we should check on the MID Server and target Windows server to identify the root cause.
Thanks in advance for your help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday - last edited yesterday
attached screenshot
