Network card stopped working

31 Jul 2006 3:28 AM

Fred

My wife has a Dell Dimension 2350 with an integrated Broadcom
440x NIC. It was working fine, then when we returned from dinner,
she had no network access. You cannot ping any external IP
addresses, either on our home network or the Internet. You can
ping the loopback device 127.0.0.1, and also her private IP
address 192.168.1.33. I've eliminated Windows as being the
culprit by booting with a Linux CD, and found I could still
not ping an IP address. I installed a spare 3-Com NIC in an
available PCI slot. I encountered the same problem with the
3-Com NIC. Here are some of the things I've tried while
troubleshooting:

-Cannot ping any IP address except for itself, even the
default gateway.
-Disabled Trend Micro and Windows firewall.
-Confirmed NIC link light activity, on router sice too.
The link light on the NIC is flashing.
-Removed RJ-45 cable from wife's PC and connected to
my PC - Connection is OK.
-Updated the Broadcom 440x driver from 3.4x to 3.63
-Installed 3-Com NIC in PCI slot, but had no connectivity
through this NIC either.
-Ran Broadcom diagnostics software, all tests passed.
-Booted from Linux CD to rescue mode with networking,
and still could not ping IP addresses.
-Checked router (firewall) is not blocking Wife's packets.

Has anyone else experienced problems with the Broadcom 440?

-Thanks

31 Jul 2006 3:48 PM

Doug Sherman [MVP]

Your description suggests that the problem is more likely TCP/IP rather than
the adapter. Try netsh winsock reset:

http://support.microsoft.com/default.aspx?scid=kb;en-us;299357

Doug Sherman
MCSE, MCSA, MCP+I, MVP

Show quoteHide quote

"Fred" <itf***@cdw.com> wrote in message
news:2cCdnQsoFIdl5VDZnZ2dnUVZ_rKdnZ2d@giganews.com...
> My wife has a Dell Dimension 2350 with an integrated Broadcom
> 440x NIC. It was working fine, then when we returned from dinner,
> she had no network access. You cannot ping any external IP
> addresses, either on our home network or the Internet. You can
> ping the loopback device 127.0.0.1, and also her private IP
> address 192.168.1.33. I've eliminated Windows as being the
> culprit by booting with a Linux CD, and found I could still
> not ping an IP address. I installed a spare 3-Com NIC in an
> available PCI slot. I encountered the same problem with the
> 3-Com NIC. Here are some of the things I've tried while
> troubleshooting:
>
> -Cannot ping any IP address except for itself, even the
> default gateway.
> -Disabled Trend Micro and Windows firewall.
> -Confirmed NIC link light activity, on router sice too.
> The link light on the NIC is flashing.
> -Removed RJ-45 cable from wife's PC and connected to
> my PC - Connection is OK.
> -Updated the Broadcom 440x driver from 3.4x to 3.63
> -Installed 3-Com NIC in PCI slot, but had no connectivity
> through this NIC either.
> -Ran Broadcom diagnostics software, all tests passed.
> -Booted from Linux CD to rescue mode with networking,
> and still could not ping IP addresses.
> -Checked router (firewall) is not blocking Wife's packets.
>
>
> Has anyone else experienced problems with the Broadcom 440?
>
> -Thanks
>

1 Aug 2006 12:18 AM

Fred

On Mon, 31 Jul 2006 11:48:36 -0400, Doug Sherman [MVP] wrote:

> Your description suggests that the problem is more likely TCP/IP rather than
> the adapter. Try netsh winsock reset:
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;299357
>
> Doug Sherman
> MCSE, MCSA, MCP+I, MVP
>

This sounds dangerous. My wife has a VPN network connection she
uses to connect to work. Would it reset the VPN TCP/IP stack as
well?

-Thanks

1 Aug 2006 5:50 PM

Doug Sherman [MVP]

Well, the command would be: netsh winsock reset catalog

And - yes - it is dangerous. But if you have no network or Internet
connectivity, you don't have much to lose. Are you saying that your wife's
VPN connection is still working?

For more info go here:

http://windowsxp.mvps.org/winsock.htm

Doug Sherman
MCSE, MCSA, MCP+I, MVP

Show quoteHide quote

"Fred" <itf***@cdw.com> wrote in message
news:pIOdnQy4jeFWAFPZnZ2dnUVZ_tWdnZ2d@giganews.com...
> On Mon, 31 Jul 2006 11:48:36 -0400, Doug Sherman [MVP] wrote:
>
> > Your description suggests that the problem is more likely TCP/IP rather
than
> > the adapter. Try netsh winsock reset:
> >
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;299357
> >
> > Doug Sherman
> > MCSE, MCSA, MCP+I, MVP
> >
>
>
> This sounds dangerous. My wife has a VPN network connection she
> uses to connect to work. Would it reset the VPN TCP/IP stack as
> well?
>
>
> -Thanks
>