Upgrade your Internet experience

Don't show me this again

Upgrade your Internet experience United States Change | All Microsoft Sites Microsoft Support

Top of Form

Search Microsoft Support Search Microsoft.com Search the web

LCID=1033

r
Bottom of Form

Support Home Solution Centers Advanced Search

Buy products Other Resources

Article ID: 220874 - Last Review: January 24, 2007 - Revision: 5.3

Other Support How to use automatic TCP/IP Sites addressing without a DHCP server Solution Centers
View products that this article applies to. This article was previously published under Q220874

On This Page

Microsoft Fix It Solutions Windows Help and How-to Office Online Microsoft Partner Network

SUMMARY MORE INFORMATION

Examples of Where APIPA May Be Useful

Example 1: No Previous IP Address and no DHCP Community Server Answers Example 2: Previous IP Address and no DHCP Forums Server Technet Forums Example 3: Lease Expires and no DHCP Server Microsoft Expand all | Collapse all Developer Network SUMMARY (MSDN)

This article describes how to use automatic Transmission Control Protocol/Intern...

Get Help Now

This article describes how to use automatic Transmission Control Protocol/Internet Protocol (TCP/IP) addressing without a Dynamic Host Configuration Protocol (DHCP) server being present on the network. The operating system versions listed in the "Applies to" section of this article have a feature called Automatic Private IP Addressing (APIPA). With this feature, a Windows computer can assign itself an Internet Protocol (IP) address in the event that a DHCP server is not available or does not exist on the network. This feature makes configuring and supporting a small Local Area Network (LAN) running TCP/IP less difficult. Back to the top

Contact a Support Professional by Email, Online, or Phone

Article Translations
Top of Form

MORE INFORMATION

Bottom of Form

Important This section, method, or task contains steps that tell you how to modi...
Important This section, method, or task contains steps that tell you how View related content to modify the registry. However, serious problems might occur if you TCP/IP in modify the registry incorrectly. Therefore, make sure that you follow these Windows 200 steps carefully. For added protection, back up the registry before you 0 Professional modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows Search related topics A Windows-based computer that is configured to use DHCP can automatically assign itself an Internet Protocol (IP) address if a DHCP server is not available. For example, this could occur on a network without a DHCP server, or on a network if a DHCP server is temporarily down for maintenance. The Internet Assigned Numbers Authority (IANA) has reserved 169.254.0.0-169.254.255.255 for Automatic Private IP Addressing. As a result, APIPA provides an address that is guaranteed not to conflict with routable addresses. After the network adapter has been assigned an IP address, the computer can use TCP/IP to communicate with any other computer that is connected to the same LAN and that is also configured for APIPA or has the IP address manually set to the 169.254.x.y (where x.y is the clients unique identifier) address range with a subnet mask of 255.255.0.0. Note that the computer cannot communicate with computers on other subnets, or with computers that do not use automatic private IP addressing. Automatic private IP addressing is enabled by default. You may want to disable it in any of the following cases: - Your network uses routers. - Your network is connected to the Internet without a NAT or proxy server. Unless you have disabled DHCP-related messages, DHCP messages Related Support provide you with notification when you change between DHCP addressing Centers and automatic private IP addressing. If DHCP messaging is accidentally Windows disabled, you can turn the DHCP messages back on by changing the value Server 2003 of the PopupFlag value in the following registry key from 00 to 01: Windows

