So..its been two days and my wireless is still working better than ever. Caterina..what I did was disabled IPv6 and assigned a static IP address. I used 192.168.1.200 for the IP. 255.255.255.0 for subnet mask. and 192.168.1.1 for default gateway and 192.168.1.1 for DNS server. Try doing that? Thats what worked for my after a week of trying everything else. Hopefully it works for you.

I tried, but it gives me "unidentified network". mmm :(

Yeah, the ip address information you would enter when setting up a static ip will very from router to router. I was able to figure out what Jugs446 needed from what he was being assigned on his ethernet adapter. Caterina182, you may need to run that cmd stuff that we talked about earlier in this thread and post your findings to clue us in on what might need to be done.

As for Domain Name Servers (DNS), those are ip addresses of servers that hold the information of what domain name (something.com) equals what IP address (xx.xx.xx.xx). If you didn't have them the only way you could get to a website would be by typing its IP address number.

Jugs446's configuration works fine with him resolving DNS from his router's gateway address. (192.168.1.1), which basically means if his computer needs to know where Daniweb is, it is told via having the dns entered in the connection to ask 192.168.1.1 so it goes and knocks on that door, his router answers, and then goes and asks the dns server that is assigned to it on the wan side, which then goes out and asks all the other dns servers they know of until finally they get the one daniweb is registered to, and it sends them back daniwebs ip address all the way back to his computer so he can then go to it.

Not every router automatically will respond to a dns resolution request sent to its gateway, so you may need to bypass that by entering your isp's DNS servers there instead. You can usually find them by plugging your computer straight in (bypass router) and set to DHCP and autmatically obtain DNS addresses. Do an ipconfig from the command prompt and it should tell you what your isp's DNS servers are.

Also, if you have DSL and your provider uses PPPoE thats a totally different monster. We don't use that here so I've never really worked with it so I can't be of much help if that is the case.

Thanks a lot for all the help. My friend Victoria (whos laptop is not working) and she's gonna try and return it to see what they say. We've tried everything, honestly!

OK, I just registered for this account to post in this thread... ;)

Anyway, I'm having the same issue and wanted to share the info I've come accross regarding the particularly frustrating scenerio. Microsoft came out with an AutoConfiguration "script/program" in 98 that makes connecting to a network easier. This is prior to the introduction of DHCP and became the alternate method when a DHPC server is not available. It is now the primary means of accessing a network connection via IPv6. The AutoConfig will search and assign an IP based on the local network. I've come accross the option of dissabling AutoConfiguration in the registry, but there has to be an easier way.. I hope. As of this post the only reason disabling IPv6 should work can be found here: http://www.microsoft.com/technet/community/columns/cableguy/cg1005.mspx
"Note: Due to misconfigured DNS servers on the Internet, computers that use both IPv4 and IPv6 might not be able to resolve names and connect to Internet resources. This rare problem occurs when a misconfigured DNS server receives a request to resolve a name to one or more IPv6 addresses (a request for AAAA records). If the DNS server does not support IPv6, the name query fails. The querying node then sends a request to resolve the name to a set of IPv4 addresses (a request for A records). The misconfigured DNS server drops the subsequent DNS query for IPv4 addresses and the entire name resolution attempt fails, resulting in impaired network connectivity for the requesting node. If you are experiencing this problem, ask your Internet service provider to reconfigure their DNS server to accept the subsequent DNS query for A records after failing the DNS query for AAAA records. Alternately, you can temporarily disable IPv6 on the requesting computer. This issue exists on the DNS servers and is common to all computers that use both IPv4 and IPv6."

I just disabled my IPv6 connection and the "Preferred" connection reverted back to my previous static Ip address. Awesome!

Once everyone begins to move over to v6, we should be seeing less of this issue.

Hope the info helps.

