Automate Setup to Configure TCP/IP for Static Addressing Fails

Last reviewed: March 21, 1997
Article ID: Q133337

The information in this article applies to:

   - Microsoft Windows NT Workstation versions 3.5 and 3.51
   - Microsoft Windows NT Server versions 3.5 and 3.51

SYMPTOMS

The TCP/IP protocol is configured for DHCP addressing instead of static addressing after you install Windows NT.

This problem occurs when you install TCP/IP using the unattended setup feature of Windows NT Setup or Computer Profile Setup (CPS) after you set !UpgradeEnableDHCP equal to NO in the answer file, UNATTEND.TXT.

NOTE: The file UNATTEND.TXT is available on the compact disc shipped with the Windows NT 3.5 Resource Kit. For additional information about the unattended Setup feature, see the Windows NT 3.5 Resource Kit, Volume 1, pages 99 - 100. For additional information about Computer Profile Setup (CPS), see the Windows NT 3.5 Resource Kit, Volume 1, pages 67 - 69.

CAUSE

OEMNXPTC.INF does not check your answer file for the !UpgradeEnableDHCP value and by default configures TCP/IP for DHCP addressing.

RESOLUTION

To resolve this problem, modify the IPINFO.INF and OEMNXPTC.INF files.

To automatically configure TCP/IP for static IP addressing when you use an answer file with Windows NT Setup or when you use CPS:

WARNING: Modification of INF files can cause serious, system-wide problems before and after Setup and may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the modification of INF files can be solved. Make INF modifications at your own risk.

  1. Copy the \I386 directory from the Windows NT compact disc to your hard drive.

  2. Expand the compressed versions of the IPINFO.INF and OEMNXPTC.INF files using the EXPAND.EXE command.

    The EXPAND.EXE file is located in the %SystemRoot%\SYSTEM32 directory.

  3. Make a backup copy of the IPINFO.INF and OEMNXPTC.INF files.

  4. If you are running Windows NT 3.5, copy the OEMNXPTC.INF file from Windows NT 3.51 over your current copy. If you do not have Windows NT 3.51, contact Microsoft Product Support Services.

  5. Modify the IPINFO.INF file to include the appropriate static IP values in the [DefaultIPInfo] section. For additional information on how to do this, please see the following article(s) in the Microsoft Knowledge Base:

    ARTICLE-ID: Q135463

       TITLE     :IPINFO.INF Values Ignored During Setup
    
       Note: Do not pad IP addresses with leading zeroes. This can result in
       incorrect address assignments and cause unexpected behavior.
    
    

  6. In OEMNXPTC.INF, search for the [InstallOptions] heading to find the following problem code fragment:

           ifstr(i) $(!STF_GUI_UNATTENDED) == YES
    
              set EnableDHCPFlag = 1
           endif
           ifstr(i) $(EnableDHCPFlag) == ""
              set EnableDHCPFlag = 0
           endif
    
    

  7. Modify the second line so that the EnableDHCPFlag is set to 0 as in the following example:

          ifstr(i) $(!STF_GUI_UNATTENDED) == YES
    
             set EnableDHCPFlag = 0
          endif
          ifstr(i) $(EnableDHCPFlag) == ""
             set EnableDHCPFlag = 0
          endif
    
    

  8. To take advantage of the changes you made, run Setup from the directory on your hard drive.

Computer Profile Setup:

Make the above modifications to IPINFO and OEMNXPTC.INF on the Master System before running UPLODPRF.EXE.


Additional query words: prodnt upgrade
Keywords : kbbug3.51 kbnetwork kbsetup nthowto ntsetup
Version : 3.5 3.51
Platform : WinNT


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 21, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.