This is not really a wireless issue; however my posting on comp.os.ms-windows.networking.tcp-ip didn't yield any responses. As I value the comments here, this seems like a good alternative.
Something happened with an HP dv5215us notebook. Suddenly for no apparent reason, both the wired and wireless interfaces stopped being able to get an IP address through DHCP, and always get that strange Alternate Private IP. The wireless card appears to connect to the AP, but I cannot be sure that it has authenticated correctly. I have done the following to try to resolve the problem:
Booted a Knoppix CD and verified that the wired ethernet interface is working correctly.
Disabled all firewalls.
Cleared the arp cache with a 'netsh interface ip delete arpcache' command.
Deleted the network interfaces in the device manager and rebooted to reinstall them.
Reset the TCP/IP parameters with a "netsh int ip reset resetlog.txt" command.
I would appreciate any further commands to run, or any further data from my machine that is needed.
What do you mean sometimes? Is there something that happens after running some program? I've had XP networking go nuts after going in and out of standby multiple times.
always get that
Is the "strange" IP address 169.254.xxx.xxx ?? If so, that's what Windoze defaults to when it can't get an address via DCHP.
resolve the problem:
Oh, it's a "card". Might it be a PCMCIA, CardBus, or PCIExpress Card? Does this card have a manufacturer and a number?
working correctly.
Good. Nothing has failed.
Do you have more than one firewall? If so, kindly disarm one of them.
Try: arp -d * which is easier to remember. Does the same thing.
Well, plug-n-play is still working.
That's usually the last resort. The problem is that if you have a personal firewall, such as Norton or McAfee installed, it will break the installation requiring a reinstall. It will also remove all the added LSP (layered service provider) entries, which will break many applications.
machine that is needed.
Did steps 1->5 do any good? Does it work now?
I have no idea what to do next. The problem I have is with your one word "sometimes". This implies that it sometimes works. My crystal ball points to some application breaking things. It's not in the wireless or wired device drivers as both apparently fail. Just about any add-on program that installs itself into the LSP networking pretzel may cause things to break. That includes wireless client managers, network diagnostic tools, VPN shims, remote control programs, VNC, browser add-ons, and various debugging programs from card manufacturers. In addition, if you have some persistent spyware installed, it will reinstall itself in the LSP when you reboot. Hard to tell from here.
My wild guess(tm) is you should approach this problem as if you had a virus/trojan/spyware problem and look for extraneous junk in the LSP. I notice that you didn't mention scanning for viruses or spyware. Do it, especially if you haven't bothered to stay up to date with Windoze updates.
SomeTHING, not sometimes. The breakage is solid. It never works now, not even in Safe Mode with Networking..
always get that
Yes, it is.
resolve the problem:
It is a Broadcom BCM4318 mini-PCI card. The ethernet is a Realtek RTL8139 built into the motherboard.
working correctly.
This computer had AOL 9, which has been uninstalled. The built-in Windoze filewall was then disabled.
Thanks for the tip.
machine that is needed.
No, otherwise I wouldn't ask.
It has all of the Windows updates till about a week ago when it broke. Nothing new had been installed just before it broke. Just before I uninstalled AOL 9, I did complete spyware and virus scans that were clean. Of the LSP stuff you mention above, the only things that might be there are browser add-ons and the card debugging stuff.
That is a cool tool. There were some AOL pieces left, but removing them didn't help. The log follows:
Logfile of Trend Micro HijackThis v2.0.2 Scan saved at 1:39:05 PM, on 7/31/2007 Platform: Windows XP SP2 (WinNT 5.01.2600) MSIE: Internet Explorer v6.00 SP2 (6.00.2900.2180) Boot mode: Normal
I found the problem using a tool called LSPFix , which showed that Winsock2 was messed up. A Microsoft help page told me how to reinstall it and all is well now.
Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.