My friend Vicky called Comet, which is where she bought her laptop from. After hours on the phone asking her to connect to the internet to download something ("THAT'S THE PROBLEM, I CAN'T!!!!, she yelled back) they suggested that she made a backup for her info and then do a system something. It wasn't system restore, bu I can't remember what it was right now. I'll aske her later and post it.

So..its been two days and my wireless is still working better than ever. Caterina..what I did was disabled IPv6 and assigned a static IP address. I used 192.168.1.200 for the IP. 255.255.255.0 for subnet mask. and 192.168.1.1 for default gateway and 192.168.1.1 for DNS server. Try doing that? Thats what worked for my after a week of trying everything else. Hopefully it works for you.

I had exactly the same problem as JUGS446 when upgrading to Vista Home Premium from XP. Previously working wireless,with internet, to Local only access. The MS KB 928233 didn't help, but the fix above worked a treat! Be patient, as after applying the IP and DNS settings, the network shows unobtainable. A Diagnose and Repair quickly brings it online with full internet access.

Oh thanks loads but doing that system restore or whatever it was actually fixed the problem.

Thanks for all your help!!!

ehi morros , and easy solution is to disable de UAC (User Account Control), this disable most of the security stuff of windows vista, this works for me !!!
later when you downloads all the security upgrates you can enable again, it should work fine.

This is a very common Problem in Vista. Consumer/Residential Internet Providers are set for Automatic DHCP. The ISP's do not even know the answers and Microsoft support has had problems getting people online. This is with the PC directly connected to the cable Modem. the first step to getting the connection going.

Working for an ISP, I would like to know the real answer for getting Vista online. It is frustating not knowing what truly is the fix. Of course we have a couple Vista PC's set up to explore on, but they are already connected. Especially for those who buy new computers and attempt to set up for the first time. This will become more prevalent as more consumers purchase Vista machine. This will probably happen this 2007 Holiday season & Microsoft comes up with a reasonable Update for most big issues.

I have attempted disabling IPv6, checking settings, disabling & re-enabling network card and LAN connection and still nothing in most cases. I have tried unplugging the power from the computer so that the network card & the system loses information holding up the connection. one time I switched over to USB and that worked. Luckily the person was not setting up with a Router.

I think more reseach needs to be done on this.

found this looking for a better fix than the one I have ...

power cycle the wireless router.

or the long answer ...

exact same expereince as the OP, local access only, I can however open the wireless router web admin page, so this isn't a wireless connection issue per se.


All was working fine until i turned off SID broad cast, lost internet access but local access was fine, tried numerous network repair and diagnostics. Eventually I re-enabled SID broadcast, this alone did not fix the problem, neither did a reboot. I had to shut down my desktop, powercycle the wireless router, boot up my desktop. Everything working again.

I suspect there is something beyond my knowledge going on with vista/wireless router upnp packet forwarding, at least I suspect it's on the routing side of things as the wireless network functions, accessing external sites is what fails ... note my XP laptop was working fine throughout the troubleshooting, so it wasn't as if the internet connection itself was down.

Just heard this may be caused by Vista's auto tuning which dosn't like some routers and to try disabling it by ruuning the command -

netsh interface tcp set global autotuninglevel=disabled

I will test it tonight.

The sad thing is, I just bought an Vista Laptop. I was debabting getting an XP laptop just because of this reason. But I figured since I troubleshoot this all day long for our customers, that I would take a shot at it. I have the same issue. I Can not get connected to the INternet whether the laptop is directly connected to the Cable modem or through a router. I can connect to the Routers Web Admin thought.

Researching this it seems like the DHCP that my ISP (and the company I work for) is different that the DHCP that Vista is running. A "Windows DHCP" that can not see the ISP's DHCP. Thanks Microsoft. TRying different things that I read and nothing has worked yet. Whatever I do try, I set back so that I know exactly what the fix is.

Today I did take the laptop to a coffee shop and I was able to connect through their wireless and get to the internet. But that was a different ISP (TMobile). So maybe they had the updates DHCP.

Now I did enable UPnP on the Router, but that does not see to do anything. Whatever it is. The Vista DHCP is not Communicating with the ISP DHCP.

Anyone have any ideas?

running the command "netsh interface tcp set global autotuninglevel=disabled
" seems to have fixed my issue, bit early to be sure.

if you try it, you can always change back with the command
"netsh interface tcp set global autotuninglevel=normal"

googling vista autotuning brings up many other issues with this feature, so maybe worth turning off anyway.

I got an interesting message back from that

"Set Global Command Failed on IPv4 The requested Operation requires elevation"

Elevation to what? I am using the Administrator account. Gggggrrr


running the command "netsh interface tcp set global autotuninglevel=disabled
" seems to have fixed my issue, bit early to be sure.

if you try it, you can always change back with the command
"netsh interface tcp set global autotuninglevel=normal"

googling vista autotuning brings up many other issues with this feature, so maybe worth turning off anyway.

being logged in as administror isn't enough ... another vista annoyance.

right click on the command prompt icon in the start menu and select "run as administrator"

then run the netsh command. Otherwise it runs with normal user rights even when logged in as admin.

I got an OK on that. still nothing.

Tried USB, it recognized the cable modem. moved driver over for it via usb flash disk/drive. no connection. still "local only" with all settings correct.

online chat with my isp. told me to uninstall the tcp/ip and reinstall it. Ooops can not uninstall it in properties. LOL

I am going to take out the battery and see if that does anything.

also try to uninstall symantic/norton security.


being logged in as administror isn't enough ... another vista annoyance.

right click on the command prompt icon in the start menu and select "run as administrator"

then run the netsh command. Otherwise it runs with normal user rights even when logged in as admin.

I find it hilarious that my problem seems to have fixed itself... I tried everything and it didn't seem to work. I finally got it to work after disabling IPv6 for my wireless connection and rebooting. I don't remember re-enabling IPv6, but it is currently running and I'm writing this from my laptop on a wireless connection at someone else's house. I truly feel, based on the results when getting configuration results back (ipconfig /all), that, in my case, the PC was using a “random” Automatic IP address configuration as the preferred connection. If anyone has insight as to how to possibly reverse/prevent this... please post.

I got past the "local" problem by opening the Network & Sharing Center, then open Manage network connections, and then highlighting the the connection and then opening "connectivity", setting it to internet and local and finally opening "network catagory" and setting it private ( check marks).

Now I am fighting with the dns server not recognizing the address.