New computer can't connect to specific wireless network

dub_c_8008

Reputable
Nov 11, 2015
5
0
4,520
I recently bought a new computer that has an Intel Dual Band Wireless-AC 7265 adapter. The new computer will connect to wireless networks at my office and at a friend's house, but will not connect to the wireless network at home. All of my other devices are connecting normally. I have updated the driver, factory reset the router, and re-booted multiple times. Each time, when I try to connect to the network and enter the password, the Connection states "Limited" and there is no internet access. When running the network troubleshooter, I get this result "Wi-Fi doesn't have a valid IP address."

When I compare the results of ipconfig on the new computer with computers that are connecting normally, I notice that the problem computer has no Default Gateway listed. Also, the problem computer has a strange value that I don't recognize listed after "Autoconfiguration IPv4 Address".

If anyone has any ideas, I would really appreciate it.
 
Solution
Thanks for your help! it is working now. Because of your suggestions, I was digging around in the wireless properties dialog box. I found a setting called "Wireless Mode". My Verizon Fios router says it is 802.11b/g. The connection didn't work when I set the mode 802.11b/g, it didnt work when I set it to 802.11g, but as soon as I changed it to 802.11b, it started working normally, and has been great since. I sincerely appreciate the help!!
Please post your ipconfig /all results. Does that Autoconfiguration IPv4 address start with 169.?

Manually set the wireless adapter to the appropriate wireless standard versus "autonegotiate" - match the router.

Double check that you have correctly entered the home router's IP address and submask.

Make sure that the number of connecting devices is not exceeding the router's setting (i.e., number of devices, DHCP address range.)

 
I'll report the ipconfig /all results when I get home from work tonight. I'll also check the other things that you suggested and report back. I don't recall what that IPv4 address was, I just remember it was not 192.168.x.x like I had expected. Thanks for your help. I will report back with updates tonight.
 
OK, I have pasted the results of ipconfig /all which was done while the connection was showing limited. It is at the bottom.

A few updates - this evening, when I got home, the connection initially worked, but was extremely slow and intermittent. Now, it is back to showing a "limited" connection with no internet access. Once again, it did work while I was at work today, but it did seem rather slow.

As for the suggestions above, I could not figure out how to turn off "auto-negotiate". I can see that the router is using 802.11b/g, but I can't see where to change the setting for the wireless adapter. I did notice that in the wireless adapter properties, the "Ad Hoc Channel 802.11b/g" Value is set to 1 -- on my computer that is working, this value is set to 11. I have no idea if this makes a difference.

As for the other suggestions, I did confirm that the number of devices was OK, and I did double check the IP address and submask.

Thanks for helping!

>>>>>>>
Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 7265
Physical Address. . . . . . . . . : 34-02-86-64-3E-71
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::7174:13c:82a:8df0%4(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.141.240(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 36962950
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-D5-65-5D-34-02-86-64-3E-71
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Local Area Connection* 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : 34-02-86-64-3E-72
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

 
The 169. --- address is a default IP address Windows uses when it cannot get an IP address.

Reconfigure your wireless adapter so that the Subnet Mask and Default Gateway match your home router.

ipconfig /all is still showing 255.255.0.0 and 169...etc. versus the most likely settings of 255.255.255.0 and 192.168.x.x (depending on the router) that you noted you would expect

What make and model is your router? Is it just b/g ? Not n or ac?

And the wireless adapter should use the same channel. Your new computer may be picking up on another nearby unsecured network or hotspot when wireless connectivity works. Are you in an area with other wireless networks?

Depending on your router it may or may not show the devices connected. If so you can identify your devices by name and/or MAC.

See if the new computer shows up when and while you have any sort of internet connectivity.

At least you know (via your office) that the wireless adapter works. So the problem is probably a configuration problem with respect to the home network. And maybe an additional problem with interference.





 


 
Thanks for your help! it is working now. Because of your suggestions, I was digging around in the wireless properties dialog box. I found a setting called "Wireless Mode". My Verizon Fios router says it is 802.11b/g. The connection didn't work when I set the mode 802.11b/g, it didnt work when I set it to 802.11g, but as soon as I changed it to 802.11b, it started working normally, and has been great since. I sincerely appreciate the help!!
 
Solution