Disable automatic private ip addressing... How to fix automatic ip address in Wind... Auto ip address Disable automatic private ip addressing... How to disable autoconfigura tion enabled

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\D HCP Note that you must restart your computer for the change to take effect. You can also determine whether your computer is using APIPA by using the Winipcfg tool in Windows Millennium Edition, Windows 98, or Windows 98 Second Edition: Click Start, click Run, type "winipcfg" (without the quotation marks), and then click OK. Click More Info. If the IP Autoconfiguration Address box contains an IP address within the 169.254.x.x range, Automatic Private IP Addressing is enabled. If the IP Address box exists, automatic private IP addressing is not currently enabled. For Windows 2000, Windows XP, or Windows Server 2003, you can determine whether your computer is using APIPA by using the IPconfig command at a command prompt: Click Start, click Run, type "cmd" (without the quotation marks), and then click OK to open a MS-DOS command line window. Type "ipconfig /all" (without the quotation marks), and then hit the ENTER key. If the 'Autoconfiguration Enabled' line says "Yes", and the 'Autoconfiguration IP Address' is 169.254.x.y (where x.y is the client's unique identifier), then the computer is using APIPA. If the 'Autoconfiguration Enabled' line says "No", then the computer is not currently using APIPA. You can disable automatic private IP addressing by using either of the following methods.

Server

Windows XP Windows 2000 Server Windows 2000 Windows 2000 Advanced Server Windows 2000 Professional Edition Windows 2000 Datacenter Server Windows Millennium Edition Windows 98

Page Tools You can configure the TCP/IP information manually, which disables DHCP altogether. You can disable automatic private IP addressing (but Print this page not DHCP) by editing the registry. You can do so by adding the E-mail this "IPAutoconfigurationEnabled" DWORD registry entry with a value of 0x0 page to the following registry key for Windows Millennium Edition, Windows98, or Windows 98 Second Edition: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\D HCP For Windows 2000, Windows XP, and Windows Server 2003, APIPA can be disabled by adding the "IPAutoconfigurationEnabled" DWORD registry entry with a value of 0x0 to the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\P arameters\Interfaces\<Adapter GUID> Note The Adapter GUID subkey is a globally unique identifier (GUID) for the computer's LAN adapter. Specifying a value of 1 for IPAutoconfigurationEnabled DWORD entry will enable APIPA, which is the default state when this value is omitted from the registry. Back to the top

Examples of Where APIPA May Be Useful

Example 1: No Previous IP Address and no DHCP Server When your Windows-based computer (configured for DHCP) is initializing, it broadcasts three or more "discover" messages. If a DHCP server does not respond after several discover messages are broadcast, the Windows computer assigns itself a Class B (APIPA) address. Then the Windows computer will display an error message to the user of the computer (providing it has never been assigned an IP address from a DHCP server in the past). The Windows computer will then send out a Discover message every three minutes in an attempt to establish communications with a DHCP server. Example 2: Previous IP Address and no DHCP Server The computer checks for the DHCP server and if none are found, an attempt is made to contact the default gateway. If the default gateway replies, then the Windows computer retains the previously-leased IP address. However, if the computer does not receive a response from the default gateway or if none are assigned, then it uses the automatic private IP addressing feature to assign itself an IP address. An error message is presented to the user and discover messages are transmitted every 3 minutes. Once a DHCP server comes on line, a message is generated stating communications have been re-established with a DHCP Server. Example 3: Lease Expires and no DHCP Server The Windows-based computer tries to re-establish the lease of the IP address. If the Windows computer does not find a DCHP server, it assigns itself an IP address after generating an error message. The computer then broadcasts four discover messages, and after every 5 minutes it repeats the whole procedure until a DHCP server comes on line. A message is then generated stating that communications have been re-established with the DHCP Server. Back to the top
APPLIES TO

Microsoft Windows Server 2003, 64-Bit Datacenter Edition Microsoft Windows Server 2003, Enterprise x64 Edition Microsoft Windows Server 2003, Datacenter Edition (32-bit x86) Microsoft Windows Server 2003, Enterprise Edition (32-bit x86) Microsoft Windows Server 2003, Web Edition Microsoft Windows XP Home Edition Microsoft Windows XP Professional Microsoft Windows XP Tablet PC Edition Microsoft Windows 2000 Server

Microsoft Windows 2000 Advanced Server Microsoft Windows 2000 Professional Edition Microsoft Windows 2000 Datacenter Server Microsoft Windows Millennium Edition Microsoft Windows 98 Second Edition Microsoft Windows 98 Standard Edition

Back to the top Keywords: kbhowto kbnetwork KB220874 Back to the top
1
132 0

9089

LABEL

Provide feedback on this information

9088 CHOICE 0

Did this information solve your problem?

Yes No I don't know

9086 CHOICE 0

Was this information relevant?

Yes No
9087 TEXT-BLOCK 0

What can we do to improve this information?

7813

LABEL

To protect your privacy, do not include contact information in your feedback. Thank you! Your feedback is used to help us improve our support content. For more assistance options, please visit the Help and Support Home Page.

Get Help Now

Contact a support professional by E-mail, Online, or Phone Microsoft Support Feedback | Services Agreement Contact Us | Terms of Use | Trademarks | Privacy Statement 2010 Microsoft