DOCUMENT:Q226848 22-OCT-2000 [sms] TITLE :SMS: Network Discovery Doesn't Time Out After Failed RPC Call PRODUCT :Microsoft Systems Management Server PROD/VER::2.0 OPER/SYS: KEYWORDS:kbsms200 kbsms200bug ====================================================================== ------------------------------------------------------------------------------- The information in this article applies to: - Microsoft Systems Management Server version 2.0 ------------------------------------------------------------------------------- SYMPTOMS ======== Network Discovery does not time out as expected if a network resource such as a Dynamic Host Configuration Protocol (DHCP) server or a workstation does not respond to a remote procedure call (RPC). You may see the following lines repeatedly in the NetDisc.log: ADM: Returning busy from idle status due to outstanding networks in our presence. ADM: Returning busy from idle status due to DHCP thread being busy. DC: Protocol module reports it is still busy while checking idle state. STATUS ====== Microsoft has confirmed this to be a problem in Systems Management Server version 2.0. MORE INFORMATION ================ In configurations earlier than Systems Management Server Service Pack 1, if a network resource (such as a DHCP server or a workstation) fails to return an RPC call issued from Network Discovery, no discovery data records (DDRs) are created. Network Discovery sites for Systems Management Server Service Pack 1 and later create DDRs for all resources it discovers before the unsuccessful RPC call. Additional query words: prodsms ====================================================================== Keywords : kbsms200 kbsms200bug Technology : kbSMSSearch kbSMS200 Version : :2.0 Issue type : kbbug ============================================================================= THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY. Copyright Microsoft Corporation 2000.