RIS Installation Stops if the Network Cable Uses Port B of a Dual-Port Network Adapter (814788)
The information in this article applies to:
- Microsoft Windows 2000 Advanced Server SP3
- Microsoft Windows 2000 Advanced Server SP2
- Microsoft Windows 2000 Advanced Server SP1
- Microsoft Windows 2000 Server SP3
- Microsoft Windows 2000 Server SP2
- Microsoft Windows 2000 Server SP1
- Microsoft Windows 2000 Professional SP3
- Microsoft Windows 2000 Professional SP2
- Microsoft Windows 2000 Professional SP1
SYMPTOMSWhen you connect to a Remote Installation Server (RIS) from
port B of a dual-port network adapter, Setup may appear to stop responding
(hang) at the "Setup is starting Windows 2000" screen. However, switching the
network cable to port A of the network adapter makes it possible for Setup to
continue.CAUSEDuring the PXE boot, the network adapter is identified, and
the Windows 2000 network adapter driver is copied over and prepared for
initialization. After the kernel and the network adapter are initialized, the
file copy process continues. Port B connectivity is lost during the network
adapter initialization because of the PXE device map encoding information that
is passed to the kernel does not match the PCI device map encoding information.
Because of this, the default port (A) is initialized instead of port
(B)RESOLUTIONService Pack InformationTo resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
Hotfix InformationA supported fix is now available
from Microsoft, but it is only intended to correct the problem that is
described in this article. Apply it only to computers that are experiencing
this specific problem. This fix may receive additional testing. Therefore, if
you are not severely affected by this problem, Microsoft recommends that you
wait for the next Windows 2000 service pack that contains this hotfix. To
resolve this problem immediately, contact Microsoft Product Support Services to
obtain the fix. For a complete list of Microsoft Product Support Services phone
numbers and information about support costs, visit the following Microsoft Web
site: NOTE: In special cases, charges that are ordinarily incurred for
support calls may be canceled if a Microsoft Support Professional determines
that a specific update will resolve your problem. The typical support costs
will apply to additional support questions and issues that do not qualify for
the specific update in question. The English version of
this fix has the file attributes (or later) that are listed in the following
table. The dates and times for these files are listed in coordinated universal
time (UTC). When you view the file information, it is converted to local time.
To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. Date Time Version Size File name
---------------------------------------------------------
24-02-2003 15:42 5.0.2195.6670 1,692,352 Ntkrnlmp.exe
24-02-2003 15:42 5.0.2195.6670 1,670,080 Ntoskrnl.exe
04-02-2003 12:15 5.0.2195.6661 29,264 Mountmgr.sys STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
This problem was first corrected in Microsoft Windows 2000 Service Pack 4.
Modification Type: | Minor | Last Reviewed: | 10/10/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbsetup kbWin2kSP4fix kbprb kbWin2000preSP4Fix kbfix kbpending kbbug KB814788 |
---|
|