The information in this article applies to:
SYMPTOMSIf you have two or more network adapters in your computer and you are using Dial-Up Networking to connect to a network using the TCP/IP protocol, you may not be assigned an IP address and may not be able to use a static IP address. When this occurs, running Winipcfg.exe shows an IP address and subnet mask of 0.0.0.0, even though you are connected with the TCP/IP protocol. CAUSE
This problem can occur when you have two or more network adapters
installed with TCP/IP bound to each, and you have TCP/IP bound to the
Dial-Up Networking adapter.
RESOLUTIONThis issue is resolved by the following updated file(s) for Windows 95, and later versions of these file(s):
To work around this problem, follow these steps:
STATUS
Microsoft has confirmed this to be a problem in Microsoft Windows 95. An
update to address this problem is now available, but is not fully
regression tested and should be applied only to computers experiencing
this specific problem. Unless you are severely impacted by this specific
problem, Microsoft does not recommend implementing this update at this
time. Contact Microsoft Technical Support for additional information about
the availability of this update.
MORE INFORMATIONFor additional information about issues resolved by updates to these components, please see the following articles in the Microsoft Knowledge Base: Q165402 Windows 95 Update to Encrypt Passwords in Memory Q158713 Fatal Exception Error Using DHCPFor additional information about Windows 95 updates, please see the following article in the Microsoft Knowledge Base: Q161020 Implementing Windows 95 Updates
Keywords : kbenv kbnetwork kbpolicy dun win95 |
Last Reviewed: June 30, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |