Identifying...([network name]) No Internet Access

Hi,

I have an Asus laptop running Windows 7 Ultimate. Last week, I had been living in a place, where I had Time-Warner Cable (TWC) Internet, and everything worked just fine, not only on that network but on others, as well. This week, I moved to a new place, and I had my service transferred over. I am using the same modem/router (Technicolor TC8715D) that was in the old place, and TWC simply transferred the service over by sending a technician out to hook it up. The service works, as I can access it both from my cell phone and tablet (both Droid-based), and the technician was able to access it from his iPad. However, my laptop connects, but it is unable to get Internet access.

At first, I was given a proper DHCP address, but subsequent efforts achieved only a 169.x.x.x address. I have tried both restoring the factory defaults on the modem and changing the default name/password, but neither of these efforts produced the desired result. I've removed the network profile from both the Network and Sharing Center, as well as the registry. I've tried releasing the IP address, flushing the DNS, assigning a static IP, and rebuilding/repairing the network stack. None of this has helped.

There was a previous DSL Internet connection in this new home available from Verizon, and I've been using this on my laptop, so I'm perfectly capable of connecting to other wireless networks. I would try a wired connection, but there's a driver issue w/ my ethernet port.

Does anyone have any thoughts on how to resolve this Identifying...([network name]) No Internet Access problem? I see different causes/resolutions online. Any help would be greatly appreciated. Thank you!


Jeff

A broadband internet wireless router is a crucial component of any home network system. If you're already using a high-speed connection to network you'll easily get access to this unique address. Wireless routers using the IP address 192.168.0.1 can function adequately as their distinctive components will be paired.

You might not need to install a DHCP client and multiple switches and hubs when you use a wireless router because it is capable of handling all the required info as a singular unit. If necessary, this unique IP may be modified by the router operator. It is a basic task. You just have to start your browser and write the Internet protocol address on the Address bar.

Just one single unit in the network system is able to use this IP. If an additional device is put to use it's going to result in computer network malfunction. You have to restrict ability to access this specific account from other people by creating a password and implementing any other required reconfigurations.

Thank you for your response, but I'm not sure how this applies to my problem.

Just as a follow up, I forgot to mention that I have VPN software installed. It was installed prior to my move, as well. However, I uninstalled it, and the connection problem persisted, so I reinstalled the software.

This is my ipconfig for the system in question. It appears to be a DNS issue, as the DNS servers seem to be IPv6 servers instead of IPv4. I should be using IPv4, as that's what was being used in my old home prior to the move. And, my tablet is receiving an IPv4 address (192.168.0.x). Therefore, I disabled both stateful and stateless IPv6 services on the router. This didn't resolve the problem, so I disabled IPv6 services on the wireless adapter, and this still didn't help, so I assigned a static IP/DNS servers to the adapter, which stuck, but it still didn't allow me outside access, nor could I ping the gateway.

I also ran the 6to4remover I found in your forums, and that was unable to remove any adapters, so I ran the flush.bat, and I was still unable to gain access via my preferred network. At this point, I'm at somewhat of a loss.

Windows IP Configuration

Host Name . . . . . . . . . . . . : Alabama
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 802.11n Wireless LAN Card
Physical Address. . . . . . . . . : EC-0E-C4-25-91-49
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2606:6000:6213:e600:2121:9f70:110c:3468(Preferred)
Temporary IPv6 Address. . . . . . : 2606:6000:6213:e600:2804:11e1:f37e:3d5d(Preferred)
Link-local IPv6 Address . . . . . : fe80::2121:9f70:110c:3468%22(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.52.104(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : fe80::ce03:faff:fe8f:78d%22
DHCPv6 IAID . . . . . . . . . . . : 283905732
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-C9-D1-DF-EC-0E-C4-25-91-49

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 38-2C-4A-3F-3C-F9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Windows Adapter V9
Physical Address. . . . . . . . . : 00-FF-6B-0A-47-B7
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Bluetooth Network Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)#2
Physical Address. . . . . . . . . : EC-0E-C4-25-91-4A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{6B0A47B7-5FA8-427A-A8DD-EFEBE8E46B57}:

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

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.{7566B35A-740B-4EF2-888E-4E8C418C210D}:

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

Tunnel adapter isatap.{0A6494B5-7F07-471D-9C82-91D1CACAF3B3}:

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

Tunnel adapter isatap.{C43B348A-9EC6-4D79-9F09-0EAB1C52E3A7}:

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

I've attached a screenshot of the Xirrus screen, when I'm connected to the network I'm having a problem w/. The SSID of this network is TC8715D89. The C34YK SSID is the Verizon wireless network that was available in this home, when I moved in. It's the one I've been using to gain Internet access, while I troubleshoot the problem w/ the TWC wireless connection.

Another update: I've run sfc /scannow, and while it replaced a few files, it didn't resolve the problem. I've tried booting into safemode, and that didn't resolve the problem, either. At this point, I'm out of ideas. Does anyone have any thoughts?

I tried connecting to the problem network, and I released the 169.x IP address, but that didn't seem to work, b/c it didn't show up as 0.0.0.0. Instead, it gave me the same 169.x IP address. Regardless, I flushed the dns, and I tried renewing the IP, but it gave me this error message:

An error occurred while renewing interface Wireless Network Connection : unable to contact your DHCP server. Request has timed out.

Does anyone have any thoughts on this problem? Any ideas on what I can/should try to resolve it?

Yet another update: I uninstalled the wireless adapter from the device manager, including removing the driver, then restarted. Once up and running, I ran the adapter's software, and it asked if I wanted to remove the driver, or repair the installation. I chose to remove the driver. I then restarted, and when the system rebooted, instead of running the adapter's software, I chose to install the driver via the device manager. I then connected to the problem network, and the same problem persisted. I'm beginning to think that there's some sort of problem w/ the router's profile on this Windows box, but I'm unable to determine where it resides, so I can't troubleshoot it. I might have to have TWC replace the router, and see if that resolves the issue.

To update this further, I had TWC replace the modem, and yet, the problem still persisted. I then installed the proper driver for the wired NIC, and I was able to get a proper DHCP address from the TWC network. Therefore, the problem was narrowed down to simply the wireless NIC and the TWC connection.

This morning, I upgraded from Windows 7 Ultimate to Windows 10, and the problem still hasn't resolved itself. I'm not a big fan of 10, so I'm thinking of switching back to Windows 7. In the meantime, does anyone have any idea(s) on what might be causing this unusually difficult problem?