Hi everyone, Recently and without any trigger I can find, my Vista Home Premium desktop can no longer connect properly to my wireless network. It will either have issues connecting at all or when it does 'connect', it can't ping anything on the network and is limited to "Local Only". I've seen a number of topics where people are having a similar issue and I have tried a lot of troubleshooting with no success. So far, this is what I've done: - Reinstalled drivers - Disabled/Re-enabled the device - Multiple restarts and multiple attempts at releasing/renewing my IP - I have fiddled with the DhcpConnBroadcastFlag (or whatever it's called) testing with it set to both "1" and "0" values - I have tried booting into Safe Mode with Networking and clean booting I've done a lot of troubleshooting and probably have forgotten some stuff that I've done. Frankly, it's been a very frustrating 2 days so far. I would love to figure it out if it's a software issue or a hardware issue. I tend to think it's a software-based issue, because the wireless card is able to get an IP address and is even given DNS server info (and I /boggle at the idea of it being a straight hardware issue), but then again it doesn't work even in Safe Mode. I forgot to mention, we have 2 Vista laptops and an XP laptop that are all able to connect without issue. If anyone can help me, that would be greatly appreciated.

Hi, Please try to take the following suggestions to troubleshoot this proble. Suggestion 1: Create a new connection =================================1. Open Start menu, input "Network Center" (without the quotation marks) in the Search bar and press ENTER to open Network Center.2. Click "Set up a connection or network".3. Choose "Manually connect to a wireless network" and click Next.4. Please follow the instructions on the screen to create a new wireless connection.5. Then, let's try to connect to the new wireless connection to verify the issue again. Suggestion 2: Reset Winsock ====================================1. Open Start menu, click All Programs -> Accessories.2. Right click "Command Prompt" and click "Run as administrator".3. Input the following command in the DOS prompt window and press ENTER at the end of the line:NETSH INT IP RESET C:\RESETLOG.TXT4. Then, please restart the computer.5. After restarting the computer, please double check the steps above to run the following command in DOS prompt window:NETSH WINSOCK RESET CATALOG6. Let's restart the computer again.Suggestion 3: Manually assign a static IP address again ==================================== Please manually assign a static IP address again after resetting Winsock. Then, please test the issue again. If it doesnt work, please run the command ipconfig /all and post the result here. Thank you for your cooperation. Hope it helps.

I tried the steps you recommended and am still experiencing the same issue. I have since re-enabled DHCP on the wireless connection, but here is the output of the ipconfig /all command: Windows IP Configuration Host Name . . . . . . . . . . . . : Wolverine Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : phub.net.cable.rogers.com Wireless LAN adapter Wireless Network Connection 2: Connection-specific DNS Suffix . : phub.net.cable.rogers.com Description . . . . . . . . . . . : Linksys Wireless-G PCI Adapter #2 Physical Address. . . . . . . . . : 00-18-F8-2E-20-01 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::15c:5d92:52dd:72a%14(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.2.100(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Wednesday, September 03, 2008 4:07:43 PM Lease Expires . . . . . . . . . . : Thursday, September 04, 2008 4:07:43 PM Default Gateway . . . . . . . . . : 192.168.2.1 DHCP Server . . . . . . . . . . . : 192.168.2.1 DNS Servers . . . . . . . . . . . : 64.71.255.198 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter Local Area Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Marvell Yukon 88E8053 PCI-E Gigabit Ethernet Controller Physical Address. . . . . . . . . : 00-17-31-BD-3C-C4 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 6: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : isatap.{C1532A27-F47D-48E2-9E2A-B5C27004AE64} Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 7: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : phub.net.cable.rogers.com Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 9: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 02-00-54-55-4E-01 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Hopefully, that can give you some information to help me further. Before getting your troubleshooting steps I also attempted to do a System Restore to a date before this started happening, in case a program was installed without my knowledge or something that might have caused the issue. Clearly, still experiencing the issue.

Looking over the output of ipconfig (thank you for that!), the only thing that looks even slightly 'odd' is the DNS server address. Generally (exception: an AD Domain), the router will/should be handling DNS queries, and would, therefore, declare its LAN address as the primary DNS server (this would be pushed out with an IP request from a client.)This, typically, holds doubly true for a cable network.Try this:reconfigure your router to act as the primary DNS server for your network. IF absolutely necessary, enter primary and secondary DNS server addresses in the router config; however, leaving that on 'auto' usually works.Run the following commands on the problem PC, from an elevated command prompt:ipconfig /flushdnsipconfig /releaseipconfig /renewPost back with results.

I'll try that, but I should mention that a similar output is produced with every system on this network, but only the one has a problem. For instance, here is the output from the XP laptop I am currently using, connected to my wireless network Windows IP Configuration Host Name . . . . . . . . . . . . : zeev7 Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : phub.net.cable.rogers.com Ethernet adapter Local Area Connection: Media State . . . . . . . . . . . : Media disconnected Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet NIC Physical Address. . . . . . . . . : 00-0F-B0-02-65-44 Ethernet adapter Wireless Network Connection: Connection-specific DNS Suffix . : phub.net.cable.rogers.com Description . . . . . . . . . . . : Broadcom 802.11b/g WLAN Physical Address. . . . . . . . . : 00-90-4B-55-94-5C Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.2.102 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.2.1 DHCP Server . . . . . . . . . . . : 192.168.2.1 DNS Servers . . . . . . . . . . . : 64.71.255.198 Lease Obtained. . . . . . . . . . : Thursday, September 04, 2008 6:40:37 AM Lease Expires . . . . . . . . . . : Friday, September 05, 2008 6:40:37 AM I will, however, try what yousuggested and see if that will help resolve the issue.

I thought I should update this. I was going to set my router up as the primary DNS server, as suggested, but had to call Linksys for help doing so. When calling Linksys, they ended up troubleshooting the wireless card itself. Apparently there is Microsoft documentation that says that a recent update to Windows Defender can cause this issue. Since I already tried restoring to before the update was installed, they figured it's a hardware problem and are sending me a replacement. I appreciate the help you guys gave