Fixing the local only internet access issue in Windows Vista
Published Sunday June 08, 2008
2011-03-14 – Update: Please make sure to first try the automated fix provided by Microsoft in the knowledge base article (look for the “Fix it” icon).
Recently I had issues with Windows Vista where it would get on a network, but would only have local access (i.e. “Access: Local only” in the Network and Sharing Center). After spending about an hour and a half I finally stumbled across the solution. Once again, the solution was hidden in a forum, and the Microsoft knowledge base article was fairly hard to follow. So, here are the steps summarized for quickly fixing this.
- First we have to find the name of network adapter that you are using to connect, you can skip this if you know the name of your network adapter.
- Open Network and Sharing Center (Start > Control Panel > Network and Sharing Center)
- Click on “Manage network connections” under “Tasks” on the left side.
- Note the name of the device in “Device Name” column for the connection that you are using (e.g. Intel® PRO/Wireless 3945ABG Network Connection)
- Now we have to find the GUID of this adapter.
- Open the registry editor: Start > type in 'regedit’
- Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\
- Look through the numbered sub-keys and jot down the “ServiceName” for the one that has the name of your network card in the “Description.”
- Keep the registry editor open because we will be changing another key in the next step.
- Once you have the GUID of the network then we have to toggle the broadcast flags.
- Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces
- Now follow the resolution in the Microsoft knowledge base article
- Make sure to set the DhcpConnForceBroadcastFlag as described in the “More Information” section of the knowledge base article.
- Finally, restart the computer.
Hopefully, after restarting the computer you will be able to access the internet.
A Few Other Things to Try
Here are a few other things to try in case the above doesn’t work. These are based on the comments that people have left below.
- Try uninstalling the wireless card drivers, restarting the computer and then reinstalling the wireless card drivers (see your manufacturer’s website). This seems to have fixed the issue for a few folks.
- Try resetting your router.
- Try the automated “Fix it” in the Microsoft Knowledge base article.
- Try a different channel.
- Try changing the IP address range (generally 192.168.0.xxx, change to something like 192.168.9.xxx).
- Try a different security method (WEP vs. WPA). Please understand the this change because it might leave your wireless network vulnerable.
- Try the same security method with access control list (example) on the router disabled.
Comments
I was scared to do it thinking I wasn't savvy enough to do all that, but it wasn't bad at all! It took about 5 minutes and it worked the 2nd I clicked apply!!
Thank you!!!
Marc
The channel is generally configured in your wireless router. Most of the operating systems pick up this configuration from the network so you shouldn't have to do anything on your computer once you have changed the channel on your router.
How do I change the channel on my router?
Plzzz help.
I tried this myself after a couple of days of other stuff and for some reason it has worked!!
Might not work for all, but thats 2 people and its easy to do for us lacking IT skills.
type R > in Run windows type services.msc click on OK > Click on
Continue > Look for service 'winhttp web proxy auto-discovery service'
turn this service on and change its startup type to autmatic.
Disconnect ur connection and conenct it again .access local only' will
disappear.
Any help would be a appreciated!
Thanks.
It worked for me and the detail you provided was excellent!
-Stever
Good luck,
Farhan
Your fix worked ,after we had tried everything else.
thanks again,
John
It didnt worked for my friends case but this one worked
follow the same instructions as mentioned above (need not be) and addition to this
Just change your settings as mentioned bellow in the same service
i.e.,
Dhcpserver should be the same as that of DhcpNameserver
and try to have IP address similer to xxx.xxx.x.x
close restart and connection should be working
- Farhan
Any ideas?
Following the instructions above we could still only get a 'local' IP for the wireless connection. I found the problem was caused by the IP allocated to the ethernet port being the first address allocated by the DHCP server built in to the router!!!
As soon as I changed the ethernet IP to one outside of the DHCP pool (or anything other than the first one) the wireless was able to obtain a valid IP and give full Internet access.
If you hard-code any IP addresses for any devices ensure they are outside the DHCP pool so no conflicts arise with any device trying to obtain an automatic IP.
I hope this helps solve a few lingering headaches.
Tried All the steps provided but got no solution. i have Huawei E156G modem with 3 and this issue happensonly in Vista tried the modem on XP and Win 7 the modem is working fine .... please help
Good luck.
can i disable the IPV6 in the regedit.msc
===============================
10:33 a.m. Tuesday February 16, 2010 (about 1 year, 8 months later)
Access Local Only — Faisal Shaikh
Are ther any Sure Fix for this issue.
Tried All the steps provided but got no solution. i have Huawei E156G modem with 3 and this issue happensonly in Vista tried the modem on XP and Win 7 the modem is working fine .... please help
http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&selected_nav=&pvid=&docurl=20080828154508EN
The router was connected to the internet and the laptop running Vista could connect to the router but NOT the internet. All externals like Ipod Touch and PS3 could connect to the router/internet, but the laptop always just said local access only.
After playing with all of the setting here, Ip6, reinstalling the driver, EVERYTHING - it still said local only.
I called support for the router and here is what he told me:
VISTA systems do not really support WPA/WPA2 security settings for the router. Seriously, that was it. He had me do the following:
Type 192.168.1.1 into an internet explorer browser (while you have the wired connection working - so the ethernet cord plugged from the router into the laptop).
On the lefthand menu you will see "Wireless settings" click on that and type in a new name for your wireless connection (You can put a 2 next to the current name or something).
Change the channel to 6
Change the security settings to WEP
scroll down - you will see a field for a passcode and then 4 keys. Keep everything blank except in the Key 1 field, type in a 10 digit number that you will remember (MAKE SURE TO WRITE IT DOWN). Click apply.
You can now unplug your ethernet cord. Go to start, connect to, click the new connection name you just made. Now if it asks you to press a button or type in the code, click the type in the code thingy and then type in that 10 digit code that you wrote down.
You should be connected wirelessly to the internet.
Just follow what WIN DOS SUCKS has written above. The drive update, which Windows itself is not able to do, is the only that has worked flawlessly.
And, I like the name Windows Sucks.
Did the Microsoft Fix patch - no change.
Did the services change to automatic - no change
Tried the channel change in the router - no change
I wasn't using any fixed router addresses for specific computers so that wasn't relevant
It finally fixed itself when I disconnected from the wireles networks and while using ethernet conection changed the range of my routers IP addresses for DCHP so that when I connected again the Vista computer would have to use a new address. I also changed the lease time for addresses from Forever to Half an hour but that didn't work by itself, although I probably didn't wait half an hour).
When I disconnected the ethernet and reconnected to the wireless it connected through to the internet. I checked the address in the router and it was a new one (the old one was say 192.168.0.2 and the new one ended in 7 as I had made the first one in the range in the pool end in 4.
Thanks to all who posted solutions. I hope this acomment also helps someone.
This is a great step-by-step solution.
THIS ISSUE HAS BEEN GOING ON FOR TWO YEARS. THANKS YOU SO MUCH!!!!
I LITERALLY HAVENT USED THIS COMPUTER FOR TWO YEARS BCAUSE THE INTERNET WOULDNT WORK AND ONLY OPENED IT BCAUSE ME DOG CHEWED THE POWER SUPPLY TO MY OTHER LAPTOP.
THANK YOU!!!!!!!!!!!!!!!!!!!!!!
2) Wireless card driver update did the thing.
Brefore I have tried everything described here and there.
In trying to set them up the xoom worked np but the laptop had the "local only" network connection issue. Spent 2 hrs on the phone w/India and still ng. Finally did a restore of the system but no time to check it as we were headed out for the holiday. Took the laptop with me to see if it would work in a new environment. Sure enough worked like a charm @ my sisters house, thought I was done. We return 2 days later and the new laptop now works fine on our home network but all of a sudden my laptop, which had been running just fine for 2-3 yrs encountered the exact same issue. I'm thinking virus:(. Tried many of the suggested fixes to no avail. Then I remembered, for added security, I had set our DHCP server to only use 192.168.1.3-192.168.1.12 when assigning ip addresses, a total of 10. It seems by adding the xoom & the laptop we exceeded the number of devices requiring an ip address within our house. As soon as I went into the router and expanded the range a bit and rebooted everything, we are all back in business.
Once again the law of unintended consequences rears its ugly head.
Just remember, sometimes you need to step back and take a larger look at what’s going on to find the answer.
Seems like Microsoft would mention this somewhere in the knowledge base.
Thanks to all who contributed
I hope someone will find this helpful.
h.
tried everything for days
just updated my Wireless driver and it worked instantly
Had same problem as everyone else when trying to connect my son's Compaq laptop - kept getting local access only.
I have tried almost every patch/fix attempt I could find, but to no avail.
I did however work out an albeit not perfect fix.
My new router enables me to create primary and guest networks. I created a primary wireless network and created a WPA AES encrypted password. This works 100% with any device not running Windows Vista.
For my son's Vista laptop, I created a separate guest network without any WEP encryption (open network). Then I was able to make it a Closed Network via my Motorola router software. This means that although it is unlocked, a user would have to know and type the exact network name into the available network list instead of selecting it from a list. When scanning for available networks, it simply show up as un-named network, then when you click to connect it asks you to type the exact network name. Nice stuff Motorola!
Not exactly an ideal fix, but it kinda works for me until we can upgrade his laptop with Windows 7.
Hope this helps someone? Believe me, I feel your pain! :(
Thanks tho ;)
- Farhan
This problem is becoming a pain in the proverbial.
cheers
I tried the above advice registry edits etc. didn't work (but thanks for sharing experiences)
Then i did a driver update for the wireless modem in Device manger. It worked.
Thanks Everyone who contributed
Then uninstalled Norton. You need to go to ftp://ftp.symantec.com and get the un-installer there. This seemed to clean things up a lot.
Which as far as I'm concerned means your solution IS the right one because everyone else's trying to fix their 'slow' Vista wifi, but with the XP driver running it's the best of both worlds! Thanks for the inspiration, mate.
Every attempt to update the driver automatically resulted in Windows (I hate, and keep one machine at home for that rare instance an older web page won't load Safari on Mac) telling me that my HP/Compaq had the best and latest driver. Following a link from CNet (http://forums.cnet.com/7723-12546_102-522932.html) I was led to a page that had a driver that was 3 years and many generations younger than what Windows claimed to be the best and latest. The link from CNet is to: http://www.atheros.cz/atheros-inf-file.php?inf=236&chipset=21&system=3
At any rate, I've been running fine for about three hours now.....a record on my laptop who would connect and go local every five minutes.
Best of luck.
After doodling with all the microfrost help, entering unusual commands, etc.
My driver is a 2010 driver now, vs. 2008.
I have suffered for months until the driver upgrade.
So disappointed in MS. I might go Ubuntu.
Nothing has worked except your solution.
I have vista in laptop and sudently couln't connect to internet (only local connection with both wireless and ethernet cable).
As it seemed i had just to enable the DHCP