This knowledge base article explains how assets are identified as Windows computers. We mostly check port 135. If this port is open, the asset is deemed to be a Windows computer. If this port is closed, the asset is deemed to be non-Windows.
If your web server is incorrectly identified as Windows or generating an RPC error, which is indeed a Windows error, you'll need to:
Ensure that port 135 is closed on the server. You can check open ports with the devicetester tool mentioned in this knowledge base article.
If a Windows asset was generated for the server, delete the faulty asset by clicking the Assets link at the top of the web console, ticking the checkbox in front of the asset and hitting the Delete button on the left.
Rescan the server by hitting the Scan All Enabled IP Ranges Now button under Configuration\Scanning Methods.
This knowledge base article explains how assets are identified as Windows computers. We mostly check port 135. If this port is open, the asset is deemed to be a Windows computer. If this port is closed, the asset is deemed to be non-Windows.
If your web server is incorrectly identified as Windows or generating an RPC error, which is indeed a Windows error, you'll need to:
Ensure that port 135 is closed on the server. You can check open ports with the devicetester tool mentioned in this knowledge base article.
If a Windows asset was generated for the server, delete the faulty asset by clicking the Assets link at the top of the web console, ticking the checkbox in front of the asset and hitting the Delete button on the left.
Rescan the server by hitting the Scan All Enabled IP Ranges Now button under Configuration\Scanning Methods.