- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-16-2020 12:38 PM
Hi All,
we are doing windows server discovery through out the enterprise network and it's working fine. But for one windows server we are getting credential Time out error, And we can able to login to the server using RDC. And we know there is no Firewall block and port 135 is also open for the server.
And when we run the simple WMI command from the MIDserver Host we are getting error like "No such Interface supported". So after reviewing the error from below KB article, it seems like Firewall issue, But the port is open.
https://hi.service-now.com/kb_view.do?sysparm_article=KB0787202
So please me out to get this issue resolved.
Thanks in Advance.
Best regards
CG.
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2020 12:08 PM
One other thing to check on the high ports. Are all the Windows servers using the same version of windows? I didn't provide the high ports for older versions of Windows, because most organizations have since upgraded. The high port requirements are different for different versions of windows for WMI:
High Ports 1025 - 5000
Windows 2000
Windows XP
Windows Server 2003
High Ports 49152 - 65535
Windows Server 2008 and later versions
Windows Vista and later versions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2020 10:44 PM
Thanks Chuck for your response, Let me check the points you mentioned above.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2020 12:08 PM
One other thing to check on the high ports. Are all the Windows servers using the same version of windows? I didn't provide the high ports for older versions of Windows, because most organizations have since upgraded. The high port requirements are different for different versions of windows for WMI:
High Ports 1025 - 5000
Windows 2000
Windows XP
Windows Server 2003
High Ports 49152 - 65535
Windows Server 2008 and later versions
Windows Vista and later versions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-03-2020 06:17 AM
Thanks Chuck, we have servers after 2008 only.. so requested to open high ports from 49152-65535
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-07-2020 06:00 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-08-2020 09:24 AM
I experienced this same issue in my environments. Most of the failures I saw were on windows VCOs (related to clusters and file shares). The short answer is the admin$ share is not accessible on VCOs on Windows server 2012 and above.
More details on my findings are available in my community inquiry: https://community.servicenow.com/community?id=community_question&sys_id=b27ddacfdb330c5814d6fb243996...