Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

Craftymama51

15 Posts

70577

July 17th, 2007 00:00

Re: Network adapter useless after lightning strike.

I need help on the same subject. Lightning struck near my house on Saturday and since then, I can't connect using broadband. I also have Intel Pro/100 VE running on Windows XP SP2 I called Bellsouth and we established that the modem (Westell 6100) is working and the Pro 100 seems to be working but I get the 169.254.xxx.xxx address. My Pro/100 diagnostics passes all but the link test. We switched to USB cable and that worked for a few hours, but I got the same result so I switched back to ethernet.I've run WinsockFix, LSPFix, downloaded the MS patch for SP2, uninstalled the Pro/100, done the winsock reset. It just won't renew the IP. I use Bellsouth PPOE and I'm out of ideas. There are no new drivers for the Pro/100 VE. Would a static Ip help? I've run this DSL for months with no problem and now I have a Microsoft headache. Could anyone help, please?

volcano11

2 Intern

 • 

28K Posts

July 17th, 2007 01:00

If it doesn't pass the link test, then it will never connect.  It's entirely possible that the lightning strike fried your ethernet adapter.   A cheap troubleshooting step would be to buy a PCI network adapter and see if that works (they can be found for less than $10).  Be aware, however, that since the Intel adapter is integrated on the motherboard, and if it is fried, then there could also be other problems with your motherboard.  If the new network card doesn't work in the PCI slot in which your install it, try a different slot.
 
Steve

Craftymama51

15 Posts

July 17th, 2007 02:00

Also I don't think the lightning sturck my computer. Our phone lines are buried and I didn't notice even a flicker. I turned it off when the storm approached and It was an hour or so after I turned it back on that it started doing that. Then the USB worked for several hours before it quit. Sometimes it would say connected but could not bring up a page. Most of the time it says limited or no connectivity.

Craftymama51

15 Posts

July 17th, 2007 02:00

Hi Steve,
The last diagnostics I ran the link passed too. I can ping all valid addresses, and packets are sent, none received. If the network card was damaged, I would think I would get an error somewhere. The only problem is the renewing of the IP address. I keep getting the 169 address. I've read so many posts about this problem and tried most of the solutions. I guess a PCI card is better than dial up. But I sure would like to know what the problem is as so many have it and for so many different reasons.
Jane

Iceman188

8 Posts

July 19th, 2007 09:00

These things can be hard to solve. I had the same problem once with a DLS modem which would not connect but still passed every diagnostics. I was lucky that a neighbour had the same modem. After I switched devices, it worked, so in that way, I could prove that it was in fact the modem that created the problem.
 
Still, sometimes the stupid and easy things are overlooked. Did you check if you are still using DHCP. Could it be you have set up a static IP address???
 

Craftymama51

15 Posts

July 19th, 2007 10:00

This is my current configuration
 
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
Windows IP Configuration
        Host Name . . . . . . . . . . . . : Craftymama51
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection 7:
        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connecti
on
        Physical Address. . . . . . . . . : 00-16-76-13-49-63
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        Autoconfiguration IP Address. . . : 169.254.224.129
        Subnet Mask . . . . . . . . . . . : 255.255.0.0
        Default Gateway . . . . . . . . . :
PPP adapter Bellsouth:
        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
        Physical Address. . . . . . . . . : 00-53-45-00-00-00
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 68.210.234.201
        Subnet Mask . . . . . . . . . . . : 255.255.255.255
        Default Gateway . . . . . . . . . : 68.210.234.201
        DNS Servers . . . . . . . . . . . : 205.152.37.23
                                            205.152.144.23
        NetBIOS over Tcpip. . . . . . . . : Disabled
 
 
 
 
No my Modem is set to obtain IP automatically. I've been through everything a hundred times. Yesterday I did a Windows repair from my CD and it still does the same thing. I've come to the conclusion it's my network connection. I've ordered a PCI adapter, and when it gets here I will let you know for sure.

Iceman188

8 Posts

July 19th, 2007 18:00

You can try the PCI adapter to be sure. Although, this does not explain why it also doen not work when you connect via USB (in priciple, you are not using the Ethernet at that point).
 
Can you ping the Westell 6100 on its IP address (should be 192.168.1.1 or look in the user documentation for the appropriate address).
 
