Custom Build with Win 7 not connecting to modem

[pyrakitt]

Greetings all,

I was on my computer last night and all was well until 3AM rolled around and the pop-up for Windows update appeared. I let the computer do it's thing and restart, installing the update. Afterward I could not connect to the internet and haven't been able to since. I'm sorry but I neglected to write down the number of the KB article. The only one sitting waiting to be updated now is KBB90830, the Malicious software removal tool.

This is a wireless connection on a custom build computer running Windows 7 Professional 32bit.
The wireless card is a TP-WDN4800.
Everything else in the house both wired and wireless is connecting to the modem fine.

I've tried the following:
- powercycling the modem (no change)
- powercycling the computer (no change)
- system restoring to a point before the update (failed)
- manually finding and removing the update and restarting (no change)

Clicking on available networks shows my modem in the lineup. Clicking on it starts an attempt to connect to it. It then states that it's connected to an Unidentified network set as Public with No network access. It shows the icons that indicate that it's connected to the modem but can't get out from the modem to a website.

I've then tried the following:
- checking Device Manager, states the wireless card is operating and drivers are updated
- disabling the TP link and then enabling it. (no change)
- uninstalling the TP link and restarting. (no change)
- inserting the disk that came with the TP link and attempting to reinstall drivers. (states they're already updated)
- getting into the modem from another computer shows my computer is not connected to the modem at all

Ipconfig /all shows the following:
Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TP-LINK 450Mbps Wireless N Adapter
Physical Address. . . . . . . . . : C0-4A-00-1E-F7-BE
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::14b3:3258:4c94:6205%12(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.98.5(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 281037312
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-BE-1C-65-C0-4A-00-1E-F7-BE

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

Attempting ipconfig /release and ipconfig /renew did nothing.

So the set up looks fine from every angle I've tried and yet I'm still getting the 169 ip address.
Attempting to set up a new connection also fails with the same icons and issues.

I need some new ideas to try and any help would be appreciated.

 

[chev65]

System restore is made to roll back your machine to before when the problematic updates were installed.

After that you can figure out which update caused the problem and right click to "hide the update" so it won't install again.

http://www.sevenforums.com/tutorials/700-system-restore.html

 

[carwiz]

I'm a little weak on network stuff but it doesn't look like your router is connected to your ISP. Confirm that they use DHCPv6 because you don't have a Default Gateway address and the DHCPv6 addresses look corrupt. You also might try running the network troubleshooter. It can fix quite a few problems. (Right click the network status icon in the lower right corner and select Troubleshoot Problems.)