Member Avatar for Jodean

my rma'd mother board just arrived back and works but the on board lan does not.

its really not worth rma'ing again.

Ive tried the three old cards i have and windows wont install them.....xp will install them, windows me, 98, 95, millenium etc....

do i have to buy a certain NIC??? No specs list x64 compatability

Do i use 2003 drivers???]

whats the deal

Joe

  • 3 Contributors
  • 2 Replies
  • 98 Views
  • 2 Weeks Discussion Span
  • Latest Post Latest Post by jbennet

Dani AI

Generated

Quick summary tied to the thread: the RMA board's LAN failing while the same NICs worked under 32-bit XP points to a driver/bitness mismatch or a hardware fault. and are on the right track about the 64-bit driver situation; the practical next steps are to verify hardware, identify the exact NIC chipset, and install a matching 64-bit driver (Server 2003 x64 / XP x64 driver family), or fall back to a known-supported add-in card.

Practical checklist (apply in order):

  • Hardware basics: check the LAN port LEDs with a good cable and switch; confirm the onboard NIC is enabled in BIOS; reseat or swap the PCI cards to verify they still work in another machine (confirms the cards themselves).

  • Identify the NIC: in Device Manager open the problem device, Properties -> Details -> Hardware Ids and copy the VEN/DEV string (example format: PCI\VEN_8086&DEV_100E). Use that exact ID to find the chipset/vendor and the correct 64-bit driver package.

  • Driver sources and install: look on the motherboard OEM downloads page and the chipset/NIC vendor (Intel, Broadcom, Realtek, Marvell) for a Server 2003 x64/XP x64 driver. Install manually via Device Manager -> Update driver -> Browse my computer -> Let me pick -> Have Disk and point to the driver INF folder.

  • Driver signing and bitness: XP x64 enforces 64-bit kernel-mode drivers and is stricter about digital signatures. If an installer is blocked, the likely causes are wrong bitness or unsigned kernel drivers; a temporary F8 boot option can disable signature enforcement for testing, but the long-term fix is a signed 64-bit driver.

If no 64-bit drivers exist for the onboard chipset, a low-cost Intel PRO/100/1000 PCI/PCIe adapter (confirm the vendor page lists Server 2003 x64 drivers before buying) is often the fastest reliable workaround. If the port never shows link activity and the device is absent from Device Manager even after reseating, the board NIC may still be faulty and another RMA or an add-in NIC is the realistic solution.

Recommended Answers

All 2 Replies

Member Avatar for Major Major

Windows XP64 has the same build version as windows server 2003 64 bit. Try the 64 bit 2003 drivers some should work. I've got a DLink NIC at home it works well, they had 64-bit drivers. The Marvell Yukon GigE on board Port didn't have 64bit drivers when I built the system and I haven't gone looking for them since.

Member Avatar for jbennet

xp 64 has really bad driver support

vista 64 is much better

and yeah, use 2003 drivers. XP 64 doesnt actually run xp, its server 2003 - server bits

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.