When you access the menu, can you see that it has actualy established a PPP session.
 
Did you try to reset the modem to the default settings?
 
 
 
Hope you will eventually find the problem and fix it. 

Craftymama51

15 Posts

July 19th, 2007 20:00

I could ping the modem for a while. Now it says request timed out on all addresses. If the adapter doesn't work, I'll just reinstall Windows. When I talked with the Bellsouth tech, the modem was working and the network connection, but no connectivity. Don't know whether to just get a static IP or not. But I love a technology challenge and this isn't the worst one I've had.
Thanks

Craftymama51

15 Posts

July 25th, 2007 00:00

Well, I'm back. After installing PCI card and reinstalling windows, I still have the same problem. I have to think it's something with the configuration of TCP/IP and/or DHCP. I really wish someone had an answer for this.
 

Craftymama51

15 Posts

July 25th, 2007 02:00



Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner.CRAFTYMAMA51>ipconfig /all
Windows IP Configuration
        Host Name . . . . . . . . . . . . : craftymama51
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : Yes
        WINS Proxy Enabled. . . . . . . . : No
PPP adapter Bellsouth:
        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
        Physical Address. . . . . . . . . : 00-53-45-00-00-00
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 66.20.136.153
        Subnet Mask . . . . . . . . . . . : 255.255.255.255
        Default Gateway . . . . . . . . . : 66.20.136.153
        DNS Servers . . . . . . . . . . . : 205.152.37.23
                                            205.152.144.23
        NetBIOS over Tcpip. . . . . . . . : Disabled
Ethernet adapter Local Area Connection 4:
        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connecti
on
        Physical Address. . . . . . . . . : 00-16-76-13-49-63
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        Autoconfiguration IP Address. . . : 169.254.224.129
        Subnet Mask . . . . . . . . . . . : 255.255.0.0
        Default Gateway . . . . . . . . . :
 
The same as it was before. But I've been doing some research, and I have no host files. This is what I have in C:\windows\system32\drivers\etc\hosts
 
# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host
127.0.0.1       localhost
 
It's the same in all the host files, just like a tutorial on the files, but no actual files. Could I possibly put my launchmodem IP in and get connected to the modem interface and be updated? And if I do put it in, where would I save it? In this file  c:\windows\system32\drivers\etc\hosts? I've never done this before.

 

volcano11

2 Intern

 • 

28K Posts

July 25th, 2007 02:00

If you reinstalled Windows, the TCP/IP properties and DNS properties would be at their default values (unless you changed something).  Everything should work with the default values.  This would eliminate Windows or software (unless you installed some software that would be interfering) as being a problem. Did you install any other sofware besides Windows?  If so, what? 
 
Post the ipconfig /all output again just to see if there are any problems there. 
 
Steve

volcano11

2 Intern

 • 

28K Posts

July 25th, 2007 03:00

How were you connected when you ran the ipconfig /all command? 
 
I don't see any evidence of a PCI network adapter.  Didn't you say you installed one?
 
Lack of a Hosts file is not the problem.  It was connected to the internet when you ran the ipconfig command, so the internet does work just not through your network adapter.  Stop trying to be creative with the hosts file - it will not solve the problem.
 
Steve

Craftymama51

15 Posts

July 25th, 2007 15:00

I'm not trying to be creative. I'm just asking a question because I don't know much about broadband. Anyway, I uploaded my last Net Diagnostics with both NIC's enabled. Here is the link as it was too large to paste here.
 
 
The one thing that I noticed is an "invalid IP address" on DHCP servers. But I don't know what most of the info is supposed to say./

volcano11

2 Intern

 • 

28K Posts

July 25th, 2007 17:00

Your link takes me to a page that says:
 

No shared folders are available.

Sorry, the owner has not enabled any shared folders in their account.

Steve

Craftymama51

15 Posts

July 25th, 2007 21:00

volcano11

2 Intern

 • 

28K Posts

July 26th, 2007 23:00

In my opinion, I think you need to find a way to test your modem.  Bell South cannot do this from their end.   They would have to come out and do it.  Alternatively, if you know someone with a laptop or if you have another computer, you could check it with that.
 
Steve

Was this post helpful?

View All

No Events found!

Top