Windows 10: Can't get Internet access on my router

I have a desktop connected by wire to my Bell modem. I also have a laptop connected via wifi. I had a problem with updates not installing on the laptop so I did a restore to a previous save (about two weeks ago. When it completed, I can recognize my modem (Bell500) but when I try to use it it says "no internet access. It worked fine before I did the restore. ANy ideas what I could have done wrong or how I can fix it. The desktop connects fine by cable but the laptop can't get internet access. WIFI status shows IPV4 and IPV6 no internet connection.I'm LOST!

:)

 

Can connect to WLAN, but can't access any web sites

Just discovered something else:

When I have my E61 connected to my Linksys wireless access point (WAP54G), I can access the Linksys firewall router (RV082) by typing in the RV082's IP address. So I definitely have good access to my home network, but I can't access anything on the public Internet.

I guess it could be a setting in my firewall router is blocking my phone from getting to the Internet? But the same router lets my laptop access the Internet via the wireless acces point without any issue.

Hmmmm...

 

Windows 10 suddenly not connecting to internet.

Hi, my notebook suddenly can't connect to the internet after running a Windows 10 update. My router is working fine and there are no issues there. I can connect to the router with my notebook no problem there either. However my internet connection is not
available. I've run trouble shooting several times and keep getting the same answer, Your connection to access point, router or cable modem is broken. Turn off your router (not the exact wording). I've done this several times. No luck. I've also done a restore
to a couple days ago, no luck there either. The thing is, my router is fine, working through it now, my notebook connects to it fine, I can ping it, but when I try to go online it can't see the connection. Please help, getting desperate.

 

Can you please click Windows Key-X (both at the same time), run Command Prompt (Admin), and then type ipconfig /all into that window? Cut'n'paste the results into a reply message so I can see what that says. I'm guessing you may no longer be getting DHCP services, but this output will confirm or correct my presumption.
Thanks,
--Ed--

 

Thanks Ed. Here it is!
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.


C:\WINDOWS\system32>ipconfig/all


Windows IP Configuration


Host Name . . . . . . . . . . . . : Norma-HP
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : home


Ethernet adapter Ethernet:


Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe FE Family Controller
Physical Address. . . . . . . . . : 78-E3-B5-63-E9-99
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes


Wireless LAN adapter Wi-Fi:


Connection-specific DNS Suffix . : home
Description . . . . . . . . . . . : Broadcom 4313GN 802.11b/g/n 1x1 Wi-Fi Adapter
Physical Address. . . . . . . . . : E4-D5-3D-41-32-D6
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::a866:8b41:f9a6:dc23%19(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.2.14(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, September 14, 2016 5:36:10 PM
Lease Expires . . . . . . . . . . : Saturday, September 17, 2016 5:36:10 PM
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DHCPv6 IAID . . . . . . . . . . . : 333763901
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-F1-06-57-E4-D5-3D-41-32-D6
DNS Servers . . . . . . . . . . . : 192.168.2.1
NetBIOS over Tcpip. . . . . . . . : Enabled


Tunnel adapter Teredo Tunneling Pseudo-Interface:


Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes


Tunnel adapter isatap.home:


Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : home
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes


C:\WINDOWS\system32>

 

It's not a DHCP problem: you have a valid private IP address, and a valid connection to your gateway (the router). Time to call your service provider, perhaps? Did the Bell router come from your provider, or is it your own equipment? They may be able to help you either way, but they will be a LOT more motivated if it's their router, not yours. Please advise...
Thanks,
--Ed--

 

If your other pc gets out ok its unlikely to be the router. OPen a cmd prompt again type
tracert 194.119.131.66

post results can you login into the router are you sure you are entering the correct password as symptoms are wrong password

 

Good call, Samuria! Hadn't thought of that, but it also explains the situation.
Thanks for chiming in.
--Ed--

 

Here's the Tracert results. Ed's suggestion made it work a "little bit better!" but still reverts to no internet
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.


C:\WINDOWS\system32>tracert 194.119.131.66


Tracing route to 194.119.131.66 over a maximum of 30 hops


1 3 ms 1 ms 1 ms 192.168.2.1
2 7 ms 8 ms 7 ms 64.230.200.227
3 9 ms 9 ms 42 ms 64.230.36.120
4 231 ms 244 ms 237 ms 64.230.95.202
5 237 ms 252 ms 245 ms 64.230.78.254
6 231 ms 225 ms 225 ms 64.230.32.145
7 231 ms 233 ms 229 ms 67.69.246.110
8 235 ms 234 ms 236 ms 4.69.153.85
9 89 ms 88 ms 89 ms 4.69.166.73
10 88 ms 90 ms 88 ms 212.113.9.106
11 91 ms 88 ms 88 ms 195.157.3.106
12 90 ms 89 ms 89 ms 194.119.131.66


Trace complete.


C:\WINDOWS\system32>

 

That shows you get out just fine so what errors are you getting from browser or other connections as there is nothing wrong with your connection it just proved it work. lets test dns from a cmd prompt type

tracert plus.net
post results

 

Tried to do that but got response the following response to tracert plus.net
unable to resolve target system name plus.net
What did I do wrong?

 

I would change your DNS server to 8.8.8.8 (Google's DNS) and try again. If this works it is a DNS problem.

Network and Sharing Center/Click on the WiFi Connection/go to properties/Internet Protocol Version 4 (TCP/IPv4) Use the following DNS Server addresses. And enter 8.8.8.8