Solved No network interface, DP43BF, new system

[cycleguy]

Hello (first post!),

I've been building a new system in my spare time. I put in the specs when I registered. Bought the motherboard in March, other parts later on.

People suggested Intel had goofy bus enumeration on this board (for no reason at all?), so Linux won't see the PCI slots. They were right. Linux may also require compiling code from Broadcom's site before the motherboard's LAN chip will work.

This was looking to be too difficult, so I bought an OEM license for Seven (64-bit, Professional). Right after installing, I put the Intel CD in the drive, and installed chip driver, LAN chip driver, etc. These might have had problems (rebooting fewer times than normal, installation not registering properly), I am not sure. I removed and reinstalled at least once. (I think 12.4.XX is what I have now.)

When I try to surf, IE can't find the web page. When I run Win 7's network troubleshooter, it thinks a network cable is disconnected. The router DID in fact give my Intel machine a dotted quad (192.168.1.133, I checked the router's internet interface from another machine).

I am running the default Windows services and the default HOSTS file on this new build. I am NOT activating Seven until this is fixed.

BTW, both Windows and Linux work on this machine with a USB wifi dongle. That's how I got to Windows Update to patch the Intel box. I got an updated LAN chip driver file from Intel's site, but it did not resolve the problem.

Yes, I have the ipconfig output. It is here:

C:\Users\Mike>ipconfig /all

Windows IP Configuration

  Host Name . . . . . . . . . . . . : Mikes-Quad-Core
  Primary Dns Suffix  . . . . . . . :
  Node Type . . . . . . . . . . . . : Hybrid
  IP Routing Enabled. . . . . . . . : No
  WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet
  Physical Address. . . . . . . . . : Yes
  DHCP Enabled. . . . . . . . . . . : Yes

Tunnel adapter isatap.{E312BBA8-6F9B-49AE-8709-669277D05FBD}:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
  Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
  Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes

C:\Users\Mike>

What do you say? No DNS? Bad LAN chip (Broadcom Gigabit 57788)? Bad products do slip out, I know (*cough* PC Power & Cooling *cough*).

Any further tests I need to do? I really don't want to get stuck with memory and an expensive processor that I can't use. If this happens, I'll probably get a Mac.

P.S.: I installed XP 64-bit briefly (delete "test" installs quickly, respect software licenses!). It had the same symptoms, just different dialog boxes (didn't write down). And 3-4 Linux distributions didn't see the LAN chip either.

 

[cycleguy]

Got it working.....

I got it working under Win 7. Linux will have to wait for another day.

I got a networking cable (gray, with blue tape extending 2-3 inches from each end) that only had 4 connectors, not 8. They are the 4 connectors in the center. I suppose I *_could_* use it for a US-style RJ-11 telephone cord. Someone on another forum suggested this 4-wire setup was used for old 10/10-base-T networking.

Anyway, replacing it with an 8-conductor cable (regular OR crossover) fixed things. In Windows. Windows works, so linux (and getting linux to see the PCI slots) can wait for now.

Thanks!