Posted on 07/09/2019 11:34:13 AM PDT by Allen In Texas Hill Country
I'm at my wits end and this is for a super tech which I am not. Wife broke her netbook so as usual I bought a used laptop. A Dell Latitude E6410. Machine looks in good shape and comes right up. Only trouble is it will not connect to my home network. It did connect once or twice in the last 3 days I've been fighting it. But for all intents and purposes it comes back with either unidentified network and/or maybe a 169.254.178.126 in the IPv4 slot. No internet access. I run ipconfig all the time. It also shows 4 or 5 entries called Tunnel Adapter this or that. Never have seen Ipconfig entries like that in XP. Win 7 is another world. :<((((
And the little circle keeps going round and round. Lower right hand corner of the screen over the connection icon. It connects to that stupid 169.xxx.xxx.xxx and must disconnect and try connecting again. Really crazy/confusing.
I called a support number and they asked me to take it to another wifi place and try it. Went to Wendy's yesterday and it worked. :<((((
I've had a Netgear WNDR4000 router forever. Two desktops (XP PROs), tablet, another laptop (VISTA) and the netbook that was broke all talked to the router OK.
Lastly I also intermittently get the IP address conflict box.
You can always try ipconfig /release then ipconfig /renew from the command prompt.
Get a new router and spring for new cables also! Good lu k
I forget to add that the router sees the laptop (mac address) but the device name and ip address are blank.
Tried rebooting both the laptop and router?
Power cycling the home network equipment would be my guess also.
Your mileage may vary:
i never could get the intel dual band wireless-ac 8260 chipset to work reliably in several new (VERY expensive) Panasonic CF-54 laptops.
I tried everything I could think of and many suggestions from the internet as well. nothing worked. the chipset was balky in connecting if it would connect at all, and when it did connect, it was almost always REALLY, REALLY, REALLY slow! And this was the case on multiple routers, both old and new.
In complete despair, I finally decided to completely nuke the MASSIVE (and as far as I could tell - nearly useless) set of bloatware known as Intel Proset/Wireless and instead just install the basic Intel WiFi drivers and let Microsoft manage the WiFi, which Microsoft has almost always done flawlessly.
Here’s what I did:
1. Download the barebones Intel drivers for the 8260 wifi chipset from here:
https://downloadcenter.intel.com/download/27206
And don’t be fooled by the the Proset page title: the first set of downloads on the page are the barebones drivers WITHOUT Proset. (When the filename does not include the word “Proset”, then they are barebones.) For my Windows 7 x64 system, I downloaded was WiFi_20.0.2_Driver64_Win7.zip:
2. Unzip the downloaded driver file, but don’t do anything else with it yet.
3. Go to Programs and Features in Control Panel and Uninstall the installed Intel Proset/Wirless software. Remove everything, including “settings”.
4. Next, manually delete the two intel wifi driver files from Windows/system32/drivers, namely netwfw02.sys and netwfw02.dat OR netwfw04.sys and netwfw04.dat (or perhaps some other number besides 02 or 04). This is a precautionary step, because uninstalling intel driver software lately does not actually delete the old driver files, and I’ve had replacement intel driver installs silently fail because they were unable to delete and/or replace existing driver files, leaving a total mess. (The worse case i’ve encountered is that uninstalling the intel HD Graphics 520 display drivers leaves over 200 driver files that have to be manually deleted AFTER uninstalling, because if they are not manually deleted, the new driver bundle will absolutely NOT install correctly leaving things like graphics acceleration completely broken.)
5. Now go back to the unzipped barebones wifi drivers folder and execute DPInst64.exe followed by executing iprodifx.exe.
And that should be it. Windows should popup a balloon from the taskbar telling you that a new wifi device has been installed and you should be good to go. Not only should the intel wifi now function flawlessly, but you’ve also eliminated a massive amount of unnecessary bloatware, including several background processes that run at all times, consuming both CPU and memory.
i never could get the intel dual band wireless-ac 8260 chipset to work reliably in several new (VERY expensive) Panasonic CF-54 laptops.
I tried everything I could think of and many suggestions from the internet as well. nothing worked. the chipset was balky in connecting if it would connect at all, and when it did connect, it was almost always REALLY, REALLY, REALLY slow! And this was the case on multiple routers, both old and new.
In complete despair, I finally decided to completely nuke the MASSIVE (and as far as I could tell - nearly useless) set of bloatware known as Intel Proset/Wireless and instead just install the basic Intel WiFi drivers and let Microsoft manage the WiFi, which Microsoft has almost always done flawlessly.
Here’s what I did:
1. Download the barebones Intel drivers for the 8260 wifi chipset from here:
https://downloadcenter.intel.com/download/27206
And don’t be fooled by the the Proset page title: the first set of downloads on the page are the barebones drivers WITHOUT Proset. (When the filename does not include the word “Proset”, then they are barebones.) For my Windows 7 x64 system, I downloaded was WiFi_20.0.2_Driver64_Win7.zip:
2. Unzip the downloaded driver file, but don’t do anything else with it yet.
3. Go to Programs and Features in Control Panel and Uninstall the installed Intel Proset/Wirless software. Remove everything, including “settings”.
4. Next, manually delete the two intel wifi driver files from Windows/system32/drivers, namely netwfw02.sys and netwfw02.dat OR netwfw04.sys and netwfw04.dat (or perhaps some other number besides 02 or 04). This is a precautionary step, because uninstalling intel driver software lately does not actually delete the old driver files, and I’ve had replacement intel driver installs silently fail because they were unable to delete and/or replace existing driver files, leaving a total mess. (The worse case i’ve encountered is that uninstalling the intel HD Graphics 520 display drivers leaves over 200 driver files that have to be manually deleted AFTER uninstalling, because if they are not manually deleted, the new driver bundle will absolutely NOT install correctly leaving things like graphics acceleration completely broken.)
5. Now go back to the unzipped barebones wifi drivers folder and execute DPInst64.exe followed by executing iprodifx.exe.
And that should be it. Windows should popup a balloon from the taskbar telling you that a new wifi device has been installed and you should be good to go. Not only should the intel wifi now function flawlessly, but you’ve also eliminated a massive amount of unnecessary bloatware, including several background processes that run at all times, consuming both CPU and memory.
At the command prompt, run the following commands in the listed order, and then check to see if that fixes your connection problem:
Type netsh winsock reset and press Enter.
Type netsh int ip reset and press Enter.
Type ipconfig /release and press Enter.
Type ipconfig /renew and press Enter.
Type ipconfig /flushdns and press Enter.
Run Command Prompt as an Admin.
Multiple times. Its looking more and more like the laptop just doesn’t like my old router. Like I said the netbook, which was also Win7, talked to the router OK.
I’m just guessing, but it sounds like the machine was set up as a server to tunnel to a specific static IP address at the other end. Generally ISP connections don’t do this, they are switching IP addresses all the time on you trying to move you to a lower load server in their system. Now how to exactly find that in Win 7 I am not sure, Maybe an IT guy here can help with that. I know I had problems with that when I set up my tunnel server in linux. Because mine is a “server” and not just a “client” it relies on a fixed IP address that doesn’t change all the time like a normal ISP service does.
“”” I’ve had a Netgear WNDR4000 router forever. Two desktops (XP PROs), tablet, another laptop (VISTA) and the netbook that was broke all talked to the router OK. “””
You have a bunch of antiques. Tech years is like dog years so your 20 year old stuff is really 140 years old.
It should be trying to connect to a router address which is usually, 192.168.0.X with the Xs being about the only thing each model may do differently.
Does XP have that feature where you can make a disk from one connected computer and use it to set up others?
Also, I don’t think you can go out and just get any router. You need to have one that’s compatible with your ISP, of course it depends on whether or not it’s a router/modem combo or strictly a router. If the latter, then it doesn’t matter.
After I called few times the Dell suport Center, I finally got an helpfull strange tip. I was told to get into safe-mode with networking.
This mode somehow recover the WL connection. I was able to finally connect to the net via WL and after rebooting and getting back to nomal-mode WL was still alive.
If it is set to WEP, the new laptop probably wants WPA or WPA2/PSK.
Newer devices will not connect to the old WEP.
three things to try.
1. temporarily turn wifi security off (none) at the wifi access point/router. See if it it is the security type that your PC is not compatible with. When you were able to connect at a different location what was that security type?
2. manually assign a free IP address on your router network, and manually assign your router’s address as the gateway, and manually give a dns of 8.8.8.8. See if your PC is having trouble with dynamic IP settings.
3. purchase an external USB wifi adapter, they are inexpensive see if that works.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.