SMS: IP Address Missing from Client Inventory

Last reviewed: March 16, 1998
Article ID: Q157681
1.20 3.11 WINDOWS kbnetwork kbbug1.20 kbfix1.20.sp1

The information in this article applies to:

  • Microsoft Systems Management Server version 1.2
  • Microsoft Windows for Workgroups 3.11

SYMPTOMS

Systems Management Server Inventory Agent fails to report an IP address for Windows for Workgroups 3.11 client and the following error is logged in the Invdos.log file located on the client in the Ms\Sms\Logs directory:

   Executing command: C:\MS\SMS\BIN\ipconfig.exe >
   C:\MS\SMS\TEMP\ipconfig.sms IP address information not found in output
   file

CAUSE

Invdos.exe does not detect TCP/IP inventory while the SMS_P environment variable is present. SMS_P is a temporary variable set in Runsms.bat or Smsls.bat, and is used for storing path detail, during client setup. The variable is then reset during termination of the respective batch file.

MORE INFORMATION

The absence of TCP/IP inventory causes Remote Control using IP sockets to fail. The following message appears during inventory (if it is run in verbose mode by setting SMSLS=1 prior to execution):

   Looking for TCP/IP stack
   Looking for Wolverine stack
   Performing TCP/IP detection
   <drive>:\MS\SMS\BIN\IPCONFIG.EXE > <drive>:\MS\SMS\TEMP\IPCONFIG.SMS
   "IP address information not found in output file"

WORKAROUND

To work around this problem, do the following to Runsms.bat (which resides at \SMS\SITE.SRV\MAINCFG.BOX\CLIENT.SRC) or Smsls.bat (which resides at \SMS\SITE.SRV\MAINCFG.BOX):

  1. Add an additional variable (for example: SMS_P2) to the :START section. For example:

          :START
    

          REM Check to see if we can save path and reserve the necessary
          environment
          REM space before continuing.
          set SMS_P=%PATH%
          set SMS_P2=%PATH%
          set SMS_TEMP=123456789012345678901234567890123456789012345
          if "%SMS_TEMP%"=="123456789012345678901234567890123456789012345" goto
          FIND_OS
          goto LOW_ENV
    

  2. Reset the SMS_P variable prior to execution of Invdos.exe in the :RUN_DOS section. For example:

          :RUN_DOS
          if not exist %0\..\%SMS_BIN%\setls%SMS_OS%.exe goto NOPATHARG0
    

          setls%SMS_OS% -m:E -i -p:%SMS_BIN%\CLI_DOS.EXE -pa:/p:%%SMS_UNC%%\ -
    
             pa:%SMS_VERBOSE% %SMS_VERBOSE%
          set SMS_P=
          setls%SMS_OS% -m:E -i -p:%SMS_BIN%\INVDOS.EXE  -pa:/l:%%SMS_UNC%%\ -
             pa:/i -pa:%SMS_VERBOSE% %SMS_VERBOSE%
          goto RESTORE
    
    

  3. Restore the path from the new variable (SMS_P2) by changing the path line in the :RESTORE section. For example:

          :RESTORE
          REM Restore the previous path setting.
          PATH=%SMS_P2%
          goto END
    

  4. Reset the new variable, instead of SMS_P in the :END section. For example:

          :END
          set SMS_P2=
          set SMS_OS=
    

          set SMS_BIN=
          set SMS_VERBOSE=
    

STATUS

Microsoft has confirmed this to be a problem in Microsoft Systems Management Server version 1.2. This problem has been corrected in the latest U.S. Service Pack for Systems Management Server version 1.2. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K


KBCategory: kbnetwork kbbug1.20 kbfix1.20.sp1
KBSubcategory: smsinv ntconfig
Additional reference words: prodsms 1.20 sms inventory automatic ip tcp/ip tcpip
configuration enabled
Keywords : kbbug1.20 kbfix1.20.sp1 ntconfig smsinv kbfix1.20.sp3
Version : 1.20 3.11
Platform : WINDOWS


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.

Last reviewed: March 16, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.